When a job posting spans two adjacent engineering levels, how do you decide which rung to interview at?

## Why the choice exists A posting that spans two rungs — say senior through staff — is common when a team has flexible headcount and would take a strong person at either level. Somebody still has to decide which loop you run, because the round mix and the bar differ. That decision is often made quietly in the first recruiter or hiring-manager conversation, from how you describe your recent work, unless you make it explicitly. ## Get the ladder text first The single most useful input is the company's **internal level-ladder document** — the written expectations per rung. Many hiring managers will share the relevant pages when a candidate asks, and asking is itself a reasonable signal. Read the two paragraphs side by side and ignore the titles: rung names are not portable between companies, and what one org calls senior another calls staff. What matters is the expectation text, which is usually written in scope terms — owning a system, setting direction others adopt, accountability beyond your own team. If no such document exists or it is not shared, substitute the hiring manager's own answer to a direct question: *what would someone at the higher rung be doing here in their first year that someone at the lower rung would not?* ## The evidence test Run your own inventory against the higher rung's wording. For an invented example: the platform group of a national freight carrier posts an opening across two rungs, and its staff rung reads *sets technical direction that at least three teams adopt, and is accountable for outcomes beyond own team*. The honest test is not whether you could grow into that. It is whether you can already name two or three pieces of work that match it at decision level — where you can say what was ambiguous, what you chose, what you rejected, which other teams changed behaviour, and what was true afterwards. Two or three solid matches: interview at the higher rung. One thin match: you are choosing between a hard loop you might lose and a comfortable one you may outgrow quickly. Zero: the lower rung is the honest answer, and the year that follows is how you build the evidence. ## The tradeoff, stated plainly **Interviewing at the higher rung** buys you a starting position that matches how you already work, avoids re-proving scope you have already demonstrated, and generally comes with a higher pay band, since band follows rung at most companies (what those bands are, and how to research them, is a separate exercise). It costs you a harder loop with more scope-shaped rounds, a higher chance of a down-level or a no-hire, and — if you land it thin — a first year spent stretching rather than settling. **Interviewing at the lower rung** buys a loop you are more likely to pass and a start where you are comfortably above the bar, which is genuinely pleasant and often leads to fast recognition. It costs you the possibility of arriving already doing the rung above and having to demonstrate it again through an internal process whose speed and predictability vary a great deal between companies — worth asking about rather than assuming. ## What tips it - **Evidence density** is the primary input. Ambition is not evidence, and neither is elapsed time. - **How the company handles an in-loop level decision.** Some panels are explicitly allowed to recommend either rung from one loop, which lowers the cost of aiming high; ask whether that is the case here. - **Trajectory of the team.** A growing group with work at the higher scope makes the higher rung easier to grow into if you land under it; a stable team with the senior work already owned makes it harder. - **How long you plan to stay.** The cost of starting a rung low compounds with a short tenure and washes out over a long one. ## The failure mode Candidates who prepare identically at every level tend to default to the higher rung on ambition and then run the lower rung's preparation — problem drilling, no scope inventory. That combination reliably produces the loop described in the down-leveling material: clean coding, prompted design, task-scope stories. Choosing the higher rung is a decision that obliges you to prepare differently, not merely to ask for more. The symmetric failure is under-claiming: a candidate with genuine cross-team direction accepts the lower rung to reduce risk, arrives visibly above the bar, and spends a year in a process to correct it. Both errors come from deciding before reading the ladder text. ## How to actually raise it Say it early and in evidence terms rather than as a request: that you read both rungs' expectations, that your last two pieces of work match the higher one in these specific ways, and that you would like the loop scoped there. That framing gives the hiring manager something to calibrate against, and it is far stronger than asking to be considered for the higher rung with nothing attached.