Levels and expectations
Senior and staff
Senior owns ambiguous multi-quarter problems and multiplies the team. Staff is a different job shape, not a louder senior.
Senior (often SDE3 at Amazon-style ladders, L5 at Google, E5 at Meta, IC3 at Dropbox) is where the job tilts from executing features to owning ambiguous problems and multi-quarter bets. You still write code — often a lot of it — but the scarce skill is choosing the right problem shape and making the team successful at it.
Staff is not "senior but louder." Scope jumps again: org-level or company-level problems, often years of work, often without a tidy ticket queue.
Concept
You need the four axes first. Senior and staff are high scores on several axes at once — especially autonomy and influence — not a medal for tenure.
SDE3 / senior
| Axis | Senior |
|---|---|
| Scope | Multi-week to multi-quarter projects; sometimes work that spans a few teams. You define milestones, not just tickets. |
| Autonomy | High ambiguity. "Search quality is slipping" lands on you. You turn it into options, a plan and a shipped outcome. |
| Complexity | Harder systems work — cross-service designs, migrations, nontrivial reliability, API contracts other teams depend on. |
| Influence | You set technical direction for a team or a problem area. Your absence is felt in planning, not only in a queue. |
Trade-off
Deep individual execution vs multiplying the team. Seniors who only hero-code become bottlenecks; seniors who only facilitate without technical depth lose the plot. Default: keep a hands-on stake in the hardest path, and spend the rest of your leverage on design clarity and unblocking. Pure people-management is a different job.
Amazon's public-ish guidance for moving SDE2 → SDE3 emphasizes leading a complex project from design, influencing longer-term technical direction, and making space for others — not merely stacking years.
Staff and beyond, briefly
Influence is how engineering works, not only what one team ships. Will Larson's StaffEng archetypes are a useful shorthand:
| Archetype | What they optimize for |
|---|---|
| Tech lead | A team's outcomes; glue, sequencing, quality bar |
| Architect | A domain's technical direction across teams |
| Solver | The hard, messy problem nobody else can close |
| Right hand | Amplifying an executive or org leader's engineering agenda |
You do not need to pick an archetype as an SDE2. You need to know that staff is a different shape of job. Details live in the path to SDE3 and beyond.
Walking through a story that levels
Weak: "I was senior-titled."
Strong: "I took an underspecified reliability problem, proposed three options, led a two-quarter migration affecting four teams, and mentored two engineers through the cutover."
That sentence scores scope, autonomy, complexity and influence. Interviewers and calibration committees hear it. Years-of-experience arguments they do not.
Common mistakes
- Hero-coding as the whole job. You become the bottleneck and the team does not grow.
- Facilitating with no technical stake. You lose the plot on the hardest path.
- Treating staff as a longer senior. It is a different shape: org problems, not a louder ticket queue.
Check yourself
Someone says "search quality is slipping" and walks away. What does a senior do next?
Turn it into options, a recommendation, a plan and a shipped outcome — not wait for tickets.
Name one staff archetype that is not "the team's best coder."
Tech lead, architect, solver, or right hand — each optimizes for a different kind of leverage.
Key takeaways
- Senior owns ambiguous, multi-quarter problems; sets direction; multiplies the team.
- Keep a hands-on stake in the hardest path. Do not only hero-code or only facilitate.
- Staff is a different job shape (tech lead, architect, solver, right hand), not a longer senior.
- Translate stories into axes, not titles.
Further learning
Next, why "senior" maps badly across companies: title mapping.
Will Larson on what staff work looks like:
Related
What the levels mean
Junior, SDE2, SDE3 and staff: scope, autonomy, impact and influence at each level.
The path to SDE3 and beyond
What senior engineers do differently: technical leadership, multiplying others and owning ambiguity.
Junior and SDE2
Juniors finish well-scoped work cleanly. SDE2s own features end to end without someone breaking the work into steps.