Levels and expectations
What the levels mean
Junior, SDE2, SDE3 and staff: scope, autonomy, impact and influence at each level.
Promotion conversations go wrong when people argue about years of experience or lines of code. Ladders are not calendars. They are descriptions of what problems you can be trusted with, how much clarity you need before you start, how hard the work is technically, and how far your decisions ripple.
This page is the map. Use it to read your current role honestly, to aim the next six months of work, and to translate between "SDE2 at Amazon," "L4 at Google," and "Senior at a 40-person startup" without getting lost in title inflation.
Once you see levels as four axes — scope, autonomy, technical complexity and influence — titles at different companies stop looking random.
Concepts in this section
Read them in order. Each one builds on the one before.
| Step | Concept | What it answers |
|---|---|---|
| 1 | The four leveling axes | What is the ladder actually measuring? |
| 2 | Junior and SDE2 | What does reliable independent delivery look like? |
| 3 | Senior and staff | When does the job tilt from features to ambiguous bets? |
| 4 | Mapping titles across companies | How do you translate "senior" between firms? |
| 5 | Leveling self-assessment | How do you grade yourself with evidence? |
Staff details live in the path to SDE3 and beyond. Promotion mechanics live in how promotion works.
A worked contrast
Same API, two shapes of work.
- A junior adds rate-limit headers after a senior writes a short design. Scope and autonomy stay low. That is appropriate.
- An SDE2 is asked to "reduce abuse on the public search endpoint." They pull metrics, propose a design, implement, add dashboards, roll out behind a flag, and write a runbook. Nobody assigned the subtasks.
The domain did not change. The axes did. That is the whole map in one picture. On a healthy team you should be able to name your current level, the written next-level bar, and the evidence that would convince your manager.
Common mistakes
- Arguing years or lines of code. The ladder is about problems you can be trusted with.
- Spiking one axis. Deep optimization in a tiny box is not a senior case by itself.
- Trusting title strings. A senior sticker on ticket work is still mid-level work.
- Grading on vibes. Committees want a pattern of evidence, not a peak.
Key takeaways
- Levels are about scope, autonomy, complexity and influence — not years or LOC.
- Junior: well-scoped tasks, learning the system, growing independence.
- SDE2: owns features end to end with little how-guidance; reliable delivery and operable services.
- SDE3: owns ambiguous, multi-quarter problems; sets direction; multiplies the team.
- Staff is a different job shape, not a longer senior.
- Self-assess with a public ladder and evidence from recent work.
Further learning
Public ladders you can actually grade yourself against:
Dropbox Engineering Career Frameworkdropbox.github.io progression.fyi — career frameworks collectionCareerminds helps organizations build clear, scalable job architecture that boosts engagement and retention. Empower employees with visible growth paths, skill progression, and our ready-to-use templates.Careerminds levels.fyi — levels and compensation mappingSearch 1M+ data points for different companies, job titles, career levels, and locations. Explore our tools to help you get paid more!Levels.fyi
Will Larson on what staff work looks like in practice:
Related
Growing your scope
From tasks to features to projects to problems: finding and taking on higher-leverage work.
How promotion works
Evidence, packets, calibration and the manager conversations that turn next-level work into a title.
The path to SDE3 and beyond
What senior engineers do differently: technical leadership, multiplying others and owning ambiguity.