Engineer Levels Overview¶
Understand what each engineering level means in real companies.
The 9 Core Roles (Typical Tech Company)¶
graph TD
A["Junior Engineer<br/>0–2 years<br/>🟢 IC Track"]
B["Mid-Level Engineer<br/>2–5 years<br/>🟡 IC Track"]
C["Senior Engineer<br/>5–8 years<br/>🟡 IC Track"]
D["Staff Engineer<br/>8–12 years<br/>🔴 IC Track"]
E["Engineering Manager<br/>5–12 years<br/>🟡 Mgmt Track"]
F["Tech Lead<br/>5–10 years<br/>🟣 Hybrid"]
G["Director<br/>10–15 years<br/>🔴 Mgmt Track"]
H["VP Engineering<br/>12–20 years<br/>🔴 Executive"]
I["CTO<br/>15–25 years<br/>🔴 Executive"]
A --> B
B --> C
C --> D
C --> E
C --> F
D --> G
E --> G
F --> G
G --> H
H --> I
style A fill:#90EE90
style B fill:#FFEB3B
style C fill:#FFA726
style D fill:#EF5350
style E fill:#EF5350
style F fill:#AB47BC
style G fill:#5E35B1
style H fill:#1A237E,color:#fff
style I fill:#000000,color:#fff
Quick Reference Table¶
| Level | Years | Role | Reports | Annual Comp | Key Metric |
|---|---|---|---|---|---|
| Junior Engineer | 0–2 | Learning, shipping code | 0 | $130–180K | Learning + Code Quality |
| Mid-Level Engineer | 2–5 | Owning features, mentoring | 0 | $150–250K | Impact + Mentoring |
| Senior Engineer | 5–8 | System design, cross-team | 0–1 | $220–400K | Scope + Influence |
| Staff Engineer | 8–12 | Org-wide technical strategy | 0 | $300–600K+ | Technical Direction |
| Engineering Manager | 5–12 | Team building, people dev | 5–12 | $250–450K | Team Health + Delivery |
| Tech Lead | 5–10 | Technical + people leadership | 0 (leads 3–8) | $220–350K | Team + Technical Impact |
| Director | 10–15 | Multi-team strategy | 2–8 managers | $350–700K+ | Org Impact + Goals |
| VP Engineering | 12–20 | Org strategy, exec alignment | Directors | $500–1M+ | Org Health + Alignment |
| CTO | 15–25 | Technology vision, board | VPs | $800–3M+ | Company Tech Strategy |
Compensation ranges are illustrative U.S. Big Tech / top-tier total comp reviewed in November 2026, not market averages. Check the rolling Levels.fyi benchmark for current IC data and company/location filters; management and executive roles vary more.
Above Staff: The Full IC Ladder¶
Staff is not the top of the IC track. Larger companies continue with:
| IC Level | Rough Management Equivalent | Typical Scope |
|---|---|---|
| Senior Engineer | — | Team / service |
| Staff Engineer | Engineering Manager | Multiple teams / a domain |
| Senior Staff Engineer | Senior Engineering Manager | A large org area |
| Principal Engineer | Director | Org / division-wide |
| Distinguished Engineer / Fellow | VP | Company-wide or industry-wide |
How AI Is Changing the Ladder (2026)¶
AI coding assistants and agents can draft code, tests, and docs at every level. But faster generation does not guarantee faster delivery: review, integration, testing, and rework still take time. The ladder still exists, and evidence of impact matters more than output volume.
| Level | Less Differentiating Than Before | More Differentiating Than Before |
|---|---|---|
| Junior | Typing speed, boilerplate, syntax recall | Verifying AI output, debugging, asking precise questions, fundamentals |
| Mid / Senior | Raw feature throughput | Design quality, review rigor, owning outcomes in production |
| Staff+ | Writing every prototype yourself | Choosing which problems to solve, setting guardrails for AI use, architecture |
| Managers / Execs | Headcount as the measure of scope | Team effectiveness, AI adoption strategy, security & governance, cost |
What current evidence says
DORA's 2025 research describes AI as an amplifier of existing organizational strengths and weaknesses, not a fix for them. METR's February 2026 research update explains why developer-productivity effects remain difficult to measure reliably: its early-2025 experiment found a slowdown in one experienced open-source setting, while later results did not establish a reliable universal uplift. Measure your own outcomes instead of assuming AI saves time.
Practical takeaway: use AI deliberately, keep changes reviewable, and be able to explain, test, and defend every line you ship. Track quality, rework, review effort, and delivery outcomes—not suggestion acceptance or generated-line counts. "The AI wrote it" is never an acceptable answer in review or an incident postmortem.
Why Levels Matter¶
For You¶
- Understand expectations at your current level
- Know what skills to develop for next level
- Benchmark compensation
- Plan your 5-year growth
For Your Manager¶
- Clarity on what "Senior" means
- Framework for promotions
- Fair, consistent evaluation
For Your Company¶
- Predictable career progression
- Reduced confusion about roles
- Clearer hiring targets
Two Valid Growth Paths¶
Individual Contributor (IC) Track¶
- Stays hands-on — writing code, designing systems
- Broader influence — affects org through expertise, not hierarchy
- Examples: Staff Engineer → Principal Engineer → CTO (if deep enough)
- Pros: Keep coding and set technical direction, with compensation comparable to management at equivalent levels
- Cons: Harder to influence non-technical decisions, less "prestige" in some orgs
Management Track¶
- Leads people — hiring, mentoring, performance management
- Business influence — understands revenue, customers, strategy
- Examples: Manager → Director → VP → CTO
- Pros: Broader organizational impact, traditional leadership path
- Cons: Less coding, more meetings, requires people skills
Hybrid Track (Tech Lead)¶
- Combination — technical authority + mentoring and coordination; formal reports only in a Tech Lead Manager role
- Sweet spot — some IC work, some mentoring
- Duration: Usually 3–5 years before choosing IC or Management
- Pros: Best of both, test management fit
- Cons: Ambiguous, easy to burn out, hard to evaluate
The Decision Point (Years 5–8)¶
At Senior Engineer, you choose:
| Decision | Path | Impact |
|---|---|---|
| "I love coding and system design" | IC Track → Staff Engineer | Deep technical authority |
| "I love growing people" | Management → Engineering Manager | Build teams |
| "I want both for now" | Tech Lead | Make decision in 3–5 years |
This choice is not permanent. You can:
- Manager → Senior Engineer (harder, but possible)
- Staff Engineer → Manager (takes adjustment)
- Tech Lead → either (that's the point)
Myths Debunked¶
Myth: Management is the only path to CTO
False. You can become CTO as a Principal Engineer if you combine deep technical expertise with business understanding.
Myth: You should reach Senior Engineer in 3 years
False. It typically takes 5–8 years. Rushing = missing foundations.
Myth: Promotions happen automatically.
False. You need to demonstrate the next level's impact for 6–12 months before promotion.
Myth: More levels = always better.
False. Staff Engineer at a 200-person company might have more impact than Director at a 5,000-person company.
Myth: You can't move between IC and management after 5 years.
False. Switching is common in the first decade and still doable later if you have the skills — many strong leaders have "pendulumed" between IC and management more than once.
Key Insight: Impact Over Title¶
Two engineers with the same title can have VERY different impact:
- Junior at a startup might own an entire system
- Senior at Big Tech might own one service
The levels in this guide define expected impact, not title. Your job is to understand what you're actually doing.
What if my company doesn't follow this structure?
Most companies deviate. Use the skills and impact descriptions, not titles. Ask your manager: "What does the next level look like here?"
Can I skip a level?
Very rarely. Most companies expect progression through levels. When it does happen, it's usually at a job change (being hired in at a higher level) rather than an internal promotion.
What if I plateau?
Normal. You might be at your optimal level. Talk to your manager about deepening expertise within your level.
Next: Choose your path. Start with Junior Engineer if you're new.