What the level actually means — scope, blast radius, and how to tell.
Staff Engineer
Also seen as: L6, IC4, Senior Staff, Principal (at smaller companies), Architect
Scope
A problem that spans teams and doesn't have an obvious owner. Often the work is deciding what should be built at all.
Blast radius
Organisational. A Staff engineer pointing the org at the wrong technical strategy costs quarters of work across multiple teams.
Autonomy
Given a business problem, not a technical one. Sets their own agenda and is trusted to have picked the right thing.
With other people
Most of the job is influence without authority: aligning teams who don't report to them, writing the document that settles an argument, being the person other Seniors check with.
Resume tells
Led something across team boundaries — a migration, a platform, a standard others adopted
Wrote a design doc or RFC that changed what multiple teams did
Named as the technical decision-maker on something with real money or risk attached
Can describe a project they killed, or argued down, as readily as ones they shipped
Evidence of writing and persuasion, not just building
Title inflation risk
Overloaded in both directions. At a 60-person company, Staff often means 'our best Senior'. At a large company it's a distinct job with an organisational remit. Also frequently self-applied on resumes with no title behind it — 'acted as Staff' usually means Senior.
Calibration questions
“Tell me about a technical decision that affected teams outside your own. How did you get people who don't report to you to go along with it?”
“What's something the org was about to do that you argued against? What happened?”
“Describe a problem you chose to work on that nobody assigned you.”
Where this goes wrong
Screened as a more senior Senior, against depth in one area, when the job is breadth and judgement across several. A Staff engineer who has spent two years aligning three teams on a migration may look, on a resume, like they shipped less than a Senior who stayed heads-down — and shipping less personally is sometimes exactly what the role required. (For the Staff-versus-manager confusion, see the fork below.)
Years of experience: 8+ years typically, but time served is close to irrelevant here. Plenty of excellent engineers stay Senior by choice and never do the organisational half of this job.
Staff or manager? The fork
Staff engineers and Engineering Managers both work across team boundaries and both influence people who don't report to them, so their resumes can read almost identically. The difference is not seniority — they are peer rungs at most companies. It's where the leverage comes from: a Staff engineer's comes from technical judgement and the documents and designs that carry it; an EM's comes from the people they hire, grow and organise.
“Have you had direct reports, and do you want them?”
A Staff engineer's impact story ends in a technical decision that changed what teams built. An EM's ends in a team that shipped, grew, or stopped losing people.
Ask what they'd want to spend a Tuesday on. Staff-inclined people describe a problem; management-inclined people describe their team.
Someone who moved to management and back to IC is not a red flag — it's one of the more useful things a candidate can tell you about themselves, and it's usually deliberate.
Player-coach roles — 'you'll manage four people and still code half the time' — satisfy neither track and are a common source of one-year attrition. If a req reads like that, it's worth establishing with the hiring manager which half they'd sacrifice under pressure, because they will have to.
Where was the title earned?
The same title means different things at different companies. Apply this before believing the level on a resume.
Seed / early startup (under ~50 people)
Titles are recruiting currency and cost nothing to give. 'Senior' often means 'third engineer hired'. Scope can genuinely be large — they may have built whole systems alone — but calibration against a wider bar has never happened.
“How many engineers were at the company when you joined, and when you left?”
Growth-stage (~50-500 people)
The ladder is usually being invented while people are on it. Titles are often regularised in a single re-levelling event, so the same person can be Mid one quarter and Senior the next without the job changing.
“Was there a re-levelling or a formal promotion process, and where did you land in it?”
Large tech company with a calibrated ladder
Titles mean something specific and were defended in a promotion committee. A Senior here has been measured against a written bar. This is the most reliable title signal you'll get — and the reason level codes (L5, IC3) are worth asking for.
“What level were you at, in your company's internal terms, and when were you last promoted?”
Agency, consultancy or outsourcing firm
Titles are often client-facing and inflate to justify billing rates. Scope tends to be broad but shallow — many projects, rarely owning anything after handover. The 'operate it after launch' evidence that separates Senior from Mid is frequently missing, through no fault of theirs.
“Which of those projects did you stay on after go-live, and what did you have to fix?”
Non-tech company (bank, retailer, manufacturer, public sector)
Ladders are often HR-wide rather than engineering-specific, and titles can be tied to tenure or grade rather than scope. Deep domain expertise is common; exposure to modern tooling and fast release cycles may not be.
“How often did your team release, and who decided when something shipped?”