Staff Engineer Levels at Google, Meta, Amazon and Apple (L6, E6, ICT5)

The staff engineer level is L6 at Google, E6 at Meta, and ICT5 at Apple. Amazon has no staff title, and its nearest level is Principal SDE at L7. At all four companies, staff is the first level above senior, and it is the point where the job changes from owning one team's work to setting technical direction across several teams.

The Amazon case surprises many engineers. Amazon's L6 shares a number with Google L6, but it is Amazon's senior level, not its staff level. An engineer who compares the two numbers directly will misjudge an offer by a full level.

This article puts the four staff levels side by side. It covers what each company expects at the level, the usual years of experience, reported pay, how engineers reach the level, and what the interviews test.

Staff Levels in One Table

These mappings are not published by the companies. They come from reported offers and from aggregators such as levels.fyi, and they are firmest for Google and Meta. The pay figures are rounded averages from levels.fyi company pages and move every month, so check the site for current numbers before you negotiate.

(https://storage.googleapis.com/download/storage/v1/b/designgurus-prod.appspot.com/o/article%2Fadhoc%2Fimg:c234ce-edba-b25e-a82-40b4c11ee.png?generation=1794420019881058&alt=media)

What Makes a Level "Staff"?

A staff engineer is a senior individual contributor whose work spans several teams rather than one. An individual contributor is an engineer who does not manage people. Three things separate staff work from senior work, and every company below looks for the same three.

• Scope. A senior engineer owns a service or a feature. A staff engineer owns a problem that crosses team boundaries, such as replacing a storage system that eight teams depend on.
• Time horizon. A senior engineer plans for the next few months. A staff engineer makes decisions that will shape the next two or three years, so the design has to allow for change.
• Influence. A senior engineer delivers mostly through their own work. A staff engineer delivers mostly through other engineers, many of whom report to someone else.

(https://storage.googleapis.com/download/storage/v1/b/designgurus-prod.appspot.com/o/article%2Fadhoc%2Fimg:21b87dc-25a3-8758-288a-a84febdf34.png?generation=1794420022613675&alt=media)

Coding skill is rarely the difference. Most engineers who fail to reach staff write excellent code. They fail because their record shows results inside one team and no decisions that other teams adopted.

For a side-by-side view of the two roles, with the same project handled at each level, see Staff Engineer vs Senior Engineer: Scope, Expectations, Interview Bar.

Google L6: Staff Software Engineer

L6 is Google's staff level, and the first level above Senior Software Engineer (L5). An L6 leads engineering for a large project or a product area, reviews designs across teams, and acts as the main technical authority in that domain.

Most L6 engineers have eight to fifteen or more years of experience. Google's terminal level is L4 officially and L5 in practice. A terminal level is one where an engineer can stay for a whole career without pressure to be promoted. So L6 is optional, and many strong engineers never pursue it.

Promotion from L5 to L6 commonly takes three to five years or more. Levels.fyi reports average L6 total pay in the United States at about $600K, with stock making up close to half. The Google software engineer levels guide covers the levels on either side.

Meta E6: Staff Software Engineer

E6 is Meta's staff level. An E6 influences engineering across several teams: they set technical roadmaps, make architecture decisions, and coordinate engineers who do not report to them. Meta also expects an E6 to raise the quality of the wider organization, not only their own team.

Meta's terminal level is E5, and below E5 Meta expects steady promotion. Reaching E6 removes that pressure for good, but only about 15 percent of Meta engineers are E6 or above. Most E6 engineers have eight to fifteen or more years of experience.

Meta pays the most of the four at this level. Levels.fyi reports average E6 total pay in the United States at about $720K, and stock is the largest part. The Meta software engineer levels guide explains the up-or-out rule below E5.

Amazon: No Staff Title, and Why L7 Is the Closest Match

Amazon's software engineers move from SDE I (L4) to SDE II (L5) to Senior SDE, also called SDE III (L6). The next level is Principal SDE at L7. There is no staff level between Senior and Principal.

That gap makes Amazon the hardest of the four to map, and sources disagree. The common mapping, used across this blog's levels series, places Amazon L7 at Google L6 to L7 and Meta E6 to E7. Pay data supports the lower end of that range, because levels.fyi reports Amazon Principal pay at about $640K, close to Google L6. Scope supports the higher end, because an Amazon Principal often sets direction for a whole organization, which at Google is more typical of L7.

Two consequences matter to engineers moving between these companies.

• Amazon L6 maps to Google L5 and Meta E5, not to Google L6. Subtract one from the Amazon number to get the Google number.
• Some Amazon L6 engineers do staff-scope work. Because the step from L6 to L7 is so large, candidates report that strong Amazon seniors are sometimes hired at Google L6 or Meta E6. That depends on the loop, not on the title.

Amazon rarely hires someone into L7 on potential. External Principal hires usually arrive with a record of leading work at that scope elsewhere. The Amazon SDE levels guide covers L4 to L8 in detail.

Apple ICT5: The Staff Level With a Plain Title

ICT stands for Individual Contributor Technical, and ICT5 is the level most often compared to Google L6 and Meta E6. Apple's terminal level is ICT4, its senior level, so ICT5 is a competitive step that many engineers never take.

An ICT5 leads the technology for a whole area, usually across several teams, and acts as the authority in that domain. Internally the title is still "Software Engineer", which hides how senior the role is on a resume. Most ICT5 engineers have ten or more years of experience.

The mapping is looser here than at Google or Meta. Candidates report that ICT5 spans engineers who would be Staff at one company and Senior Staff or Principal at another. Levels.fyi reports average ICT5 total pay in the United States at about $560K, with a higher share in base salary than at Meta. The Apple ICT levels guide maps ICT2 to ICT6.

Preparing for a staff loop? The rounds look the same as a senior loop, but each one is scored for scope, time horizon, and influence. Grokking Staff Engineer Interview teaches what staff answers contain, round by round.

Promotion or External Hire: Two Ways to Reach Staff

There are two ways to reach a staff level: promotion inside a company, or hiring in from outside. Each one is hard in a different way.

Promotion needs evidence. A promotion committee, which is a group of senior engineers and managers who decide promotions, reads a written case. At staff level, that case needs projects where other teams changed how they work because of your decisions. Engineers who stay inside one team rarely build that evidence, however strong their work is.

External hiring needs a loop that proves the level in four or five hours. The common failure is down-leveling, which means the company makes an offer one level below the one the candidate applied for. A staff candidate whose answers are correct but stay at team scope usually gets a senior offer. Ask the recruiter for the target level before the loop is scheduled, because companies can adjust it before the interviews and almost never after.

How Promotion to Staff Works at Each Company

None of the four companies publishes its promotion process in detail. The descriptions below come from engineers' public accounts and career guides, so treat them as the usual pattern rather than official policy. The shared idea is simple: at staff level, a manager alone cannot promote you, and a group of people who do not work with you every day has to agree that your work is already at the next level.

Google. Promotion is decided by a committee that reads a written case, usually called a promotion packet. The packet describes your projects, quotes feedback from peers, and includes your manager's assessment of how you already work at the next level. Engineers report that the committee looks for at least two quarters of work at L6 scope before it approves, and that under Google's current review system the manager has a larger role in the case than before. The practical lesson is that an L6 case is built over a year or more, not written in the month before the deadline.

Meta. Promotions are decided during calibration, which is a meeting where managers compare engineers across a whole organization so that ratings and promotions are consistent. Your manager presents the case, and other managers ask questions and compare your results with those of other engineers. Engineers report that E6 promotion needs sustained staff-level impact over several months, not one strong project. Because the meeting compares people directly, impact that other teams can see and measure carries the most weight.

Amazon. Promotion to Principal (L7) is widely described as one of the hardest promotions at the company. Engineers report that it rests on a long written document, reviewed by senior leaders and by existing principal engineers, and that support from your manager's manager matters as much as support from your manager. Amazon also runs a Principal Engineering Community, a group of its most senior individual contributors with its own published tenets, and candidates are expected to already work the way that community describes.

Apple. Apple's process is the least visible of the four. Engineers report that promotion to ICT5 depends heavily on the support of senior leaders in the organization, and that there is less of a shared, company-wide rubric than at Google or Meta. Because the internal title stays "Software Engineer", the level is also harder to show to the outside world, which affects engineers who later move to another company.

How the Amazon L7 Question Affects Offers

The disagreement about Amazon L7 is not only a table problem. It changes the offers that engineers receive in both directions.

An Amazon Senior SDE (L6) who interviews at Google or Meta usually targets L5 or E5. If their record shows decisions that several teams adopted, a recruiter may set the target at L6 or E6 instead. Candidates report that this happens, but it depends on the loop, and the safer plan is to ask for the higher target early and then prove it in the system design and project rounds.

An Amazon Principal (L7) who moves to Google or Meta is often offered L6 or E6, sometimes L7 or E7. The answer usually follows scope rather than title. A Principal who set direction for a large organization has a strong case for the higher level, while a Principal whose work stayed inside one product area is more likely to receive the staff level.

In the other direction, a Google L6 or Meta E6 who joins Amazon is usually hired at L7 only when their record already shows organization-wide decisions. Otherwise the common offer is L6, the senior level, often with a higher salary inside that band. Engineers who skip this detail can accept what looks like a lateral move and later find that they took a step down in title.

Common Mistakes When Comparing Staff Offers

Staff offers are large, and small misreadings add up to large differences. These mistakes come up often.

• Comparing level numbers instead of scope. Amazon L6 and Google L6 share a number but sit one level apart. Always convert to the same company's ladder before comparing.
• Comparing the first year only. Stock grants usually vest over four years, and the schedule differs between companies. Some front-load the grant, while others spread it evenly. Compare the total over four years, and check whether refresh grants, which are new stock awards given in later years, are typical at that level.
• Ignoring stock risk. Most staff pay comes from stock, so the value moves with the share price. A 720K package that is 60 percent stock carries more risk than a 560K package with a larger base salary.
• Treating a title as permanent. A down-level at hiring often takes two or more years to recover through promotion. A slightly lower total pay at the correct level can be the better choice.
• Forgetting the terminal level. Above the terminal level there is no pressure to be promoted, but there is also no automatic growth. At staff, further growth depends on finding larger problems, so ask what problems the team expects its staff engineers to own.

What Staff Interviews Test

Staff loops at all four companies usually contain coding, system design, a deep dive into a past project, behavioral questions, and a hiring manager conversation. Coding works mostly as a bar to clear. The level decision usually comes from system design, the project deep dive, and the behavioral rounds.

In system design, a staff answer defines the problem before solving it, names the trade-offs that will matter in two years, and explains how several teams would build and run the system. The L6 system design guide shows what that looks like in a full answer. In behavioral rounds, the stories need decisions that crossed team boundaries and a measurable result.

The staff engineer interview guide explains each round in detail and gives a six-week preparation plan.

How the Staff Level Compares to the Levels Around It

Read the rows above Staff as rough guides. At Amazon and Apple, one level covers a wider range of scope than at Google or Meta, so two engineers with the same Amazon or Apple level can map to different Google levels. The FAANG software engineer levels guide has the full comparison, including Netflix.

Frequently asked questions

What level is staff engineer at Google? Staff Software Engineer is L6 at Google. It is the first level above Senior (L5), and most L6 engineers have eight to fifteen or more years of experience.

Is Meta E6 the same as Google L6? Yes. E6 and L6 are both the Staff Software Engineer level, with the same scope across several teams. Reported pay at Meta E6 is usually higher than at Google L6, mostly because of larger stock grants.

Does Amazon have staff engineers? No. Amazon goes from Senior SDE (L6) directly to Principal SDE (L7). Principal is the closest match to Google L6 and Meta E6, although some sources place it nearer Google L7.

Is Amazon L6 equal to Google L6? No. Amazon L6 is Senior SDE, which maps to Google L5 and Meta E5. Subtract one from the Amazon number to get the Google number.

What is ICT5 at Apple? ICT5 is Apple's level above senior, usually compared to Google L6 and Meta E6. The internal title is still Software Engineer, and most ICT5 engineers have ten or more years of experience.

How many years of experience does a staff engineer need? Reported ranges are about eight to fifteen years at Google and Meta, and ten or more at Apple and Amazon. Years alone do not decide the level; evidence of work across several teams does.

How much does a staff engineer earn at FAANG? Levels.fyi reports average US total pay of about 600K at Google L6, 720K at Meta E6, 640K at Amazon Principal, and 560K at Apple ICT5. Check the site for current numbers, because they change often.

How do you get promoted to staff at Google or Meta? Both companies decide staff promotions in a group review, not by a manager alone. Engineers report that the review looks for several months of work that already matches staff scope, such as decisions that other teams adopted, backed by written feedback from peers on those teams.

Should I accept a senior offer when I applied for staff? It depends on the gap between the two levels at that company and on the role. A down-level can take two or more years to recover, so compare the offer with your current path, and ask the recruiter what evidence would support a staff offer instead.

Related reading

• FAANG Software Engineer Levels Explained
• The Staff Engineer Interview: What Changes From Senior, Round by Round
• System Design Interview for L6 Engineers
• Google Software Engineer Levels Explained
• Amazon SDE Levels Explained
• Apple ICT Levels Explained
• Staff Engineer vs Senior Engineer: Scope, Expectations, Interview Bar

Applying for a staff role? Grokking Staff Engineer Interview covers the system design, project deep dive, and behavioral rounds that decide the level, with full mock loops to compare against your own answers.