How to Get Promoted from E3 to E4 at Meta
Building your promotion case?
Get AI coaching on what to document and how to present it.
You're six months into your first job at Meta. Your code is shipping. Your manager says you're doing fine. But every time you check Team Blind, someone is posting about getting exited at the 24-month mark for not making E4, and you're not sure if "doing fine" is the same thing as "on pace to get promoted."
It isn't, necessarily. E3 at Meta is not a terminal level. There's an explicit expectation that you advance to E4, and a clock running in the background. The E3-to-E4 promotion is the most straightforward level jump at Meta, but straightforward doesn't mean automatic. You still need a Performance Summary Cycle (PSC) packet that survives calibration, a manager who builds the case, and evidence that you've already been working like an E4. Here's how that works.
What Changes from E3 to E4
E3 is Meta's entry-level software engineering role. E4 is where Meta considers you a fully independent contributor. The title doesn't change dramatically, but the expectations shift in specific ways.
| Dimension | E3 (Entry-Level SWE) | E4 (Software Engineer) |
|---|---|---|
| Independence | Works under guidance; manager breaks down tasks | Works independently on well-scoped problems |
| Scope | Individual tasks and small bug fixes | Owns features end-to-end from design to launch |
| Design work | Implements designs from senior engineers | Contributes to design docs; may author designs for own features |
| Code quality | Code works and follows team patterns | Code is well-tested, production-ready, and earns trust in review |
| Communication | Asks good questions, absorbs feedback | Communicates proactively, raises risks, provides useful code reviews |
| People | Minimal expectation | Begins helping onboard new teammates and answering questions |
The gap comes down to one shift: your manager gives you a problem, not a task list. You figure out the approach, break it down, execute it, and ship it. At E3, someone else does most of that scoping. At E4, that's your job.
How Meta Promotions Work at E3-E4
Meta's promotion process is manager-driven with calibration oversight. Your manager builds your promotion case and presents it during calibration alongside your PSC results. The calibration committee normalizes ratings and promotion decisions across the org.
The process runs on a clear sequence:
- You write your self-review (~1,000 words) during the PSC window
- Peer feedback is collected from 3-5 nominators you choose
- Your manager drafts their assessment and proposes your rating
- Calibration happens: managers argue for their reports' ratings and promotions against competing claims
- Results come through the review tool, followed by a 1:1 with your manager
Your PSC is evaluated across Meta's four performance dimensions:
- Project Impact: what you shipped and what changed because of it
- Engineering Excellence: code quality, reliability, testing, technical standards
- Direction: how you influenced priorities, not just executed on them
- People: mentorship, collaboration, raising the team's quality bar
At E3, Project Impact and Engineering Excellence carry the most weight. The committee wants to see that you can ship quality code that solves real problems independently. Direction and People matter less at this transition than they will for E4 to E5, but showing early signal in both dimensions strengthens your case.
The rating that matters: an Exceeds (EE) rating signals promotion readiness. Greatly Exceeds (GE) makes the case very strong. Meets All (MA), the most common rating at roughly 45% of engineers, means you're performing solidly at your current level but doesn't generate promotion momentum.
The backdrop that makes this urgent: Meta has an explicit up-or-out policy at E3. You have 24 months from reaching E3 to make E4. Miss that window and you'll be exited. Even before that deadline, two consecutive Meets Most (MM) ratings trigger an automatic PIP. Every PSC cycle counts.
How Long E3 to E4 Should Take
| Pace | Timeline | What's happening |
|---|---|---|
| Fast | 12-18 months | Strong from the start; may have been under-leveled at hire; E4-scope work early |
| Standard | 18-24 months | Solid contributor, steady growth across two PSC cycles |
| Slow (danger zone) | 24+ months | Hitting the up-or-out boundary; something structural needs to change immediately |
Meta moves faster than Google for this transition. At Google, the L3-to-L4 jump typically takes a similar 18-24 months, but L3 at Google doesn't carry an explicit up-or-out deadline. At Meta, the clock is real.
The compensation jump reinforces why this matters. Based on Levels.fyi data, median total comp at E3 is roughly $175K compared to approximately $260K at E4. That's an $80K+ increase, driven primarily by larger stock grants and a higher bonus multiplier. Every cycle you wait costs real money, and the up-or-out deadline means waiting too long costs you the job entirely.
What Actually Gets You Promoted
Own a feature end-to-end
The clearest signal of E4 readiness is completing a feature from problem identification through launch without someone else breaking down every step. This doesn't need to be a massive project. It could be a well-scoped improvement to an internal tool, a new API endpoint, or a user-facing feature your team needs. What matters is that you drove it: you understood the problem, proposed the approach, built it, got it reviewed, shipped it, and confirmed it worked.
If your current workload is entirely tasks that someone else scoped and handed to you, talk to your manager about getting work where you own the full cycle.
Get comfortable with ambiguity
E3 engineers receive well-defined tasks. E4 engineers receive problems. The transition means getting comfortable with figuring things out. When your manager says "this API is unreliable and users are complaining," the E4 response is to investigate, identify the root cause, propose a fix, and execute. The E3 response is to wait for someone to tell you which file to look at.
Practice this before it shows up in your review: when you hit a problem, try to reason through it for 30-60 minutes before asking someone. When you do ask, come with what you've tried and a hypothesis, not just "I'm stuck."
Write strong self-reviews
Your self-review is one of the primary documents the calibration committee reads. Treat it like a promotion case, not a task log. For each contribution, cover what you did, what impact it had, and how it went beyond E3 expectations.
"I got promoted after 14 months. The self-review was what made it work. I wrote it like I was arguing my case, not listing tasks."
Use Workplace to document your thinking
Meta's internal social network is treated as evidence in your PSC. Engineers who post project updates, share technical decisions, and answer questions publicly create a trail of artifacts that feed into peer feedback and self-review content. This visibility isn't about self-promotion. It's about making your work visible to people who will later write your peer feedback.
If you're doing strong work quietly, you're making it harder for your peers to write meaningful feedback and harder for your manager to defend your rating in calibration.
Have the promotion conversation early
Don't wait for your manager to bring it up. After your first full PSC cycle, ask directly: "What does E4 readiness look like for me? What evidence would make my case clear in calibration?"
This conversation gives you a target and signals to your manager that you're thinking about growth. Your manager is the person who presents your case in calibration. They need to know what you're aiming for, and they need specific wins to build that case.
Mistakes That Keep Engineers at E3
Only doing what you're told. The most common pattern among E3 engineers who stall is executing assigned tasks well without ever stepping beyond them. E4 requires showing initiative: identifying a problem before it's assigned, proposing a solution, and driving it. If every piece of work you've done was handed to you with a clear spec, your manager doesn't have the material to argue for a level change.
Not tracking your wins. When the PSC window opens, you have a week or two to recall months of contributions. Engineers who track accomplishments as they happen write stronger self-reviews. Engineers who scramble to remember produce vague summaries the committee can't evaluate.
Writing a task log instead of a promotion case. "Fixed 47 bugs and submitted 83 PRs" is an E3 self-review. "Owned the migration of the notification service from the legacy API to the new platform, reducing latency by 40% and eliminating the team's top on-call ticket category" is an E4 self-review. The difference is framing impact, not listing output.
Ignoring the People dimension entirely. E3 engineers sometimes go heads-down and code for 12 months without helping anyone else. At E4, even early signal matters: answering questions on Workplace, helping a new hire navigate the codebase, or giving thorough code reviews. Zero people signal is a gap calibration notices.
Assuming your manager is tracking everything. Managers at Meta can have 8-12 reports. They're not remembering every PR you merged or every bug you fixed. If you're not surfacing your contributions in 1:1s and Workplace posts, your manager's calibration packet will reflect what they remember, not what you actually did.
Frequently Asked Questions
How long does it take to get promoted from E3 to E4 at Meta?
Most engineers who get promoted spend 18-24 months at E3. Strong performers with good project fit can do it in 12-18 months. The minimum is typically one full PSC cycle of strong results, though two cycles is more common. Meta's up-or-out policy sets a hard deadline of 24 months. Engineers who haven't been promoted by then are exited. This is stricter than Google, where L3 carries an informal expectation but no forced timeline.
Is the E3 to E4 promotion considered easy at Meta?
Relative to later promotions, yes. The bar for E3 to E4 is lower than E4 to E5, and the expectations are more concrete: ship features independently, debug without hand-holding, communicate clearly. But it's still a calibration decision that requires your manager to present evidence. "Easy" doesn't mean it happens without effort.
What PSC rating do I need to get promoted from E3 to E4?
An Exceeds (EE) rating is the standard promotion-track signal. Greatly Exceeds (GE) makes the case even stronger. Meets All (MA) means you're performing well at E3 but doesn't generate promotion momentum on its own. Your manager needs calibration-ready evidence that you're operating at E4 scope. One or two cycles of EE with clear E4-scope evidence is the typical promotion profile.
What's the pay difference between E3 and E4 at Meta?
Based on Levels.fyi, median total compensation jumps from roughly $175K at E3 to approximately $260K at E4. That's an $80K+ increase, driven by base salary increases, larger stock grants, and a higher bonus multiplier. This is one of the larger percentage jumps in Meta's engineering ladder.
Should I switch teams if I'm stuck at E3?
Only if the problem is your team, not your skills. If your team doesn't have E4-scope work (rare, but possible on small maintenance teams), switching can help. But a team change resets your context. Your new manager won't know your work, and you'll spend months ramping up again. Given the 24-month clock, a team switch mid-tenure is risky. If your manager is the issue (disengaged, not building your case), try having the direct conversation first. If that doesn't change anything after a full PSC cycle, then consider moving, but do it quickly.
CareerClimb tracks your wins across Meta's four performance dimensions as they happen, maps them to what calibration evaluates, and tells you exactly what evidence you're missing before your manager presents your case. When the next PSC window opens, your self-review is backed by documented impact, not memory. Download CareerClimb