Google Software Engineer Career Ladder
Every level of Google's software engineering ladder from L3 to L8 — typical timelines, what changes at each level, why engineers get stuck, and how promotions actually work.
Last updated: 2026-03-23
Aiming for your next level at Google?
Get a personalized promotion plan with AI coaching.
Level Overview
| Level | Title | Typical Years | Median TC | Terminal? |
|---|---|---|---|---|
| L3 | Software Engineer II | 1–3 yr | $191K | No |
| L4 | Software Engineer III | 1.5–2.5+ yr | $296K | Yes |
| L5 | Senior Software Engineer | 2–4+ yr | $423K | Yes |
| L6 | Staff Software Engineer | 3–5+ yr | $620K | Yes |
| L7 | Senior Staff Software Engineer | 4–6+ yr | $900K | Yes |
| L8 | Principal Engineer | 5–8+ yr | $1300K | Yes |
Promotion Cycle
Frequency
Twice yearly (March and September)
Decision Maker
committee
Manager-driven, committee-decided. Your manager assembles a promotion packet (self-review, peer reviews, manager assessment) and presents it to a calibration committee. The committee reviews the packet and decides. For L6+, an additional second committee automatically reviews all approved promotions.
Key Details
- •March is the primary cycle, September is the 'off cycle'
- •Manager nominates you and writes your packet — or you self-nominate, but the manager still writes the narrative
- •Peer reviewers are selected by you and approved by your manager
- •Committee members read your packet cold — they don't know you
- •GRAD performance ratings (Significant/Outstanding/Transformative Impact) are deliberately disconnected from promotions
- •Minimum 6 months in role before eligibility
- •Google uses lagging promotions — you must demonstrate next-level work for ~6 months before promotion
- •Promotion budget is explicitly capped per cycle — even qualified candidates may wait
L3 — Software Engineer II
Junior / New GradEntry point for new grads. You work on individual tasks within a feature with guidance from more senior engineers. Your manager breaks down problems for you, and you execute.
Typical Time at Level
1–3 years (typical: ~1.5 years)
Total Compensation (US)
$170K–$220K (median: $191K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Staying in a comfort zone — only taking tasks you already know how to do
- •Not owning features end-to-end — always implementing parts of someone else's project
- •Weak communication — doing good work but not surfacing it
- •Over-reliance on mentors when you could figure things out independently
L4 — Software Engineer III
Mid-LevelFirst level of true independence. You own features end-to-end, contribute to design docs, and work without someone scoping every task. Your manager gives you a problem, not a solution.
Typical Time at Level
1.5–2.5+ years (typical: ~2.5 years)
Total Compensation (US)
$260K–$340K (median: $296K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Working on L4-scope projects only — no amount of excellent L4 execution gets you to L5
- •No design doc with your name on it — the promo committee expects to see one
- •No evidence of growing others — L5 is the first level where mentorship is expected
- •Manager misalignment — manager support is described as 'at least 85% of the game'
- •Project cancellation or reorg wiping out months of L5-scope work
- •Unquantifiable impact — the committee wants measurable results
- •Generic peer feedback that doesn't help your case
- •Promotion budget constraints — even if you meet requirements, slots may be exhausted
L5 — Senior Software Engineer
SeniorTeam-level scope and impact. You own medium-to-large projects, author design docs, mentor L3/L4 engineers, and operate with little direction. Cross-team collaboration is expected. This is the most common level at Google.
Typical Time at Level
2–4+ years (typical: ~4 years)
Total Compensation (US)
$370K–$500K (median: $423K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Continuing to operate at team scope instead of driving organization-level impact
- •Not creating scope — solving known problems instead of identifying new ones
- •Doing all the work yourself instead of leading through others and delegation
- •No cross-team design artifacts showing architectural influence beyond your team
- •Not growing L5 peers — at L6 you're expected to develop senior engineers
- •L6+ promotion budget explicitly capped since 2023
L6 — Staff Software Engineer
StaffOrganization-wide scope. You create scope by identifying problems no one has named yet, work through others via delegation and influence, and set technical direction across multiple teams. Equivalent level to engineering managers. Promotion faces multi-committee review and explicit budget caps.
Typical Time at Level
3–5+ years (typical: ~5 years)
Total Compensation (US)
$520K–$750K (median: $620K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Impact limited to a single team or product area
- •Not influencing technical direction at the org level
- •Lacking VP-level visibility into your work
- •No evidence of growing the organization (recruiting, team health, L5 development)
L7 — Senior Staff Software Engineer
Senior StaffMulti-org scope. You define technical strategy across multiple organizations, drive company-wide initiatives, and are recognized as a domain authority. Very few ICs reach this level.
Typical Time at Level
4–6+ years (typical: ~6 years)
Total Compensation (US)
$750K–$1100K (median: $900K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Scope limited to a single organization
- •Not driving company-level technical strategy
- •Insufficient external visibility and industry recognition
L8 — Principal Engineer
PrincipalCompany-wide scope. You shape Google's technical direction, define multi-year strategies, and are among the most senior individual contributors in the company. Extremely rare — fewer than 1% of engineers.
Typical Time at Level
5–8+ years (typical: ~8 years)
Total Compensation (US)
$1000K–$1600K (median: $1300K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Requires sustained company-wide impact over many years
- •Must be recognized industry-wide as a technical authority
Additional Context
Google's GRAD system (Googler Reviews and Development) replaced the old PERF system in May 2022. Performance ratings and promotions are deliberately separate processes. In 2023, Google announced fewer promotions to L6+ senior roles. In 2025, Google expanded the Outstanding Impact rating to reward more top performers with higher bonuses.
Data sourced from Team Blind (verified Google employees), Promotions.fyi, Levels.fyi, Developing.dev, Hacker News (ex-Googler threads), and CNBC. Compensation figures from Levels.fyi. Last verified March 2026.