Why does an E3 level SWE at Meta make only ~190k/year, while an E8 level engineer makes over ~$2M/year, even though both engineers are ICs and spend the same time at work?
I have spent the last 5 years at Meta as an IC. I joined with a little over 15 years of experience, and I’ve worked with many solid engineers in this time.
Here is how I think about that compensation jump.
1. Same hours, completely different “unit of work”
An E3’s unit of work is usually a task or a ticket.
An E8’s unit of work is a multi year problem for the company.
E3: “Implement this service, fix this bug, write this feature.”
E8: “How do we cut infra cost by 20 percent across this product” or “How do we make this platform safe to scale to 10x users.”
One person is paid to execute.
The other is paid to decide what is worth executing in the first place.
2. Radius of impact
E3 usually impacts a file, a service, maybe a small team.
E8 shapes whole orgs and product lines.
If an E3 ships something great, the impact is great but local.
If an E8 ships the right platform, hundreds of engineers become faster and the company saves or earns millions every year.
Comp tracks the area of the circle you influence.
3. Risk and downside protection
At junior levels, mistakes are usually contained and reversible.
At senior staff levels, a bad call can burn tens of millions or damage the brand.
E8s are paid for judgment under ambiguity.
They decide which bets the company should not make, which migrations can wait, which “shiny idea” is going to kill reliability.
You pay more to people whose good judgment protects you from very expensive failures.
4. They scale themselves
This can happen in a few ways.
1. Delegation with ownership
They define the shape of the problem, then hand large pieces to other senior and mid level engineers while keeping the bar and direction clear.
2. Knowledge that travels
They write RFCs, public comments, FAQs, wikis, internal posts.
One answer helps hundreds of people who will face the same issue next quarter.
3. Tools over heroics
Instead of unblocking people manually all day, they build tools, libraries or guardrails so others can unblock themselves. One well designed tool can save thousands of engineering hours every year.
This is what “scaling yourself” actually looks like.
The company pays for that multiplier.
5. Ownership of the “uncomfortable problems”
Junior engineers usually work inside a well defined box.
E8s take ownership between the boxes.
They pick up problems that:
Span many teams and no one really “owns”
Require aligning leaders who disagree
Have product, infra, legal and security angles at the same time
Most people avoid those because they are messy, political and slow.
Very senior ICs lean into them. That is where a lot of value sits.
Continued ↓
