Levels and expectations
The four leveling axes
Scope, autonomy, technical complexity and influence — the four questions every engineering ladder is really asking.
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.
Once you see levels as those four axes, titles at different companies stop looking random, and you can diagnose why you feel stuck.
The big idea
Almost every serious engineering ladder collapses into the same four dimensions. Names differ; the questions do not.
| Axis | Question the ladder is asking |
|---|---|
| Scope | How big is the thing you own — a task, a feature, a multi-team project, an org-level problem? |
| Autonomy / ambiguity | How complete is the problem statement when it lands on you? Who defines success? |
| Technical complexity | How deep or novel is the engineering — local change, careful design, hard distributed or performance work? |
| Influence | Whose behavior changes because of you — your PR, your team, peer teams, the engineering org? |
Concept
Scope is the radius of responsibility: what breaks if you disappear for two weeks. A ticket has tiny scope. A product surface used by every customer has large scope. Scope is not the same as hours worked; a narrow, critical auth path can outrank a wide but cosmetic UI sweep.
These axes move together but not in lockstep. You can have high technical complexity and narrow scope (deep optimization in one service). You can have wide scope and moderate complexity (coordinating a migration that is mostly careful execution). Promotion usually wants progress on several axes, not a spike on one.
Walking through a score
Use this 1–4 scale on real work, not vibes.
| Score | Scope | Autonomy | Complexity | Influence |
|---|---|---|---|---|
| 1 | Single ticket | Steps provided | Local change | Own PR |
| 2 | Feature slice | How mostly clear | One service, known patterns | Team reviews |
| 3 | Feature / small project end to end | You clarify how | Cross-cutting or careful migration | Team direction in an area |
| 4 | Multi-quarter / multi-team | Ambiguous problem | Hard novel or high-risk systems | Peer teams / org practices |
Be brutal about consistency. One heroic on-call save is a story; a year of closing loops is a level. Calibration committees look for a pattern, not a peak. Worked scoring of recent projects lives in leveling self-assessment. See also how promotion works.
Common mistakes
- Scoring hours instead of radius. Busy is not scope.
- Spiking one axis. A clever algorithm in a tiny box is not a promotion case by itself.
- Confusing title with axes. A "senior" who only closes tickets is mid-level work with a senior sticker.
Check yourself
You spent six months optimizing one query in one service. Which axis is high, and which is probably not?
Complexity is high. Scope and influence are probably still narrow.
A manager says you "work really hard." What should you ask for instead?
Work scored on scope, autonomy, complexity and influence — not hours.
Key takeaways
- Levels describe problems you can be trusted with, not years or lines of code.
- The four axes are scope, autonomy, complexity and influence.
- Axes move together but not in lockstep. Promotion wants several, consistently.
- Score recent work with evidence. A peak is a story; a pattern is a level.
Further learning
Next, see how those axes look at junior and SDE2.
Related
What the levels mean
Junior, SDE2, SDE3 and staff: scope, autonomy, impact and influence at each level.
Junior and SDE2
Juniors finish well-scoped work cleanly. SDE2s own features end to end without someone breaking the work into steps.
Growing your scope
From tasks to features to projects to problems: finding and taking on higher-leverage work.