skip to content

When two job offers carry the same engineering title, how do you check they are really the same level?

level: middleimportance: should knowfreq 42%

answer

  1. The noun on the letter is not the job
  2. Which rung, out of how many?
  3. Own it, or contribute to it?
  4. Ask for the written expectations per rung
  5. The rung carries the band, not the word

basics

~20 s

Titles are not standardized between employers, so compare the written expectations for the rung, the scope you would own, where that rung sits within the ladder's full length, and which pay band the level carries.

solid answer

~50 s

Ask each employer for the written expectations attached to the rung you are being offered, and compare those, not the words on the letter. Three checks do most of the work. First, position: which rung is it out of how many, since a middle rung on a long ladder and a middle rung on a short one mean different things. Second, scope: would you own a system and its direction outright, or contribute inside something someone else owns? Third, band and next step: what pay band does the level carry, and what does the rung above it require? Ladder shapes, internal level codes and promotion cadences vary a lot by employer, so treat every mapping as approximate. The reason this matters is that the level, not the title, sets your scope, your band and where your next promotion starts.

go deeper

for a junior

Remember that titles are set per company and are not comparable across employers. Ask which rung a role sits on and what that rung is expected to own.

for a middle

Explain how the level drives the pay band, the scope assigned to you and the starting point of your next promotion — that is why the rung outranks the word.

for a senior

Show how you would map two different ladders onto each other from evidence: ladder length, written expectations, decision rights and what the next rung demands.

for a principal

Own the ambiguity: ladder mappings are approximate and scope varies inside a rung. Say which mismatch you would accept and what you would want in exchange.

## Why titles do not compare There is no industry registry of engineering levels. Each employer designs its own ladder, decides how many rungs it has, writes its own expectations for each rung, and attaches its own pay band. The result is that the same word on two offer letters can describe visibly different jobs, and two different words can describe the same job. Any comparison that runs on titles is comparing labels. What you actually want to compare is the **level**: the internal rung, with its written expectations, its scope and its band. ## Four things worth comparing **1. Position on the ladder.** Ask how many rungs the engineering ladder has and which one the offer sits on. A rung four steps into an eight-rung ladder is a very different place from a rung three steps into a five-rung ladder, even when both letters say the same thing. Many employers also carry an internal level code distinct from the public title; the code is the thing the band and the review process actually key on, so ask about it directly. **2. Written expectations.** Most companies with a ladder have a document describing what each rung is expected to do — scope of ownership, how far ahead they plan, whether they set technical direction, whether they are expected to grow other people. Ask for the expectations for the rung you are offered, in writing. Comparing two such documents is the single most informative thing you can do here, and asking for them is normal. **3. Scope and decision rights.** Read past the adjectives to the verbs. Would you *own* a platform capability — its design, its reliability, its roadmap — or *contribute to* one that someone else owns? Who decides when your part of the system changes shape? Whose sign-off does a risky migration need? Scope is what the level really encodes, and it is the part you would spend a year re-proving if you enter a rung below where you currently operate. **4. Band and next rung.** The level sets the pay band you sit inside, which is why a down-level with a bigger headline package can still be behind after a review cycle or two: the band moves with the rung, not with your starting figure. Ask what the rung above requires and roughly how long people spend at your rung before moving. Cadences vary by company and by year, and nobody can promise you one — treat the answer as a shape, not a commitment. ## Signals that a title is running ahead of the level - The company cannot describe what the rung owns beyond the title itself. - The ladder is short or newly written and everyone senior carries the same word. - The scope described in the loop is narrower than the scope you own today, but the title is the same or grander. - The title was raised during the process without any change to the described responsibilities or the band. None of these is disqualifying. A grander title on a short ladder at a small company can be an excellent job with genuinely wide scope. The point is to score the level from evidence rather than from the noun. ## Putting it on the scorecard Level and scope deserve their own row, weighted before you see any offer, and scored from the expectations documents rather than the letters. In an illustrative platform-engineering comparison, one offer may carry a grander word attached to a narrower remit and a lower rung on a longer ladder; scored honestly, that row goes down even though the title reads up. This is also where the most useful sentence in offer evaluation tends to come from — "The higher number is at a lower level, with a manager I did not click with" only becomes sayable once you have checked the level rather than the title. ## The practical script Ask, plainly: *what rung is this out of how many, what are the written expectations for it, what would I own outright, and what does the next rung up require?* Employers with a real ladder answer these easily. An employer who cannot answer them at all has told you something about how levels work there, which is itself a score on that row.

  • What would you ask to find out whether a level is real rather than a generous label?
    Ask what the rung owns outright, what decisions it makes without sign-off, how many rungs the ladder has and where this one sits, and what the rung above requires. Then ask for the written expectations. A company with a real ladder produces those quickly; one that can only restate the title has answered the question a different way.
  • Why does entering one rung lower matter even when the package is larger?
    Because the rung, not your starting figure, sets the band you sit inside, the scope handed to you and the starting point of your next promotion. A larger package at a lower rung can be behind within a couple of review cycles, and meanwhile you spend that time re-proving scope you already had.
  • Is a grander title at a smaller company always a warning sign?
    No. Short ladders are normal at small companies, and the scope behind the title is often genuinely wide — sometimes wider than the same word buys elsewhere. The check is the same either way: what does the rung own, what decisions does it make, what does it take to move up. Score the evidence, not the noun.

saying these in an interview costs you the question

  • Assuming identical titles at two employers mean identical levels
  • Comparing rungs without asking how long each ladder is
  • Accepting a title bump with no change in scope or pay band
  • Never asking for the written expectations attached to the rung
  • Treating a promised future promotion as if it were part of the offer

context