ResumeAdapter
Companies / Meta / Levels
Updated 2026-06-05

Meta engineering levels, E3 to E9.
Scope, not years, sets the band.

Why this matters

Meta runs an IC engineering ladder from E3 to E9, with E5 as the terminal level where most career engineers settle. Meta does not publish an official public level map or salary bands; the levels, titles, and compensation figures below reflect commonly reported community data as shown on levels.fyi, observed June 2026, and should be treated as indicative ranges rather than official Meta figures.

Scan my Meta resumeFree to scanScope per levellevels.fyi cross-reference
By the numbers
Level range
E3 to E9
Plus E10 Meta Fellow
Comp range
~$186K to $3.44M
levels.fyi, June 2026
Terminal level
E5
Senior SWE, no up-or-out clock
Hardest step
E5 to E6
Senior to Staff, optional

The quick answer

What are Meta's engineering levels and what do they pay?

Meta uses an internal IC ladder for engineers, commonly reported as E3 (entry or new grad), E4 (mid), E5 (Senior), E6 (Staff), E7 (Senior Staff), E8 (Principal), and E9 (Distinguished Engineer), with E10 Meta Fellow above for a tiny top fraction. Meta does not publish an official public level map or salary bands, so the E-numbers surface mainly through levels.fyi and offer letters. Commonly reported total compensation on levels.fyi, observed June 2026, runs roughly $186K at E3, $310K at E4, $483K at E5, $697K at E6, $1.24M at E7, and around $3.44M at E8 on a very limited sample; E9 has no reliable public median and is described qualitatively. These are crowdsourced figures, indicative and not official Meta numbers. E5 Senior is the terminal level where most career engineers settle, because up-or-out pressure exists only at E3 to E4 to E5; promotion to E6 and above is optional and more competitive. Scan your resume to see whether its scope language matches the level you are targeting. Scan your Meta resume.

Meta uses an internal IC band system for engineers, E3 through E9, and does not publish an official public level map or salary bands. The ladder below is commonly reported by the community: levels.fyi crowdsourced compensation uploads plus community reports. Every comp figure on this page is levels.fyi crowdsourced data observed June 2026, indicative and not an official Meta number.

The year-of-experience bands attached to each level are community heuristics describing what is typical, not Meta policy. Two engineers can sit at the same level with very different tenure, which is why scope of ownership, not years, is the reliable signal of band. Treat every number here as a commonly reported, community-sourced estimate.

The defensible public scope is E3 to E9, which covers essentially every realistic applicant. E5 (Senior Software Engineer) is the terminal or career level: up-or-out pressure exists only at the junior steps, E3 to E4 to E5 over about four to five years, and once at E5 there is no up-or-out clock. Promotion to E6 and above is optional and more competitive.

Public comp data thins out sharply at E8, where the sample is very small, and disappears as a reliable median at E9, so any single number there should be read as a wide, uncertain bracket or omitted entirely. For any anchor number on a resume or in a negotiation, cite levels.fyi by name and date the data as June 2026.

The E ladder, level by level

Each level: scope, autonomy,
impact, and typical signals.

For each level, the commonly reported title and a scope rubric, scope of ownership, autonomy, impact, and the typical signals a resume needs, with levels.fyi-anchored compensation folded into the signals. Titles, levels, and year bands are community-sourced heuristics, not official Meta figures, and all compensation is levels.fyi crowdsourced data observed June 2026. For the wider hiring picture, start with the Meta resume guide.

E3
Level E3

Software Engineer (entry / new grad)

Scope of ownership

Typically 0 to 2 years. Owns well-scoped tasks and small features inside an existing system while ramping. The standard new-grad entry point; Meta's ladder starts at E3, sometimes written IC3, with no public E1 or E2 for software.

Autonomy

Works with regular guidance and code review. Success is reliable, well-tested delivery of assigned work, not independent problem framing.

Impact

Impact is at the task and small-feature level inside one team. Year band is a community heuristic, not a Meta policy.

Typical signals & comp

Lead with clean problem-solving and measurable internship or project results. Total comp commonly reported on levels.fyi around $186K, observed June 2026, indicative and not an official Meta figure.

E4
Level E4

Software Engineer (mid)

Scope of ownership

Typically 2 to 4+ years. Owns standard features and medium projects end to end with some guidance. The first fully contributing band, where an engineer is a dependable independent builder.

Autonomy

Drives assigned projects to completion with limited oversight and starts to scope ambiguous work into concrete tasks.

Impact

Impact spans a feature area within one team. The E3 to E4 to E5 sequence is where Meta's only up-or-out pressure sits, roughly 4 to 5 years to reach E5. [commonly reported]

Typical signals & comp

Show ownership of a feature plus one quantified outcome. Total comp commonly reported on levels.fyi around $310K, observed June 2026, indicative not official.

E5
Level E5

Senior Software Engineer

Scope of ownership

Typically 4 to 6+ years. Owns a domain or a significant project area, sets technical direction for a team, and mentors. This is the terminal or career level: once at E5 there is no up-or-out clock.

Autonomy

Operates independently on ambiguous problems, frames the work, and is trusted to make and defend technical decisions for the team.

Impact

Impact is team-wide and durable. Promotion beyond E5 is optional and more competitive, so most career engineers reach E5 and stay. [commonly reported]

Typical signals & comp

Lead with owned domain, technical direction, and mentorship, not just execution. Total comp commonly reported on levels.fyi around $483K, observed June 2026, indicative not official.

E6
Level E6

Staff Software Engineer

Scope of ownership

Typically 6 to 10+ years. Owns cross-team or multi-quarter technical scope and is a recognized technical leader for a larger area. Equivalent to Staff at peer companies.

Autonomy

Sets direction across teams, resolves the hardest technical disagreements, and is trusted with org-relevant architectural calls.

Impact

Impact spans multiple teams. Commonly cited that around 15% of Meta SWEs reach E6; treat that as a community figure, not an official Meta statistic.

Typical signals & comp

Lead with cross-team influence and architecture, not feature delivery. Total comp commonly reported on levels.fyi around $697K, observed June 2026, indicative not official.

E7
Level E7

Senior Staff Software Engineer

Scope of ownership

Typically 10 to 15+ years. Owns org-wide technical strategy and the most consequential systems. A small population of engineers operating at the scope of a whole product or infrastructure org.

Autonomy

Defines multi-org technical direction and is a primary technical authority leadership relies on for high-stakes bets.

Impact

Impact is org-wide and long-horizon. Commonly cited that around 3% of SWEs reach E7; treat that as a community figure, not official.

Typical signals & comp

Lead with org-level strategy, systems owned, and named outcomes at scale. Total comp commonly reported on levels.fyi around $1.24M, observed June 2026, indicative not official.

E8
Level E8

Principal Engineer

Scope of ownership

Typically 15+ years. Company-relevant technical leadership across a major domain. Rare; the public data sample at this level is very small.

Autonomy

Operates as a top technical voice on company-scale problems, shaping direction well beyond a single org.

Impact

Impact is company-relevant. Commonly cited that fewer than 1% of SWEs reach E8; treat that as a community figure, not official.

Typical signals & comp

Company-scale technical influence and direction. levels.fyi shows total comp around $3.44M, but this rests on very limited data points, so treat it as a wide, uncertain bracket rather than a band midpoint. Observed June 2026, indicative not official.

E9
Level E9

Distinguished Engineer

Scope of ownership

Company-level technical leadership. The top of the regular IC ladder, with engineering influence felt across the entire company.

Autonomy

Among the most senior technical decision-makers at Meta, setting direction at the company level on the hardest open problems.

Impact

Impact is company-level and extremely rare; commonly cited that fewer than roughly 50 engineers sit at E9. Above E9, E10 Meta Fellow exists for a tiny top fraction.

Typical signals & comp

Describe this level qualitatively by scope and company-level influence. There is no reliable public compensation median for E9, so no hard pay number is published here on purpose; any figure circulating should be treated as unverified.

Notes on the comp figures

Meta total compensation is base plus equity plus a cash bonus, and the equity component grows as a share of pay at higher levels, tending to dominate from E6 up. The E8 figure rests on very limited public data points, so it is a wide, uncertain bracket rather than a band midpoint, and E9 has no reliable public median, so no hard number is published for it. Above E9, E10 Meta Fellow exists for a tiny top fraction. Meta also runs a separate management track, and the dual tracks are described below. All figures are levels.fyi crowdsourced data observed June 2026, indicative and not official Meta numbers.

Reading the numbers

How L1 to L4 map to Meta,
and the management parallel.

Many searchers ask how generic L1, L2, L3, L4 numbering maps to Meta. It does not map by number. Meta uses E-numbers that start at E3, so the alignment is by scope, one to one, not by the digit. The mapping below is hedged and approximate, observed June 2026, and is not an official Meta equivalence.

Generic L-style to Meta E, by scope

Meta's ladder simply starts counting at E3, so a generic entry level lines up with E3 by scope even though the numbers differ. Other firms (for example Google, where L3 is the entry engineer) align roughly one to one by scope, not by number. Treat this as an approximate scope bridge, never an exact equivalence.

L3 (entry, e.g. Google)E3, entry / new grad. Meta has no public E1 or E2 for software; E3 is the floor, sometimes written IC3.
L4 (mid)E4, mid Software Engineer. First fully contributing band.
L5 (senior)E5, Senior Software Engineer. Meta's terminal / career level.
L6 (staff)E6, Staff Software Engineer. Cross-team scope.

Mapping is by scope, not by a shared number, and is approximate. Community-reported, observed June 2026, not an official Meta mapping.

IC and management dual tracks

Above E5, Meta runs IC and management as parallel tracks. The management ladder commonly starts at E5 / M0, and community sources (including Pragmatic Engineer) commonly map the levels one to one by scope as below.

M0 / E5Manager track begins at the Senior level; many E5s manage or lead without leaving IC scope.
M1 = E6Manager, mapped to Staff IC scope.
M2 = E7Senior Manager, mapped to Senior Staff IC scope.
D1 = E8Director, mapped to Principal IC scope.
D2 = E9Senior Director, mapped to Distinguished Engineer IC scope.

Parallel role-family ladders also exist for product, data, and other functions, with their own per-level specifics not covered here. Commonly reported, observed June 2026, not official Meta figures.

How far engineers typically climb

Commonly cited community distribution, not an official Meta statistic: roughly 15% of Meta SWEs reach E6 (Staff), around 3% reach E7 (Senior Staff), fewer than 1% reach E8 (Principal), and fewer than roughly 50 engineers sit at E9 (Distinguished Engineer). Because most engineers settle at E5 with no up-or-out clock, the levels above are increasingly selective rather than expected. Treat these proportions as indicative community figures, observed June 2026, not official Meta data.

  1. 01

    Identify your level by scope, not years

    Place yourself by the scope you actually own, since year bands are community heuristics: E3 to E4 owns tasks and features, E5 Senior owns a domain and mentors, E6 Staff owns cross-team scope, E7 and above own org-wide direction.

  2. 02

    Write bullets at the level's altitude

    Execution for E3 to E4, owned domain and mentorship for E5 Senior, cross-team architecture for E6 Staff, org-wide strategy for E7 and up. A resume written one level too low reads as the lower level to a Meta recruiter.

  3. 03

    Translate scope into numbers

    Attach a denominator to every claim: users served, systems owned, teams a platform supported, latency or quality deltas. Cross-reference levels.fyi for your target level, observed June 2026, and remember these are crowdsourced, not official Meta figures.

  4. 04

    Scan and iterate on ResumeAdapter

    Upload to ResumeAdapter to see your score against the Meta job description, the scope language missing for your target level, and a rewrite plan that quantifies the level you are pitching.

FAQ

Meta levels FAQ

The questions candidates surface when they cross-reference their experience against Meta's internal E3 to E9 ladder. Answers are byte-identical to the FAQPage JSON-LD, because AI engines that extract HTML and AI engines that extract JSON-LD should not see different text.

What are the engineering levels at Meta?

Meta's software engineering ladder is commonly reported as E3 (entry or new grad), E4 (mid), E5 (Senior), E6 (Staff), E7 (Senior Staff), E8 (Principal), and E9 (Distinguished Engineer), with E10 (Meta Fellow) above E9 for a tiny top fraction. Meta's ladder starts at E3, sometimes written IC3, and there is no public E1 or E2 for software. Meta does not publish an official public level map or salary bands, so these come from levels.fyi and community reports, observed June 2026, and are indicative rather than official Meta figures.

What is E5 at Meta?

E5 is Senior Software Engineer and is widely treated as Meta's terminal or career level. Up-or-out pressure exists only at the junior levels, roughly E3 to E4 to E5 over about four to five years; once at E5 there is no up-or-out clock, and promotion to E6 and above is optional and more competitive. An E5 owns a domain, sets technical direction for a team, and mentors. Total compensation is commonly reported on levels.fyi around $483K, observed June 2026, which is indicative and not an official Meta figure.

What is E9 at Meta?

E9 is Distinguished Engineer, a company-level individual contributor role at the top of the regular ladder. It is extremely rare; community sources commonly cite fewer than roughly 50 engineers at E9, and above it sits E10, the Meta Fellow tier, for a tiny top fraction. Because the public sample is so small, there is no reliable compensation median for E9, so this guide describes it qualitatively and does not publish a hard pay number. Meta publishes no official level map, so all of this is community-reported and observed June 2026, not official.

How do L1, L2, L3, L4 map to Meta levels?

Meta does not use generic L1, L2, L3, L4 numbering for engineers; it uses E-numbers that start at E3 (entry, sometimes written IC3). Generic L-style numbering from other firms, such as Google where L3 is entry, roughly aligns to Meta one-to-one by scope rather than by number, because Meta's ladder simply starts counting at E3. So an entry engineer is E3 at Meta and L3 at Google by scope, not by a shared number. Treat any cross-company mapping as approximate, since titles and scope, not the digits, are what actually line up. This is community-reported and observed June 2026, not an official Meta mapping.

How much does an E7 make at Meta?

Total compensation for an E7, Senior Staff Software Engineer, is commonly reported on levels.fyi at roughly $1.24M, observed June 2026. That figure is crowdsourced and indicative, not an official Meta number, and it is base plus equity plus bonus with equity dominating heavily at this level. E7 is rare; community sources commonly cite that around 3% of Meta SWEs reach it, so the public sample is smaller and individual offers vary widely.

Why are Meta's engineering levels private?

Meta does not publish an official public level map or salary bands, so the E3 to E9 ladder, the titles attached to each level, and the compensation figures are reconstructed by the community rather than disclosed by Meta. Crowdsourced sources, primarily levels.fyi, fill that gap, which is why every level and number on this page is attributed to levels.fyi and dated June 2026 and should be read as indicative community data, not official Meta figures.

Continue

Go deeper on the rest
of the Meta stack.

01 / Pillar

Meta resume guide

The pillar covering Meta's hiring bar, the values it screens for, and the loop. Start here if you have not already.

Read
02 / Spoke

What Meta looks for

Meta's core values mapped to resume language, with do-this and avoid-this examples and the impact-first lens.

Read
03 / Spoke

The Meta interview process

The Meta loop, the coding and system design rounds, and how leveling is decided after the onsite.

Read
04 / Resume example

Software engineer resume example

A worked software-engineer resume with scope quantified at each bullet, the level signal this page describes.

Read
Related

The ATS baseline and the rest of the company library.

For the data behind the median pre-edit score, see the ATS statistics. To compare hiring playbooks across employers, browse the full company library.

See the ATS statisticsBrowse all company guides
Engineer your resume to a specific level

Scan your resume against
a Meta job description.

Get your match score against the Meta posting, the scope language missing for the level you are targeting, and a rewrite plan that quantifies the level you are pitching. Free to scan; no signup to see the score.

Scan my Meta resumeGenerate a matching cover letter →
Your resume stays yoursAnalyzed in seconds, then deleted. Never stored. Never used to train AI.Meta job description scored