Meta Software Engineer Career Ladder
Every level of Meta's software engineering ladder from E3 to E9 — typical timelines, up-or-out policies, what changes at each level, and how the PSC review process drives promotions.
Last updated: 2026-03-23
Aiming for your next level at Meta?
Get a personalized promotion plan with AI coaching.
Level Overview
| Level | Title | Typical Years | Median TC | Terminal? |
|---|---|---|---|---|
| E3 | Software Engineer (Entry) | 1–2 yr | $175K | No |
| E4 | Software Engineer (Mid-Level) | 1.5–3 yr | $260K | No |
| E5 | Senior Software Engineer | 2–4+ yr | $440K | Yes |
| E6 | Staff Software Engineer | 3–5+ yr | $650K | Yes |
| E7 | Senior Staff Software Engineer | 4–6+ yr | $1000K | Yes |
| E8 | Principal Engineer | 5–8+ yr | $1500K | Yes |
Promotion Cycle
Frequency
Annual review with mid-year check-in (moving to 2 full cycles per year under 2026 Checkpoint program)
Decision Maker
hybrid
Manager-driven with calibration committee approval. During the Performance Summary Cycle (PSC), you write a self-review (~1,000 words), collect peer feedback from 3-5 nominators, and your manager writes their assessment. The manager then presents your packet at calibration, where it's evaluated against peers at your level.
Key Details
- •Four performance dimensions: Project Impact, Direction, Engineering Excellence, People
- •Rating scale: Redefines (~3%), Greatly Exceeds (~7%), Exceeds (~35%), Meets All (~45%), Meets Most (~8%), Meets Some (~2%)
- •Two consecutive Meets Most ratings trigger automatic PIP
- •Up-or-out: E3→E4 within 24 months, E4→E5 within 33 months
- •Manager is the sole advocate in calibration — relationship quality directly affects outcomes
- •Workplace posts (Meta's internal social network) serve as evidence in reviews
- •2026 Checkpoint program: 2 review cycles per year, bonuses up to 300% for top performers
- •External leverage can play a significant role in promotions at E5+
E3 — Software Engineer (Entry)
Junior / New GradStandard new-grad entry point. You work under guidance on individual tasks and small bug fixes. Your manager breaks down problems for you. Up-or-out policy: you have 24 months to reach E4.
Typical Time at Level
1–2 years (typical: ~1.5 years)
Total Compensation (US)
$155K–$200K (median: $175K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Not owning features end-to-end — staying in task-execution mode
- •Weak communication — not surfacing your work via Workplace posts or status updates
- •Not building independence — relying on your manager for every decision
- •Up-or-out clock creates real pressure — 24 months is the deadline
E4 — Software Engineer (Mid-Level)
Mid-LevelFirst level of true independence. You own features end-to-end, contribute to design docs, and are expected to demonstrate growing scope. Up-or-out policy: 33 months to reach E5 from when you reached E4.
Typical Time at Level
1.5–3 years (typical: ~2.5 years)
Total Compensation (US)
$230K–$300K (median: $260K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Not demonstrating impact across the four review dimensions (Project Impact, Direction, Engineering Excellence, People)
- •Calibration opacity — your manager defends your packet against peer managers, and results often differ from expectations
- •Manager dependency — a weak manager relationship means a weak defense in calibration
- •Meets Most trap — one MM rating triggers a 6-month check-in; two consecutive MM ratings trigger automatic PIP
- •Impact vs. visibility tension — strong technical work that isn't documented and socialized gets lower ratings
- •Up-or-out pressure — 33-month timeline creates anxiety
E5 — Senior Software Engineer
SeniorSenior-level scope. You lead medium-to-large projects, mentor junior engineers, drive technical decisions, and demonstrate cross-team influence. The up-or-out pressure ends here — E5 is a terminal level.
Typical Time at Level
2–4+ years (typical: ~4 years)
Total Compensation (US)
$380K–$530K (median: $440K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Not generating org-level impact — staying within team boundaries
- •Not developing leadership skills (Direction and People dimensions)
- •Competing for limited Staff slots — E6 promotion is rare and highly contested
- •Not leveraging external offers — at this level, leverage plays an increasing role
E6 — Staff Software Engineer
StaffOrganization-wide scope. You drive cross-team technical strategy, influence without authority, and make high-impact architectural decisions. Very selective — promotion from E5 to E6 is one of the hardest jumps in tech.
Typical Time at Level
3–5+ years (typical: ~5 years)
Total Compensation (US)
$530K–$800K (median: $650K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Impact scoped to a single team or product
- •Not shaping technical direction at the org level
- •Lacking executive-level visibility
E7 — Senior Staff Software Engineer
Senior StaffMulti-org scope. You define technical strategy across multiple organizations and are recognized as a domain authority within Meta. Extremely few ICs reach this level.
Typical Time at Level
4–6+ years (typical: ~6 years)
Total Compensation (US)
$800K–$1300K (median: $1000K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Scope limited to a single organization
- •Not driving company-level technical initiatives
E8 — Principal Engineer
PrincipalCompany-wide scope. Among the most senior individual contributors at Meta. You shape company-wide technical direction and define multi-year strategies.
Typical Time at Level
5–8+ years (typical: ~8 years)
Total Compensation (US)
$1200K–$1900K (median: $1500K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Requires sustained company-wide impact over many years
- •Must be recognized as a leading technical authority
Additional Context
Meta's PSC (Performance Summary Cycle) is the core review system. In 2026, Meta is rolling out the Checkpoint program — two full review cycles per year with restructured bonus/equity distribution. Meta is known for its up-or-out culture at lower levels and a review system where calibration outcomes sometimes differ from manager signals. The Meets Most trap is unique to Meta and drives significant anxiety.
Data sourced from TeamRora (65+ Meta client data), Team Blind (verified Meta employees), Levels.fyi, Perplexity research synthesis. Compensation figures from Levels.fyi. Last verified March 2026.