The engineering ladder rubric: levels, dimensions, and examples that hold up to scrutiny
Engineering ladders rot when they're too vague to differentiate adjacent levels or too rigid to apply across disciplines.
- 5-7 IC levels and 4-5 manager levels mapped together. More than that = theatre.
- Five common dimensions: technical depth, scope, complexity, impact, leadership.
- Per role family (backend, frontend, ML, infra, security), examples are written by current engineers at that level.
- Stress-test annually: run 3 packets through the rubric blind; if results match prior calibration, rubric agrees with practice.
An engineering ladder is the single document your engineers read most carefully — and most cynically. It must be precise enough to differentiate, broad enough to fit across disciplines, and refreshed often enough to feel current.
Structure: levels + dimensions
| Level | Common label | Years (rough) | Scope |
|---|---|---|---|
| L1-L2 | Engineer / Engineer II | 0-3 | Task → feature |
| L3 | Senior Engineer | 3-6 | Feature → service |
| L4 | Staff Engineer | 6-10 | Service → team domain |
| L5 | Senior Staff | 8-12+ | Team domain → cross-team area |
| L6 | Principal | 10+ | Cross-team area → company-wide architecture |
| L7 | Distinguished / Fellow | Rare | Industry-shaping |
Examples per discipline
- 1Backend L4Owns a service that processes >10M req/day with documented SLO; mentors 2-3 ICs; drives a quarterly architecture review.
- 2Frontend L4Owns the platform shared by 4+ teams; drives accessibility + perf budgets; design-system steward.
- 3ML L4Owns a production model in revenue-critical path with monitoring + rollback; drives experimentation discipline.
- 4Infra L4Owns multi-region runtime for production services; on-call lead; drives incident reduction targets.
- 5Security L4Owns threat model + control posture for a product area; drives security review; partners with product on roadmap.
Across role families
- Shared rubric (5 dimensions, level descriptors).
- Discipline-specific examples maintained by a working group of current engineers at that level.
- Cross-discipline calibration once a year — read packets across families.
- Mobility: moving from backend L4 to ML L4 is a real move; document expectations.
Annual review
- Working group of L4+ ICs + 2 managers refresh the rubric.
- Test against 3 recent packets blind. Compare to prior outcome.
- Update examples to current tech (LLM era examples ≠ 2020 examples).
- Publish changelog. Engineers read it more carefully than you think.
Read next
All playbooksMost companies say they have a dual ladder. Few actually do. Here's what 'real' looks like — equal pay, equal scope, equal status — and the four anti-patterns…
Leveling rubrics rot at scale. Here's the design pattern — common dimensions, function-specific examples, and the calibration discipline — that keeps the bar…
Promotions get political when the process is informal. Here's the end-to-end design — nomination, packet, committee, decision, communication — that holds up…