Why is benchmarking your pay by job title unreliable when comparing across companies?
answer
- Ladders differ, labels do not travel
- Compare scope, not the word on the posting
- Count the rungs before comparing bands
- Pay is administered against the internal rung
basics
~20 sJob titles are not calibrated between employers, so the same title can sit two rungs apart on two ladders. Pay is keyed to the internal level, so benchmark the scope the role owns, mapped to each company's own rung.
solid answer
~50 sTitles are marketing; levels are the thing pay is actually keyed to. One company may run seven engineering rungs and open a security role at rung four; another runs five rungs and opens comparable work at rung three — and both postings say the same word. If your benchmark sheet has a title column instead of a level column, you are pooling entries from different rungs and computing a band that describes no real job. The fix is to map by scope: what the role owns, how much autonomy it carries, whether there is a rung above it doing the same work at wider blast radius. Then read the band for that rung, at that geography and company stage. Where the mapping is genuinely ambiguous between two rungs, record both bands rather than picking the flattering one.
go deeper
Remember that pay is attached to a company's internal rung, not to the words on the posting, and that two companies can use the same seniority adjective for very different jobs.
Be able to explain the mechanics of mapping: rung counts, scope descriptions, autonomy and blast radius, and why pooling untagged entries by title yields a band that matches no real rung.
Demonstrate judgment when the mapping is ambiguous — bracketing two rungs on the sheet, deciding which scope evidence outweighs which, and re-deriving your numbers when the level turns out different from your first read.
Own the tradeoff in choosing which ladder to be measured against at all: a wider rung at a smaller company buys scope and volatility, a narrower rung at a larger one buys band predictability, and the benchmark sheet should show both.
## Titles travel; levels do not Every company that has grown past a handful of engineers has a ladder: an ordered set of rungs, each with a scope description and each attached to a pay band. Compensation is administered against the rung. The title on the job posting is a label applied on top, chosen partly for recruiting appeal, and it is not calibrated against anyone else's labels. That is why the most common benchmarking mistake is to benchmark a title instead of a level and then compare across ladders that do not align. It feels rigorous — you have entries, you have a median — but the entries came from different rungs, so the band you computed describes no real job at all. ## What ladder mismatch looks like Take an invented but internally consistent example in the security world. Company A runs an engineering ladder of seven rungs and opens a detection-engineering role at rung four; the rung's scope description says the person owns detection coverage for one product area and reviews the work of one or two others. Company B runs five rungs and opens what is functionally the same work at rung three; but B is a 60-person company, and rung three there owns the whole security function, including vendor review and incident response. Both postings carry the same seniority adjective. The scopes differ by a lot, the bands differ by more, and a sheet keyed on the adjective merges them into one meaningless number. ## Map by scope, not by adjective Useful scope anchors, in rough order of how much signal they carry: 1. **Blast radius** — one component, one product area, one function, or the whole organisation. 2. **Autonomy** — is the problem handed over defined, or does the role define it? 3. **Ownership of others' output** — reviewing, mentoring, setting technical direction others follow. 4. **What sits above** — if there is a rung above doing the same work at a wider radius, you are not at the top of the ladder, whatever the posting says. 5. **Rung count** — a five-rung ladder and a nine-rung ladder cannot be compared position by position; compare by scope description instead. Once you have the rung, everything else on the benchmark sheet keys off it: geography, company stage, and the percentile position where your target and walk-away sit. ## What the other side of the table sees A compensation partner does not price a title. They price a rung, inside a band the company has already approved, adjusted for a location tier. This is why a conversation about the number goes nowhere until the level is settled: two people using the same word for different rungs will disagree about the band forever and never find out why. It is also why finding out which internal level a role is opened at is a research task you can do early and openly — it is a factual question about the role, not a negotiation move. ## When the mapping is ambiguous Sometimes you honestly cannot tell whether a role sits at one rung or the next. Do not resolve the ambiguity in your own favour and forget you did. Record both: on the sheet, keep a band for each candidate rung, and set the target against the lower rung's upper region until the mapping firms up. That way, if the level turns out higher, you get a pleasant correction rather than a position you cannot defend. A related trap is the title bump with no scope change. A change of adjective without a change in what you own does not move you to a new band; it moves you to a new word. When you see one in your own history, benchmark the scope you actually held. ## Reading the sources with this in mind Most crowdsourced compensation entries let the submitter type a title and, sometimes, tag a level. Entries that carry a level tag from a company whose ladder you can describe are worth many untagged ones. Some postings publish a range as well; where they do, treat that range as one more data point about that company's band for that rung, not as a statement about where in the band you would land. Practices around what postings disclose vary by market and by employer, so treat any such range as evidence, not as a rule. The discipline is one line long: a benchmark sheet has a level column, not a title column.
- How do you find out which internal level a role is opened at before the final round?Ask directly and early — it is a factual question about the role, not a negotiation move. A recruiter or compensation partner will usually name the rung, and the loop itself gives evidence: what scope the interviews probe, whether there is a rung above doing the same work more broadly, and how the company's published ladder describes the level.
- Two companies both call the role senior. What evidence tells you the rungs are not equivalent?Compare scope descriptions rather than adjectives: how wide the blast radius is, whether the role defines its own problems, whether it owns others' output, and how many rungs sit above it. A five-rung ladder and a nine-rung ladder can put the same word in very different places.
- What do you put on the sheet when the level mapping is genuinely ambiguous between two rungs?Both bands. Keep a row for each candidate rung and set the target against the lower rung's upper region until the mapping firms up. Resolving the ambiguity in your own favour produces a position you cannot defend; recording both means a higher level is a correction upward rather than a surprise.
saying these in an interview costs you the question
- Averaging pay for a title across companies with different ladders
- Assuming a seniority adjective means the same rung everywhere
- Treating a title bump with no scope change as a band change
- Reading one aggregate median for a title and calling it a band
- Resolving an ambiguous level mapping upward and forgetting you did