What to do when your job title doesn't match the work you did
Your title says "Coordinator." Your job was running projects. Or the reverse: the title sounds big, and the work was small. Either way, the line on your résumé and the work you did don't match, and you have to decide what goes on the page.
I've changed industries three times, so I've had to explain what a title meant in one place to people who only know how it's used in another. A "project engineer" on a highway crew and a "project engineer" at a software company are not the same job. Titles don't travel well. Here's what I do about it, and the one thing I won't do.
The rule: the title is a fact, the work is yours to describe
Your official title is a record. It's in your employer's system, and it's what a background check will confirm. Changing it on your résumé is the fastest way to turn a small mismatch into a real problem. If you wrote "Project Manager" and their records say "Coordinator," the offer can get pulled after you've already told your current boss you're leaving.
So keep the title honest. Then put the real work in the bullets, where you have all the room you need. A title is a few words. Your bullets are where a reader learns what you actually did.
Three common mismatches and what to do
1. The title is smaller than the job
You were a "Coordinator" or "Assistant" and you ran budgets, schedules or a team. This is the most common one, and the most common mistake is quietly upgrading the title.
Don't. Do one of these instead:
- Keep the title and lead with the scope. First bullet states what you owned: "Ran scheduling and vendor follow-up for 12 concurrent projects." A reader sees the size of the job before they care about the label.
- Add a plain clarifier in parentheses if the title is vague enough to mislead: "Coordinator (project management duties)." You're not renaming anything. You're telling the reader which kind of coordinator.
If you want to show a real jump in responsibility, say so with a number, not an adjective. I wrote more about that in how to quantify your résumé bullet points.
2. The title is bigger than the job
"Manager" with no direct reports. "Lead" on a team of two. This one worries people less than it should, because a big title feels like a gift.
It's a risk of its own. A reader sees "Manager," expects management, and asks in the interview how many people you managed. Answer that with the truth up front. Keep the title, and make the first bullet say what it really covered: "Managed vendor relationships and the monthly budget; no direct reports." That one line takes the question off the table and shows you answer straight.
3. The title is a company-internal label nobody outside would understand
"Associate III." "Level 5 Specialist." "Operations Analyst II." These tell a recruiter nothing, and some applicant tracking systems match on title text.
Here the usual advice is fine: keep the official title and add the common industry name next to it, such as "Associate III (Accounts Payable Specialist)." Both are true. The official one is there for verification, the second one is there for the reader and the software. If your employer's own public job postings use the common name for the same role, that's a good sign the clarifier is accurate.
What about contract work, or a title from a different employer?
If you did the work through a staffing firm or an agency, the title you were given there and the work you did on the client's site can differ. The cleanest way is to list the arrangement as it was, not to blend it. I covered that in how to list contract and freelance work on your résumé. The same rule holds: real title, real dates, real scope.
A quick test before you add a clarifier
Ask yourself three things:
- Could HR confirm every word I wrote? If you wrote only the official title, yes. If you added a clarifier, could they confirm the duties it describes?
- Would my old manager read this and nod? If they'd wince, it's inflated.
- Could I explain it in one sentence in an interview? "My title was Coordinator, but about half my time was project management." That's an easy sentence to say out loud. If you can't say it comfortably, don't write it.
Where the match actually matters: the job you're applying to
The mismatch that costs people interviews is usually not their own title. It's the gap between their wording and the posting's wording. Your title can be accurate and still not use the term the posting uses. That's not a reason to change it. It's a reason to make sure the work underneath uses the same terms, truthfully. I wrote up how to do that in tailoring your résumé to a job description.
The short version
- Keep your official title. It's a record, and it can be checked.
- Put the real scope in the first bullet, with a number where you have one.
- Use a plain clarifier in parentheses when the title is vague or internal. Both parts must be true.
- Never upgrade a title to fit the job you want. The offer is where it comes back to bite you.
A title is a few words, and you don't control how your employer wrote it. You do control the rest of the page. Spend it on what you did.
ResumAI is a privacy-first résumé builder. Your résumé is scrubbed of personal details before it reaches any AI model, it's never shown to other users, and you can bring your own AI key or delete everything with one click. The Vault holds your master résumé and tailoring matches it to the specific job you're applying to, using only the experience you already have.