Your Job Titles Are Lying for You — Add One Line to Make Them Earn It

A recruiter at a global bank opens a CV that says “Director, Operations.” She skims the dates, the company name — a Series A startup of forty people — and revises her estimate of the candidate downwards before she’s read a single bullet. Two minutes later she opens another CV that says “Director, Operations” at a 180,000-person insurer. She revises that one downwards too. Same title, two opposite reactions, both wrong. The problem isn’t either candidate. It’s that “Director” without context means almost nothing on its own.

The short answer: under each job title on your CV, add a single line — under twenty-five words — that names who you reported to, what you actually ran (team size, budget, surface area), and the organisational context. That line does more for your seniority than rewording the title ever will, and it survives the reference check.

Job titles have inflated and deflated wildly over the last decade, and they vary so much between organisations that recruiters have stopped trusting them as a primary signal. What they trust instead is scope — the size of the team you ran, the budget you owned, who you reported to, what you were actually responsible for. The eye-tracking work behind the Ladders 2018 study found that in a 7.4-second first-pass scan, the title block is one of the only things a recruiter reliably reads — which is exactly why a one-line context tag earns more than reworking the bullets underneath.

This piece is about how to add one line of context that protects your real seniority — without inflating it, and without forcing the reader to deduce anything.

Why the title alone doesn’t work

The same word does completely different work at different companies. “Senior Manager” at a twelve-person agency means you and the founder are running the place. At a bank, it’s a salary band — there are six thousand of you, and the title tells you almost nothing about scope. “Director” at a 200,000-person org sits four levels below the SVP and runs perhaps a 30-person sub-team. At a 30-person Series A, “Director” is two levels below the founder and you might run the entire function.

Recruiters know this. They’ve seen the same titles at fifty different companies. What they want, when they hit your title, is one fast piece of context that tells them which version of that title this is.

The pattern that holds up across enough hiring loops to count: a recruiter looking at your title block isn’t trying to find out whether you had a senior role. They are trying to find out which senior role — and they want it answered in the next sentence, not at the bottom of the bullets. That single sentence is what most candidates are missing. Not because they’re being modest — because nobody told them it was a separate field.

The pattern: title, then scope-and-context

The structural change is small. Under the title, before the bullets, you add a single line. It contains three things, in roughly this order:

• Who you reported to — "reporting to the CEO," "reporting to the SVP of Product," "reporting to the founder."
• What you ran — team size, surface area, budget, region, named product.
• The organisational context — total team size, division, where this role sat in the structure if it's not obvious.

You don’t need all three on every role. One or two will usually do the job. The whole line should be under twenty-five words. It is not a bullet point — it’s a scope tag.

What it looks like in practice

Two candidates, two different “Senior Manager” titles, both unhelpful on their own. Here’s the same role with and without a context line.

The “after” tells a recruiter, in twenty-six words, what level they’re really looking at — a senior manager with a specific remit, working directly under a group head, with named scope. It also gives them three things to ask about in interview, which is half the reason your CV exists.

The same pattern works at the other end of the size spectrum:

Without the context line, “Director” at a 38-person company is a coin-flip — half of recruiters will read it as inflated and half will read it as substantive. With the line, there is no coin-flip. The recruiter knows exactly what they’re looking at, the candidate hasn’t inflated anything, and the company size is named openly. That last detail is the one most candidates skip, and it’s the one that does the most work.

The trap on the other side: title inflation

The opposite mistake is more dangerous. A candidate who renames their job on the CV — calling themselves “Head of Product” when their actual title was “Senior Product Manager” — almost always gets caught at the reference stage. The reference call asks one straightforward question: “And what was their job title with you?” If the answer doesn’t match the CV, the offer disappears and the conversation ends.

The context line solves this elegantly. You don’t need to upgrade your title to “Head of Marketing” — you write “Senior Marketing Manager, reporting to the CFO; ran the marketing function in the absence of a Head of.” That’s true, it survives the reference call, and it does ninety percent of the work that the inflated title would have done.

When the team you ran wasn’t yours on paper

A common edge case: you led a project team, an initiative, or a working group that didn’t appear in the org chart. The instinct is to overclaim — “Managed a team of nine” when the actual reporting line was dotted. The better phrasing names the dotted line plainly. “Led a nine-person cross-functional pod across engineering, design and marketing for an eighteen-month rebuild — no direct reports, but functional ownership of the workstream.”

That sentence is longer than the inflated version, but it survives interview. A recruiter who reads it knows exactly what kind of management this was — and crucially, they know you know the difference. That last part matters. The candidate who blurs the line between “managed” and “led” reads, in interview, as someone who’ll do the same with budget and authority once they’re hired. The candidate who names the distinction reads as someone who is going to be a clean hire.

What changes downstream

Adding a context line is a fifteen-minute job. It is also one of the few CV changes whose effects compound through the whole hiring process. The recruiter routes your CV with more confidence, because they know what scope they’re selling to the hiring manager. The hiring manager goes into the first conversation knowing what to ask about, so the call is more substantive. The reference checks go through without surprises. And the offer conversation — when it happens — starts from a more accurate read of the role you came from, which usually means a better number.

None of that requires you to change a single bullet, a single date, or a single line of your actual experience. It requires one line of context per role. Most candidates haven’t got it. Recruiters notice the ones who do. Once the context line is in, the next two passes worth doing are the six-second CV rewrite — making sure the rest of the page survives the same fast scan — and the bullet-to-cut audit, which removes the bullets that no longer pull their weight now that scope is named up top. If your bullets still lean on “responsible for,” see our take on the alternatives that actually land.