Engineer Level & Compensation Comparison

Explore how software engineering roles compare between companies like Google, Meta, and Microsoft. See how each level's experience, title, and total compensation align across countries.

What are software engineering levels?

Engineering levels are the rungs of a company's internal ladder. Each rung fixes the scope you are expected to own, how much direction you need, how far your influence reaches, and the pay band your offer comes from. Notation differs, with L levels at Google, E levels at Meta, and numbers at Microsoft, but the progression from task to system to organisation is the same everywhere.

The chart below puts those ladders side by side so you can see where a rung at one company sits relative to another, and how the compensation attached to it changes between the United States, the United Kingdom, and India. Select the companies you care about, switch country, and open any level for the detail behind it.

This page covers product technology companies. If you work at a large IT services firm, where progression runs on grade codes, bands, and appraisal ratings rather than on L or E ladders, the career levels hub is the page built for that and the two are deliberately kept separate.

Levels at a glance

What a level sets
Expected scope, autonomy, influence, and the pay band your offer is drawn from
Common notation
L at Google, E at Meta, numbers at Microsoft, ICT at Apple
What moves you up
Demonstrated scope, not tenure or effort
Who decides
A committee reading a written case, usually not your manager alone
Biggest comparison trap
Matching titles instead of matching scope and pay bands
Negotiate first
The level, because it determines the band the salary comes from

Google

Software Engineer II (Entry)
Level: L3
Exp: 0-2 yrs
$185k
Software Engineer III
Level: L4
Exp: 2-4 yrs
$294k
Senior Software Engineer
Level: L5
Exp: 5-8 yrs
$403k
Staff Software Engineer
Level: L6
Exp: 8-12 yrs
$525k
Senior Staff Engineer
Level: L7
Exp: 8-12 yrs
$525k
Principal Engineer
Level: L8
Exp: 8-12 yrs
$525k
Distinguished Engineer
Level: L9
Exp: 8-12 yrs
$525k
Google Fellow
Level: L10
Exp: 8-12 yrs
$525k

Meta

Software Engineer
Level: E3
Exp: 0-2 yrs
$125k
Software Engineer
Level: E4
Exp: 2-4 yrs
$155k
Senior Software Engineer
Level: E5
Exp: 5-8 yrs
$200k
Staff Software Engineer
Level: E6
Exp: 8-12 yrs
$250k
Senior Staff Engineer
Level: E7
Exp: 2-4 yrs
$155k
Director
Level: E8
Exp: 5-8 yrs
$200k
VP
Level: E9
Exp: 8-12 yrs
$250k

Microsoft

Software Engineer I
Level: 59
Exp: 0-2 yrs
$161k
Software Engineer I
Level: 60
Exp: 2-5 yrs
$182k
Software Engineer II
Level: 61
Exp: 5-8 yrs
$210k
Software Engineer II
Level: 62
Exp: 8-12 yrs
$273k
Senior Software Engineer
Level: 63
Exp: 0-2 yrs
$161k
Senior Software Engineer
Level: 64
Exp: 2-5 yrs
$182k
Principal Engineer
Level: 65
Exp: 5-8 yrs
$210k
Principal Engineer
Level: 66
Exp: 8-12 yrs
$273k
Principal Engineer
Level: 67
Exp: 0-2 yrs
$161k
Partner
Level: 68
Exp: 2-5 yrs
$182k
Partner
Level: 69
Exp: 5-8 yrs
$210k
Distinguished Engineer
Level: 70
Exp: 8-12 yrs
$273k

How to read the comparison above

The chart is most useful when you narrow it to the ladders actually in front of you. This is the order that gets you to an answer.

  1. 1

    Pick the companies you are actually comparing

    Use the checkboxes to show only the ladders in front of you. Comparing every company at once produces a wall of colour rather than an answer, and the useful comparison is almost always between two or three specific offers.

    • The chart aligns rungs vertically, so equivalent bands sit at the same height
    • Each column is one company's ladder from entry to its most senior rung in the data
  2. 2

    Switch to the country the offer is in

    Compensation bands are set per location. Comparing a United States band against a United Kingdom or India band without switching country will mislead you badly, because the ratio between them is large and varies by level.

    • Use the country selector before drawing any conclusion about pay
    • Compare your position within the local band rather than across borders
  3. 3

    Open the level and read the detail

    Click any level to see the title, the experience range, the notes attached, and the compensation figures for every country in the data. This is where the difference between two similar looking rungs becomes visible.

    • Experience ranges are indicative, not entry requirements
    • Notes flag where a rung behaves differently from its neighbours
  4. 4

    Match on scope, then check the band

    Find the rung whose expectations match the largest thing you have actually owned. Only then look at what that rung pays. Doing it the other way round leads people to argue for a level they cannot substantiate.

    • Write down the biggest system or programme you owned end to end
    • Note the decisions you made without needing approval
  5. 5

    Read the company specific guide before you negotiate

    The chart gives you the shape. The company guides linked below give you the written expectations, promotion norms, and compensation structure for a specific ladder, which is what you need for an actual conversation.

    • Check where the individual contributor track ends at that company
    • Look at how equity is granted and refreshed, not just the headline total

Ladder shapes side by side

The same career span is divided into a different number of rungs at every company. This table summarises the ladders in the chart above so you can see the shape before reading the detail.

CompanyRungs shown hereEntry rungMost senior rung shown
Google8 levels, L3 to L10L3: Software Engineer II (Entry)L10: Google Fellow
Meta7 levels, E3 to E9E3: Software EngineerE9: VP
Microsoft12 levels, 59 to 7059: Software Engineer I70: Distinguished Engineer
Apple5 levels, ICT2 to ICT6ICT2: Junior Software EngineerICT6: Senior Staff / Principal Engineer
Netflix5 levels, L3 to L7L3: Software EngineerL7: Principal Engineer
Uber6 levels, 3 to 73: Software Engineer I7: Principal Engineer
Salesforce5 levels, Associate MTS to Principal ArchitectAssociate MTS: Associate Member of Technical StaffPrincipal Architect: Principal Architect / Senior IC
Airbnb5 levels, G7 to G11G7: Software EngineerG11: Principal Engineer
Spotify4 levels, Associate Engineer to Staff EngineerAssociate Engineer: Entry Software EngineerStaff Engineer: Staff Software Engineer

Rungs shown here are the ones present in this comparison, not necessarily every level a company operates. Read the company guide linked below for a complete ladder.

How engineering ladders differ between companies

Put several ladders next to each other and the differences are structural rather than cosmetic. They change how often you get promoted, how much a promotion is worth, and how far you can go without managing people.

The first difference is the number of rungs. Some ladders in the comparison above run to eight or more levels from entry to the top listed rung, others cover the same career span in four or five. A ladder with many narrow rungs produces frequent promotions with modest increments, which feels like momentum. A ladder with few wide rungs produces long stretches at one title followed by a large jump. Neither shape tells you how quickly someone is actually growing, which is why promotion frequency is a poor proxy for career progress.

The second is where the individual contributor track stops. On some ladders the senior rungs are explicitly individual contributor roles, principal and distinguished engineers who influence technical direction without managing people. On others, the rungs above a certain point are described in management terms, which tells you that staying technical means staying put. This is worth checking before you join, because it determines whether there is a path for you in five years.

The third is the mix of base salary and equity. At the major United States employers, equity becomes a large share of compensation as levels rise, which makes offers harder to compare than the headline numbers suggest: a grant is a value at a point in time that then vests over years, and two identical totals can be worth very different amounts depending on vesting and whether refresh grants are routine.

The fourth is how the same experience range maps onto rungs. Two companies can put an engineer with five years of experience at different points on their ladders without either being wrong, because they are calibrating against their own internal population. This is the root cause of most confusion when people compare their level to a friend's at another company.

The fifth is how much the ladder is published. Where expectations per level are written down and available, you can prepare against them precisely. Where they are not, you are relying on your manager's interpretation, which makes the conversation about what you must demonstrate far more important.

  • More rungs means more frequent promotions, not faster growth
  • Check where the individual contributor track ends before you join
  • Equity heavy packages make offers harder to compare than the totals imply
  • The same years of experience maps to different rungs at different companies
  • Published expectations let you prepare precisely; unpublished ones make the manager conversation critical

What actually changes at each level: scope, autonomy, and influence

Every ladder, whatever its notation, is measuring the same three dimensions. Learning to read them is what lets you translate between companies and argue for a level with evidence.

Scope is the size of what you own. At entry level it is a task somebody else specified. One rung up it is a feature, including the parts nobody thought about. At senior it is a system with dependencies, where your decisions constrain other teams' work. At staff and above it is a technical area or a programme, where the question is no longer how to build the thing but whether it is the right thing to build.

Autonomy is how much of the problem arrives already framed. Early on you receive a specification. Then you receive a problem and produce the plan. Then you decide which problems are worth attention at all, and you are trusted because you have been right often enough. The transition from the first to the second is where most careers stall, because doing assigned work extremely well never generates evidence of autonomy. Someone has to hand you an ambiguous problem, or you have to find one.

Influence is whose work changes because of you. It starts with your own output. Then your team's, through review, mentoring, and the standards you set locally. Then other teams', through design decisions, shared infrastructure, or being the person consulted before a plan is finalised. At the most senior rungs influence is exercised almost entirely over people who do not report to you, which is why the operative skills are writing, persuasion, and judgement rather than authority.

Notice that all three are about the shape of your work rather than its volume or quality. An engineer can be the most productive person on a team and still sit at a mid level, because everything they produced was inside a boundary someone else drew. This is not unfair, it is what the ladder is measuring.

Compensation follows the three. It does not lead them. A promotion case that argues from years served, hours worked, or number of tickets closed is describing input, and committees are looking for scope, autonomy, and influence. Rewriting the same year of work in those terms often changes the outcome without changing any of the facts.

How levelling and promotion decisions are actually made

There are two separate mechanisms, and confusing them causes a lot of avoidable frustration: the one that sets your level when you join, and the one that changes it once you are there.

When you join, the interview loop produces feedback and a recommendation, and then a separate calibration or hiring committee decides the level. This is why an offer sometimes arrives at a different level from the one in the job advert, and why the interviewers themselves often cannot tell you what level you will get. The decision rests on which level's expectations your demonstrated scope matched, judged by people comparing you against everyone else hired recently at that band.

Once you are inside, promotion usually runs through a written case. Your manager documents the scope you have handled, gives specific examples of impact, and gathers feedback from people who worked with you, often deliberately from outside your immediate team. A committee then compares that document against the written expectations for the next level, alongside other candidates.

The critical implication is the same in both cases: the people deciding have not watched you work. They are reading. Excellent work that was invisible outside your team, or that only your closest colleagues could evaluate, is genuinely hard to write up persuasively. That is a reason to make your work legible as you do it, through design documents, written decisions, and results that someone outside your team can see.

Calibration is the part people underestimate. Before final decisions, managers compare their proposed promotions across a group to keep standards consistent. Your manager's support is necessary and not sufficient; the case has to hold up next to other cases. That is also why timing matters, since cases are considered in cycles rather than whenever the work happens to be finished.

The practical response is unglamorous. Ask your manager directly what would cause the case to fail. Ask what evidence is currently missing. Then choose work that produces it, and write down what you decided and what resulted while you still remember the details.

How to prepare for a promotion to the next level

Promotion preparation is mostly an evidence problem rather than a skill problem, and it starts a year before the cycle you are aiming at.

Begin with the written expectations for the level above yours. Read them as a list of claims you will need to support, then mark each one as strong evidence, partial evidence, or none. Almost everyone finds the same pattern: solid evidence of technical execution, thin evidence of influence beyond their own team, and nothing at all for ambiguous problems they framed themselves.

That gap is your plan, and it usually means choosing different work rather than more work. The project that spans two teams, the migration nobody wants to own, the design decision that has been deferred three times: these generate the evidence that promotion cases need. Additional well executed tickets do not, however many of them there are.

Tell your manager explicitly that you are working toward the next level. This gets skipped constantly, and it matters because your manager assembles the case, steers work toward you, and knows what previous cases failed on. Agree what the missing evidence is, and set a checkpoint mid cycle rather than discovering the verdict at review time.

Keep a running record as the year goes. Note the decision, the reasoning, who was affected, and the outcome. When the case is written, specific dated examples are far more persuasive than a general impression of competence, and you will not remember the details six months later.

Finally, understand the calendar. Cases are submitted into cycles, and a strong case that misses the window waits for the next one. Knowing when the deadline falls, and what your manager needs from you before it, is part of the preparation rather than an afterthought.

  • Audit yourself against the written expectations for the next level, item by item
  • Close the evidence gap by choosing ambiguous, cross team work rather than more tickets
  • Say out loud that you are going for the next level, and ask what would make the case fail
  • Keep dated notes on decisions and outcomes as you go
  • Know the cycle deadline, because timing decides whether a strong case waits a year

How to interpret a level when you change company

Changing employer is where levelling has the largest financial consequence, because the level in your offer sets the band your salary comes from and how long your next promotion will take.

Start by describing yourself in scope rather than title. Write down the largest system or programme you owned end to end, how many people depended on it, which decisions you made without approval, and what happened as a result. That description translates between companies. A title does not.

Then read the target company's expectations for the level being offered and compare. If they match your description, the offer is calibrated and you should focus on the package. If the level looks lower than your title implies but the expectations match your actual scope, the offer is probably accurate and your previous title was generous. If the expectations clearly exceed anything you have done, accepting is a risk rather than a win, because you will be measured against them from your first review.

Down-levelling usually reflects what the interviewers could verify rather than doubt about your ability. The remedy is evidence, not indignation: point to the ambiguous work you framed, the decisions you made alone, and the people outside your team who depended on the result. If you cannot point to any of those, the lower level is the honest read and the right response is to take it and close the gap quickly.

Negotiate the level before the money. Level determines the base band, the equity range, and your starting point for the next promotion, so a higher salary inside too low a level is a short term win with a long term cost. Once the level is agreed, negotiating inside the band is a much smaller conversation.

One more practical point: ask for the ladder. A company that will show you the written expectations for the level they are offering, and for the one above it, is giving you the information you need to judge the offer. Reluctance to do so is itself informative.

Why comparing titles across companies is unreliable

There is no external standard for engineering titles, and there is no body that certifies what Senior means. Every company decides its own, and several forces push those decisions apart.

First, titles are partly a recruiting instrument. A generous title is cheap to give and helps close candidates, so title inflation is a rational strategy for a company competing for hires. That means the same title can sit at quite different rungs at two employers who are otherwise similar.

Second, some companies share one title across several levels while others change the title at every rung. Where one title covers multiple levels, two people with identical titles can have materially different scope, pay, and promotion prospects, and nothing on a resume will reveal it.

Third, ladders change. Companies add rungs, split levels, and rename bands, and they rarely announce it externally. A mapping that was accurate two years ago can quietly stop being accurate.

Fourth, the same title means different things in different organisational contexts. A lead role at a fifty person company may involve more autonomy and less scope than the same title at a ten thousand person company, or the exact reverse, depending entirely on how the work is divided.

What does transfer is scope, expectations, and compensation band. Comparison charts, including the one on this page, are orientation tools that put a rung in the right neighbourhood so you can start a sensible conversation. Treat them that way rather than as arithmetic, and verify against the written expectations for the specific role in front of you.

  • Titles are partly a recruiting instrument, so inflation is rational and common
  • One title can cover several levels, hiding real differences in scope and pay
  • Ladders gain rungs and get renamed without any external announcement
  • Organisational context changes what the same title involves
  • Scope, written expectations, and pay bands are what actually compare

Software Engineer Salary and Level Comparison: Google vs Meta vs Microsoft

Understanding how software engineering levels and salaries align across major tech companies like Google, Meta, and Microsoft is essential for any engineer planning career moves, negotiating offers, or benchmarking pay equity. Each company defines its internal levels differently (from L3 and L4 at Google to E4 and E5 at Meta or 60 to 65 at Microsoft), but they represent comparable bands of skill, experience, and compensation.

For example, a Software Engineer III (L4) at Google is roughly equivalent to a Software Engineer (E4) at Meta or a Software Engineer II (Level 61) at Microsoft. These levels usually correspond to engineers with 2 to 4 years of experience and total compensation around $180k to $250k USD depending on country and stock refresh cycles. By comparing rank and experience ranges, engineers can identify how promotions and pay progression align across employers.

Understanding Level Structures

Each company uses a numeric hierarchy to define seniority. Google's "L" system ranges from L3 (entry) to L10 (Google Fellow). Meta uses the E prefix from E3 to E9, while Microsoft employs numbered levels from 59 through 70+. These levels map approximately as follows:

Compensation Trends

Compensation typically includes three components: base salary, annual bonus, and equity (RSUs). For US-based engineers, equity can represent over half of total compensation at higher levels. For example, a L6 Staff Engineer at Google might have a base salary of $220k, a 15% bonus, and $250k+ in yearly stock. In contrast, the same level at Meta or Microsoft might balance the equity and base differently, but total annual pay tends to fall within a similar range.

Engineers in the UK and India see different scales, but relative progression remains consistent. UK compensation is often 70 to 80% of US levels, while India sees around 25 to 35% of US numbers, although stock refreshes at top companies increasingly narrow this gap for senior levels.

Career Growth Insights

Promotions typically follow a 2 to 3 year cadence at early levels, slowing to 4 to 6 years at Staff and above. Google emphasizes technical breadth and design impact, while Meta prioritizes execution speed and leadership. Microsoft values collaboration and architectural influence. Engineers comparing offers should assess not just title or pay but also advancement rate, scope, and stability of stock value.

For those targeting senior positions, understanding the level structure is key to aligning expectations. For example, a L7 at Google is often a senior manager or architect, while Meta's E7 may still be an individual contributor role. These distinctions impact not only pay but career direction.

Takeaways for Job Seekers

By using this Engineer Level & Compensation Dashboard, you can visualize differences clearly and make informed decisions about your career path.

Updated November 2025. Data reflects aggregated public information and crowd-sourced compensation reports for software engineering roles.

Engineering level questions

What are software engineering levels?

Engineering levels are the rungs of a company's internal ladder. Each one defines the scope you are expected to own, how much direction you need, how far your influence reaches, and the compensation band your offer is drawn from.

Companies use different notation for the same idea: an L ladder at Google, an E ladder at Meta, numbered levels at Microsoft, and ICT levels at Apple. The notation differs, the underlying progression from task to system to organisation does not.

How do engineering ladders differ between companies?

They differ in how many rungs they have, how wide each rung is, where the individual contributor track ends, and how much of total compensation is equity rather than base salary.

A company with many narrow rungs promotes more often in smaller increments. A company with few wide rungs leaves people at the same title for years and then moves them a long way. Neither shape tells you how fast someone is actually growing.

What changes as you move up an engineering ladder?

Scope, autonomy, and influence, in that order of visibility. Scope moves from a task, to a feature, to a system, to a technical direction that several teams follow. Autonomy moves from being told what to build, to being handed a problem, to deciding which problems matter. Influence moves from your own output, to your team's, to teams that do not report to you.

Compensation follows those three rather than leading them, which is why promotion cases built on tenure or effort tend to fail.

How are levelling decisions made?

For internal promotions, your manager usually assembles a written case describing the scope you have handled, with examples and peer feedback, and a committee compares it against the written expectations for the next level. The reviewers have not seen your work, so legible written evidence matters more than informal reputation.

For new hires, the interview loop produces a recommendation and a separate calibration step sets the level. That is why the level in an offer sometimes differs from the one in the job advert.

Why is comparing job titles across companies unreliable?

Because there is no external standard and titles are chosen partly for how they read. One company attaches Senior to its third rung, another to its fifth. Some publish a title per level, others share one title across several levels, which is why a single title can cover very different scopes.

Comparing the written expectations, the scope of the work described, and the compensation band is reliable. Comparing titles is not.

What is down-levelling and how do I avoid it?

Down-levelling is being offered a level below the one your current title suggests. It usually happens because the scope the interviewers could verify was narrower than the title implied, not because they doubted your competence.

The defence is evidence: describe the largest thing you owned end to end, the decisions you made without approval, and who depended on your work. If you cannot point to ambiguous work you framed yourself, the lower level is probably the accurate read.

Should I negotiate the level or the salary first?

The level, always. Level determines the band your base salary comes from, the equity range attached, and how long the next promotion will take. Winning on salary inside a level that is too low is a short term result with a long term cost.

Once the level is settled, negotiating within the band is a much smaller conversation.

How long does a promotion usually take?

Early rungs move faster than senior ones because the required jump in scope is smaller. Above senior, each step needs a demonstrably larger sphere of impact, so the gap between promotions widens, and at the most senior individual contributor levels there may be very few positions at all.

The pattern is structural rather than a reflection of individual pace: there is simply less room at the top of any ladder.

How much of total compensation is equity at senior levels?

At the major United States technology employers, equity becomes a large share of the package as levels rise, and for higher levels it can exceed base salary. That is the pattern the figures in this comparison reflect.

Because equity is granted as a value at a point in time and then vests over years, two offers with the same headline total can be worth very different amounts depending on grant timing, vesting schedule, and whether refresh grants are routine.

Why do levels pay differently in different countries?

Compensation bands are set per location, so the same level pays differently in the United States, the United Kingdom, and India. The comparison on this page lets you switch country to see that difference directly.

The relative progression up the ladder stays broadly consistent even where the absolute numbers do not, which is why comparing your position within a local band is more useful than comparing across countries.

How is this page different from the career levels page?

This page covers product technology companies, where ladders use L, E, ICT, or numeric notation and compensation is heavily weighted toward equity.

The career levels page covers large IT services firms such as TCS, Infosys, Wipro, HCLTech, and Cognizant, where progression runs on grade codes, bands, and annual appraisal ratings. If you work in services, start there.

Can I trust the compensation figures in the chart?

Treat them as aggregated and crowd sourced rather than official. They reflect public information and self-reported offers, so they are useful for orientation and for seeing the shape of progression between levels.

Before a negotiation, verify against several independent sources and, where possible, against individual reported offers with a date attached.

Company ladders, services grades, and pay research

This chart gives you the shape of each ladder. These pages give you the written expectations, promotion norms, and compensation detail for a specific company.

Company level guides

Comparisons and senior rungs

IT services career ladders

Pay research and preparation

  • Salary directory

    Pay ranges by role, useful for sanity checking a band before a conversation.

  • Recent offers

    Individual reported offers broken into base, bonus, and equity.

  • Interview questions

    The behavioural questions that probe scope, ownership, and influence.

  • Mock interviews

    Practise explaining your scope to someone who was not there.

  • Resume builder

    Describe scope and ownership rather than listing tasks.

  • Courses

    Structured courses for the technical depth the next rung expects.

  • Resources library

    Levelling guides, compensation research, and interview process breakdowns.