Using a Different Job Title Than the One on Your Payslip

Many people have two job titles: the one in the HR system and the one they used with colleagues and clients. Putting the working title on a resume is reasonable when the official one is meaningless, but it creates a mismatch with the record an employer may check. The safe approach is to show the official title as the title and the working one as context, in the same entry, so nothing is hidden and nothing is unclear.

Why the two diverge

Official titles are shaped by internal pay structures rather than by what anyone does. Organisations use graded ladders — Analyst II, Officer Grade 5, Associate — where the number carries the meaning internally and nothing at all externally. Others use a small set of generic titles for a wide range of work, so “Consultant” covers three unrelated jobs.

Meanwhile the working title describes the function: the person everyone called the data lead, the de facto office manager, the one who ran security reviews. That title is more informative to an outside reader and appears in no system.

Neither is dishonest. The problem is only that a resume shows one and a verification check returns the other.

What a check actually returns

Employment verification, where it happens, typically confirms a small set of fields: that you worked there, the dates, and the title as recorded. It does not evaluate whether the recorded title was a fair description. So a resume saying “Head of Analytics” against a record saying “Analyst II” produces a flat contradiction, even if every colleague would have described you as running analytics.

The difference matters because titles are the field where people most often assume interpretation is allowed. It generally is not — the check compares strings.

The format that solves it

Show both, with the official one in the structural position:

Analyst II (working title: Data Lead) — Company, Mar 2022 – Aug 2024

Or, where the working title needs more room:

Analyst II — Company, Mar 2022 – Aug 2024 Known internally as the data lead; sole owner of the reporting stack for two product teams.

Both are fully accurate, both give the reader the useful information, and neither can be contradicted. The second version is often better, because a sentence describing the responsibility carries more than a title does anyway.

Avoid the reverse arrangement — working title in the heading with the official one in small print — because a skim reader takes the heading as the claim, which is the situation you were trying to avoid.

Translating a meaningless title

If your official title is a grade with no external meaning, you still should not replace it. Keep it and add a short translation:

Officer Grade 5 (equivalent to senior project manager) — Department, 2021 – 2024

The word “equivalent” is doing honest work here: it signals a comparison rather than asserting the title. A reader who wants the mapping gets it; a checker who wants the string gets that too.

Where this crosses into overstatement

Two cases are worth naming plainly.

Inventing a seniority level you did not hold. Turning Associate into Senior Associate, or adding “Lead” to a title where nobody treated you as one, is not translation. It also tends to be internally inconsistent, because the verbs and scope in the bullets underneath will not match, and the verb you chose is a claim in its own right.

Upgrading a title an AI tool suggested. Ask a drafting tool to make an entry stronger and it may rewrite the title, quietly, as part of tidying the entry. Titles are fixed fields and should be copied in from your own records at the end, exactly as dates should be. Check them explicitly on the final read; they are easy to skip because they look like headings rather than claims.

Consistency across surfaces

Whatever you choose, use the same construction everywhere. If your resume says “Analyst II (working title: Data Lead)” and your public profile says “Head of Analytics,” you have created the discrepancy yourself, in public, where anyone can see it. This is a common and entirely avoidable version of the problem, and keeping one story across every surface is the fix.

The same goes for application forms. A form asking for your most recent job title is asking for the official one; put it there and use the resume for the nuance.

If you have already sent the wrong version

It happens: an old resume with an upgraded title is out there, possibly with an agency. Correcting it early is much easier than correcting it after an offer, and there is a straightforward way to send a corrected version without turning it into an incident.

The underlying point

A resume is read by people trying to work out what you can do, and it is checked by systems comparing strings. Those are two different audiences with two different needs, and the both-titles format serves each without lying to either. Once you see the split, most title questions answer themselves: put the checkable thing where it will be checked, and put the meaningful thing where it will be read.