On this page
Meta Levels in One Table
E3: Software Engineer (Entry Level)
E4: Software Engineer (Intermediate)
E5: Senior Software Engineer
E6: Staff Software Engineer
E7 to E10: Senior Staff, Principal, Distinguished, Fellow
The Up-or-Out Rule, Explained
Hiring Levels and Negotiation at Meta
Frequently asked questions
Related reading
Meta Software Engineer Levels Explained: E3 to E10, Salaries, and Promotion


On This Page
Meta Levels in One Table
E3: Software Engineer (Entry Level)
E4: Software Engineer (Intermediate)
E5: Senior Software Engineer
E6: Staff Software Engineer
E7 to E10: Senior Staff, Principal, Distinguished, Fellow
The Up-or-Out Rule, Explained
Hiring Levels and Negotiation at Meta
Frequently asked questions
Related reading
Meta's software engineer levels run from E3 to E10. E3 is the entry level for new graduates, E5 is Senior Software Engineer, and E10 is Engineering Fellow. Only a few people have ever held that last level.
The E stands for Engineer, and the ladder covers individual contributors only. Managers sit on a parallel M ladder.
Two things make Meta's ladder different from other FAANG companies. First, junior engineers face an explicit expectation to reach E5 within about five years, often described as "up or out". Second, once you reach E5, the pressure stops completely. This guide explains each level, the pay, and how that promotion system works.
Meta Levels in One Table
| Level | Title | Typical Years of Experience | Approximate Total Pay (US) |
|---|---|---|---|
| E3 | Software Engineer (entry) | 0 to 2 | 150K to 180K |
| E4 | Software Engineer | 2 to 5 | 200K to 300K |
| E5 | Senior Software Engineer | 5 to 10+ | 300K to 500K |
| E6 | Staff Software Engineer | 8 to 15+ | $500K+ |
| E7 | Senior Staff Software Engineer | 12+ | high six figures |
| E8 | Principal Engineer | very rare | seven figures |
| E9 | Distinguished Engineer | fewer than 50 ever | $2.5M+ |
| E10 | Engineering Fellow | single digits | varies |
Pay figures are rough market averages that move with stock value and location. Treat them as a starting point and check levels.fyi for current data.
E3: Software Engineer (Entry Level)
E3 is where new graduates and engineers with up to two years of experience start.
An E3 writes production code for individual tasks with some guidance. The focus is solid coding, debugging, and learning fast inside a team.
Promotion: E3s are expected to reach E4 within about one and a half to two years. This is not optional at Meta; staying too long at E3 puts the role at risk.
E4: Software Engineer (Intermediate)
E4 is Meta's mid-level engineer, usually with two to five or more years of experience.
An E4 delivers complete features on their own. They write technical specs, work across teams, and mentor through code reviews. An E4 needs very little day-to-day direction.
Most engineers spend around two years here before the jump to E5, which requires proof of end-to-end ownership.
E5: Senior Software Engineer
E5 is the most important level on Meta's ladder, for one reason: it is the terminal level.
A terminal level is a level you can hold indefinitely without promotion pressure. Below E5, Meta expects steady progress. At E5, the expectation ends, and you can build a whole career there. Only about 15 percent of Meta engineers go beyond E5.
An E5 owns a problem area end to end. They set the technical direction for it, drive the work of others, and uphold the quality bar. Many first-line managers (M1) carry roughly the same scope.
Years of experience: typically five to ten or more, faster for high performers.
Compensation: roughly 300K to 500K total per year in the United States, including salary, bonus, and stock.
E6: Staff Software Engineer
E6 is Staff Engineer, a large jump in scope from E5.
An E6 influences engineering across multiple teams. They set roadmaps, make architecture decisions, and coordinate several engineers or projects as a technical lead. They are expected to raise the quality of the whole organization, not just their own team.
Reaching E6 usually takes eight to fifteen or more years of experience. Total pay is commonly above $500K.
E7 to E10: Senior Staff, Principal, Distinguished, Fellow
E7 (Senior Staff) engineers are about 3 percent of Meta's engineering population. Their impact spans an entire organization: they drive programs across many teams and plan two to three years ahead.
E8 (Principal) engineers have impact beyond Meta itself, often shaping how the industry approaches a technology. They are extremely rare and usually well-known names in their field.
E9 (Distinguished) has been reached by fewer than 50 engineers in Meta's history. Compensation can pass $2.5M per year.
E10 (Engineering Fellow) is the top of the ladder, held by single-digit numbers of people. Meta does not hire into E10; it is earned over a long career of historic contributions.
The Up-or-Out Rule, Explained
Meta expects engineers to progress from E3 to E5 in about four to five years. An engineer who stalls at E3 or E4 for too long is usually managed out.
This sounds harsh, but it has a clear logic: E5 is the level where Meta considers you a fully independent senior engineer. The company treats everything below it as a growth phase.
The rule cuts both ways for candidates. Joining at E4 with several years of experience puts you on a clock to demonstrate E5 scope. Joining at E5 removes the clock entirely. This makes the level you are hired at worth negotiating hard for.
Hiring Levels and Negotiation at Meta
Meta interviews you for a target level, and your loop is scored against that level's rubric:
- E3 and E4 loops center on coding speed and correctness.
- E5 and above add system design and behavioral rounds with real weight. Senior candidates fail more often on design than on coding.
Three practical points:
- Ask the recruiter for the target level and frame your stories at that scope: end-to-end ownership for E5, cross-team influence for E6.
- Meta E5 maps to Google L5, Amazon SDE III (L6), and Apple ICT4. Use a competing offer at those levels to argue for E5.
- Compensation bands overlap. A strong E4 offer can approach a low E5 offer, and initial stock grants are the most flexible part. Negotiate them separately from base.
The Meta software engineer interview handbook covers each round of the loop in detail.
Frequently asked questions
What is E5 at Meta? E5 is Senior Software Engineer, and Meta's terminal level. It requires end-to-end ownership of a problem area and typically five to ten years of experience. Total pay is roughly 300K to 500K per year in the United States.
What does "up or out" mean at Meta? Engineers below E5 are expected to keep getting promoted, reaching E5 within about five years of joining as E3. Engineers who stall below E5 are usually managed out. The expectation ends at E5.
How does Meta E4 compare to Google L4? They are equivalent. Both are mid-level engineers with roughly two to five years of experience who deliver features independently. Meta E5 likewise matches Google L5.
How many Meta engineers reach E6 or higher? Roughly 15 percent of Meta's engineers are E6 or above. E7 is about 3 percent, and E8 and beyond are a small fraction of one percent.
What is the salary of a Meta E6 engineer? Total compensation for E6 commonly passes $500K per year, with stock as the largest component. E7 reaches the high six figures, and E8 and above reach seven figures.
Does Meta down-level external candidates? It can happen, usually when the interview loop shows senior coding skills but weak system design. Preparing design and leadership stories at your target level is the best protection.
If you have an offer and want to negotiate the level or the package, Grokking Tech Salary Negotiations gives you the scripts for that conversation.
Related reading
What our users say
Eric
I've completed my first pass of "grokking the System Design Interview" and I can say this was an excellent use of money and time. I've grown as a developer and now know the secrets of how to build these really giant internet systems.
KAUSHIK JONNADULA
Thanks for a great resource! You guys are a lifesaver. I struggled a lot in design interviews, and Grokking System Design gave me an organized process to handle a design problem. Please keep adding more questions.
Arijeet
Just completed the “Grokking the system design interview”. It's amazing and super informative. Have come across very few courses that are as good as this!
Access to 50+ courses
New content added monthly
Certificate of completion
$31.08
/month
Billed Annually
Recommended Course

Grokking Microservices Design Patterns
13,063+ students
4.1
Master microservices design patterns for designing scalable, resilient, and more manageable systems.
View Course