Your contract says "Associate II". What you did for three years was run payroll for 400 people in two countries. A recruiter looking for a payroll manager will never type "Associate II" into a search box, and the software sorting applications will not guess on your behalf.
That gap between the title on record and the title the market uses is ordinary, and it runs in both directions. Some titles undersell the job, some oversell it, and some describe nothing. You are allowed to fix the line. You are not allowed to fix it into a different job.
Three ways an official title goes wrong
Obscure and internal titles. Grade codes and house vocabulary: "Associate II", "Member of Technical Staff", "Analyst, Band 6", "Customer Happiness Ninja". They are precise inside the building and empty outside it. A Member of Technical Staff can be a backend developer two years out of university or a researcher with twenty years behind them.
Inflated titles. Small firms hand out big titles because titles are free. The "Head of Marketing" at a nine-person company is often the entire marketing department. In some banks, "Vice President" is a mid-level grade shared by a great many colleagues. Sent unexplained to a larger employer, either title makes the reader assume a scope you never had, or suspect you of dressing things up. Both outcomes hurt you.
Deflated titles. Large organisations do the reverse. Titles are tied to pay bands, so a "Coordinator" or an "Officer" can be running a multi-country programme with a budget in the millions. A grading committee set the title once and the job kept growing.
The mechanism is the same in all three. The reader converts your title into their own scale, and the conversion comes out wrong.
The honest fix is two titles on one line
You don't have to pick one. Put the official title and a market equivalent side by side, one in the main position and the other in brackets straight after it. The reader gets the word they recognise, and the line still matches the record.
A few before and after lines:
- Before: Associate II. After: Associate II (payroll management, 400 employees, UK and Ireland)
- Before: Member of Technical Staff. After: Member of Technical Staff (Backend Software Engineer)
- Before: Customer Happiness Ninja. After: Customer Support Specialist (official title: Customer Happiness Ninja)
- Before: Head of Marketing. After: Head of Marketing (sole marketer in a 9-person company, reporting to the founder)
- Before: Programme Coordinator. After: Programme Coordinator (project manager for a 6-country programme, EUR 3m budget)
Look at what the brackets do in each case. For the obscure titles they translate. For the inflated one they shrink the claim to its real size before anyone else does. For the deflated one they add the scale the title hides. None of them raises the level.
One rule for the bracket: it describes the function in words a stranger would use, and it stays short. If it runs past a dozen words, the detail belongs in the first bullet under the role.
Which title goes first
Both orders are honest. They are not equally useful everywhere.
Official title first is the right order when the employer is likely to check, which means finance, healthcare, government work and most large companies. It is also right when the official title is plain enough to be half understood and only needs a nudge, like "Analyst" or "Officer". The record leads and the translation follows.
Market title first is right when the official title would match nothing at all. Nobody searches for "Ninja", "Associate II" or "Band 6". When you apply through an applicant tracking system, the title of your current role is commonly one of the things compared with the vacancy, so a line that opens with a code gives the system nothing to work with. Lead with the plain title, then write "official title:" and the real one in brackets. Those two words matter. They show you are translating in the open.
If the market title leads, the official title must still be on the page. A translation the reader can see is a courtesy. A swap they cannot see is a discrepancy.
My own view: if you are unsure, put the official title first. It costs you a little in search matching, which the bullets underneath can win back, and it never has to be explained to anyone. Which words to carry into those bullets is a keyword question, and a separate one.
Where an edit becomes a lie
Three things cannot move: level, scope, and whether you managed people.
- Level. "Senior", "Lead", "Head of", "Director" and "Principal" are levels. If your employer did not give you the word, you cannot give it to yourself, however senior the work felt.
- Scope. "Finance Manager" for someone who ran accounts payable claims the whole function. Write the part you ran.
- People. "Manager" suggests direct reports to most readers. If you managed a process, a budget or a supplier, say so in the bracket. "Team Leader" with no team is the edit that falls apart fastest.
The test fits in one question: would the HR department of your former employer recognise the role from your title line? They do not have to like the wording. They only have to recognise the job. "Backend Software Engineer" for a Member of Technical Staff who wrote backend code passes. "Engineering Manager" for the same person does not.
Think about what actually gets confirmed. Many employers will confirm only your dates of employment and the title held on record, and some go no further than that. A background check compares what you declared with that record, line by line. If you gave both titles, the comparison finds nothing to report. If you gave only your own version, it shows up as a mismatch, and you end up defending an honest translation as though it were a fabrication. A referee asked about your role will answer in the company's words too, so tell your referees which wording you used.
Keep the CV, LinkedIn and the application form aligned
Recruiters often open your LinkedIn profile next to your CV. Two different titles for the same job over the same dates look careless at best. Use the same pairing in both places. On LinkedIn the title field of a position accepts free text, so the bracket format works there as well.
This matters even more when one document feeds the other. A tool like Postulit builds a CV from your LinkedIn profile, so whatever sits in the title field of each position is what lands on the CV. Fix the title once on the profile and the two stay in agreement.
Application forms are the exception to the pairing. Many have a field that asks for your exact job title, and some add a declaration that everything entered is accurate. In that field, give the official title and nothing else. Put the market equivalent in the description box, or let the attached CV carry it. The form is the document a check is most likely to be run against, so it gets the version on record.
Then prepare one sentence for the interview, because someone will ask. "My contract title was Associate II, which is a grade at that company. The job itself was payroll manager for the UK and Ireland." Say it flatly and move on. People who work in hiring have seen stranger titles than yours.
What to do this week
For each job, find the document that states your official title: the contract, an offer or promotion letter, your HR record. Don't work from memory, because titles drift in conversation over a few years.
Then, for every role where the title would confuse a stranger, write the pair. Official first, unless it matches nothing. Check each bracket against the three things that cannot move. Copy the result to LinkedIn word for word, and keep a note of the bare official titles for any form that asks. That is about an hour of work, and it removes a question you would otherwise answer badly under pressure.