Senior vs Staff Scope

The levels differ in the size of the unit of work someone can be handed and trusted with.

A mid-level engineer takes a well-specified ticket and lands it. The problem has already been framed by someone else; the skill on display is execution.

A senior engineer takes an outcome — "make onboarding not lose people at step three", "we need billing" — and produces the plan, the design, the code, the rollout, and the follow-up. They break the ambiguity themselves, decide what's out of scope, and surface the trade-offs to the people who need to weigh in. Crucially, the failure modes are theirs to anticipate: they're the one who noticed the migration needed a backfill.

A staff engineer's scope crosses teams and quarters. The work stops being a project and becomes a direction: which of the five things we could do actually matters, what technical strategy do we commit to, whose roadmap has to change. Will Larson's archetypes are useful shorthand here — Tech Lead, Architect, Solver, Right Hand — because they make it obvious that "staff" isn't one job and that the title is granted for company impact, not for skill.

At a twenty-person AI startup these boundaries blur badly. The senior engineer is the architect and often the solver, because there's nobody else. That's an advantage in interviews if you can name the scope precisely rather than claiming the title.

Levelling is decided in the first two rounds, largely from how you describe past work, and it's the single biggest lever on both comp and how interesting the job is. Describing genuinely senior work in mid-level language — "I was assigned", "my lead decided" — gets you downlevelled by people who never doubted your coding ability. The fix is not inflation; it is being accurate about which decisions were actually yours.

• Level tracks the ambiguity you can absorb, not tenure, headcount, or lines shipped.
• Mid-level lands a specified task; senior owns an outcome end to end including its failure modes; staff decides which outcomes are worth pursuing across teams.
• Staff is not one role — Tech Lead, Architect, Solver, and Right Hand are different jobs with the same title.
• Titles are company-relative: a startup senior often does architect work, and a big-company senior often does not.
• Interviewers infer level from the verbs in your stories — "decided", "scoped", "convinced" read differently from "helped", "was asked to", "worked on".
• Small companies grant scope faster than titles; say what you owned and let them do the mapping.
• Claiming a level you can't back with a story is worse than claiming a lower one and exceeding it.