How rare is L7 promotion?

Very. Single-digit percentage of FAANG-tier engineers reach L7. The exact rate varies by company and by org structure; rough estimates from candidate reports and Hello Interview's analysis suggest 5-10% of L6 staff promote to L7 over a 5-year window. Most staff engineers reach L7 either through long tenure with consistent strategic impact, or through external move to a company with a slot opening at the level.

Do all FAANG companies have an L7 distinction?

No. Google, Meta, Apple have explicit L7 (Senior Staff). Amazon uses Principal at the L7-equivalent position. Stripe goes Staff → Principal directly with no intermediate. Netflix has a flatter structure with 'Senior Software Engineer' covering a wide compensation range that overlaps L5-L7 at peer companies. Anthropic uses 'Member of Technical Staff' as an umbrella title without explicit L7 differentiation externally. The practical guidance: research the specific company's ladder via levels.fyi.

What's the path from staff to L7 if my company doesn't have an L7?

Move companies, or accept that your terminal level is staff at this company. At Stripe (Staff → Principal direct), staff engineers who want L7-equivalent scope often need to make the staff → principal jump, which is empirically rarer at Stripe than the L6 → L7 jump at Google. Engineers in companies without L7 distinctions sometimes find that an external move to a company with the level (and slot availability) is the practical path forward.

Is L7 worth it for the comp delta from L6?

Sometimes. The total comp delta from L6 to L7 averages $200k-$300k/year, mostly in stock. For engineers with 4+ years at L6 with stacked refresher RSUs, the delta narrows. Non-comp considerations: L7 has more strategic involvement, more visibility, more influence on technical direction. But also more org-political overhead, more meetings, less hands-on coding. Engineers who prefer technical depth over strategic involvement often find L6 staff more sustainable; engineers who want broader influence find L7 worthwhile.

How does L7 IC compare to engineering Director?

Roughly comp-equivalent at most FAANG. Total comp typically within 10-15% of each other; specific variation depends on company and stock performance. Work fundamentally different: L7 IC ships through technical artifacts (RFCs, design docs, code on the highest-leverage problems); Director ships through people management (hiring, performance reviews, team strategy). The choice is about work, not compensation. Reference: Charity Majors's 'Engineer/Manager Pendulum' (charity.wtf/2017/05/11).

What's the hiring committee process for L7 promotion?

More rigorous than L6. At Google, L7 promotion requires the L6 → L7 calibration committee plus often a senior leadership review (Director / VP). Promo packets are longer (10-20 pages typically) with extensive evidence of org-level scope. Cross-team impact letters from staff and director-level partners are common. The decision is rarely individual-IC-level; it's a strategic decision about whether the org needs another L7 in this area. Reference: Lazlo Bock's 'Work Rules!' chapter on calibration.

Do L7 engineers still write code?

Less than L6, and on the highest-leverage problems only. The work shifts further toward strategic technical leadership: RFCs, multi-team architecture, mentoring staff, executive-level conversations. Engineers who reach L7 often miss hands-on coding and either find ways to do it (taking on specific deep-technical projects) or transition into engineering management where the work is more uniformly strategic. Reference: Tanya Reilly's 'The Staff Engineer's Path' chapter 5 covers technical work at staff+ levels.

Should I aim for L7 or for engineering Director?

Different work. If you energize on deep technical problems and dread people management overhead, L7 IC. If you energize on team building and people decisions, Director. Compensation is comparable; track choice should be about long-term work satisfaction. Many engineers oscillate between the tracks (Charity Majors's pendulum); some commit to one. The wrong basis: 'managers earn more' (false) or 'IC has more flexibility' (also often false at L7). Right basis: which work do you want to do for the next 5-10 years.

Software Engineer Hub

Senior Staff Software Engineer Guide (L7 / IC7) (2026)

By Blake Crosley · Last verified 2026-04-29

In short

Senior Staff (L7 / IC7 / E7) sits between staff and principal at companies with deep IC ladders. The level exists at Google, Meta, and Apple as an explicit rung; at Stripe and many others, the path goes Staff → Principal directly. Scope at L7 expands to multi-product-area or full-platform technical leadership; total comp at FAANG-tier commonly clears $750,000 and clusters $810k-$1.2M+ (per <a href="https://www.levels.fyi/companies/google/salaries/software-engineer/levels/l7" rel="noopener" target="_blank">levels.fyi/companies/google/salaries/software-engineer/levels/l7</a>). The level distinction is so company-specific that the practical guidance is to read it as a comparison table by company.

Key takeaways

Senior Staff (L7 / IC7 / E7) is a company-specific level — Google, Meta, Apple have explicit L7; Stripe goes Staff → Principal directly; Amazon uses Principal at the L7-equivalent position. Hello Interview's leveling analysis details the per-company mapping.
L7 promotion is rare — typically reached by single-digit-percentage of the senior+ engineering population at companies that have the level (per Hello Interview's analysis at hellointerview.com/blog/understanding-job-levels-at-faang-companies).
FAANG-tier L7 total comp clusters $810k-$1.2M+ with stock vesting; some packages exceed $1.5M at peak vesting cycles per levels.fyi/companies/facebook/salaries/software-engineer/levels/e7.
L7 leads multi-product-area technical strategy, not single-area execution. The structural shift from L6: L6 owns a platform pattern; L7 sets the technical direction across multiple platforms or org-level scope.
Promotion from staff is rare and often comes via cross-org-recognized impact: significant open-source maintainership, popular internal libraries that ship across org, multi-year strategic projects with measurable company-level impact.
Many companies don't have L7 — knowing whether your company does (and what equivalent it has) is the load-bearing question for IC career planning past staff.

L7 by company: who has it and what they call it

The single most useful framing for L7 is a comparison table — the level's existence and meaning vary substantially by company. Sourced from levels.fyi, Hello Interview's FAANG levels guide, and engineer reports on Blind / Glassdoor:

Company	L7-equivalent title	Internal level code	Comp range (total)
Google	Senior Staff Engineer	L7	$750k-$1.05M+ (levels.fyi/companies/google/salaries/software-engineer/levels/l7)
Meta	Senior Staff (sometimes 'Director of Engineering' titled)	E7	$810k-$1.2M+
Apple	Senior Staff Engineer	ICT6	$700k-$1M+
Amazon	Principal Engineer	L7	$700k-$1M+ (Amazon merges L7-equivalent into Principal)
Stripe	(no L7 distinct from Principal)	L4 → L5	L4 (Staff) $560k-$780k; L5 (Principal) $750k-$1.1M+
Netflix	Senior Software Engineer (top of single-rung structure; comp varies widely)	—	$650k-$950k+
Anthropic	Member of Technical Staff (no formal L7 distinction externally)	—	$700k-$1.1M+ at L5-MTS
Databricks	Senior Staff Engineer	L7	$750k-$1.1M+

The practical guidance: the question 'what's L7 at my target company' is more useful than 'what's L7 in general'. Engineers planning past-staff trajectories should research the specific company's IC ladder via levels.fyi/job-family/Software-Engineer and Hello Interview's per-company analysis.

What L7 SWEs actually do (the structural shift from L6)

The structural shift from staff (L6) to senior staff (L7) is scope expansion from one platform / pattern to multiple platforms / org-level technical strategy. Concrete examples:

L6 (Staff) scope	L7 (Senior Staff) scope
Architect the company's standardized tracing pattern; drive adoption across 47 services	Set technical strategy for the entire observability platform; align with security, data, and infrastructure leadership
Lead a multi-team migration from monolith to microservices for one product area	Set the org-wide migration strategy; establish standards that all product areas follow
Own technical direction for the ML-platform team	Own technical direction across all ML-related teams (training, inference, evaluation, tooling)
Maintain a key internal library used across 5 services	Maintain external open-source projects with significant adoption (Spark for Databricks, Next.js for Vercel, etc.)

What L7 engineers do day-to-day:

Lead technical strategy across multiple product areas or platforms. Multi-quarter or multi-year horizons; influences org-level technical decisions.
Drive org-level architecture decisions. What to standardize, what to invest in, what to deprecate at the company level.
Mentor staff engineers. The mentorship at L7 is for L6 staff peers, not for senior or below.
Represent engineering at executive level. Often partner with VP/CTO on strategic decisions; sometimes report directly to executive layer.
Influence hiring strategy, leveling rubrics, technical org structure. L7 engineers often participate in calibration committees and shape the engineering bar across the org.

What L7 isn't: 'staff with more tenure'. L7 is structurally distinct in scope; engineers who don't expand beyond the staff platform-pattern level can stay L6 indefinitely.

Compensation at L7 — sourced specifics

From levels.fyi self-reports (verified 2026-04-27):

Google L7: ~$340k base, $750k-$1.05M+ total per levels.fyi/companies/google/salaries/software-engineer/levels/l7.
Meta E7: ~$340k base, $810k-$1.2M+ total per levels.fyi/companies/facebook/salaries/software-engineer/levels/e7.
Apple ICT6: ~$300k base, $700k-$1M+ total.
Databricks L7: ~$340k base, $750k-$1.1M+ total.
Anthropic L5 MTS (L7-equivalent): ~$380k base, $700k-$1.1M+ total.

The stock-vesting dynamic at L7: total comp variation across companies and across years for the same engineer is enormous, driven by stock performance. Meta E7 in 2024 (with Meta stock running) saw individual packages exceeding $1.5M; Meta E7 in 2022 (post-stock decline) saw the same level realize less than half. Plan for the median, not the peak.

External hiring at L7 is rare but not unheard of. Companies hire externally to L7 typically when (a) they have a specific gap (e.g., recruiting an open-source maintainer who's notable in their domain) or (b) the candidate has a strong existing relationship at the hiring company. levels.fyi job-history data shows external L7 hires receiving 20-30% bumps over internal-promote L7 comp; the external move is high-leverage when the slot exists.

Path from staff to senior staff

Empirical pattern from L7 engineers' published career retrospectives (Will Larson's StaffEng essays, Tanya Reilly's StaffEng counterpart at noidea.dog/staff, and engineer-shared career narratives on Blind / Twitter):

The four most common paths to L7:

Multi-year strategic project leadership. You lead a multi-quarter or multi-year initiative with org-level impact. Examples: leading a major platform migration affecting all product teams; architecting and shipping a foundational system that becomes company infrastructure; leading a multi-quarter incident-remediation effort post-major-outage.
Cross-org technical influence. You become the engineer the org consults on a specific technical area. RFCs you author get adopted; design conversations across teams reference your work; your name appears in calibration discussions for senior+ engineers across the org.
Mentoring multiple staff engineers. Several staff engineers cite you as their mentor or formative reviewer. The signal: you've helped multiple L6s reach their level.
Public technical contribution. Open-source maintainership of significant projects (Spark, React, Next.js, MLflow, etc.); conference talks at Strange Loop, QCon, KubeCon, RAILS Conf; technical writing read by a wider engineering community. The visibility expands beyond the company.

What doesn't get you to L7:

Doing L6 work for many years. L7 isn't 'staff with tenure'.
Volume of contributions without strategic impact. Many small RFCs < one foundational RFC that shapes the org.
Staying narrow in one technical area without cross-org influence.
Avoiding executive-level conversations because they feel uncomfortable.

The honest truth about L7: most staff engineers don't reach L7. The slot scarcity is real (companies have far fewer L7 positions than L6); the impact bar is structurally higher; promotion timing depends partly on org-level needs (an L7 promotion may wait for an opening). Engineers who target L7 should plan for a 5-10 year horizon from staff and accept that the path may not complete.

Frequently asked questions

How rare is L7 promotion?: Very. Single-digit percentage of FAANG-tier engineers reach L7. The exact rate varies by company and by org structure; rough estimates from candidate reports and Hello Interview's analysis suggest 5-10% of L6 staff promote to L7 over a 5-year window. Most staff engineers reach L7 either through long tenure with consistent strategic impact, or through external move to a company with a slot opening at the level.
Do all FAANG companies have an L7 distinction?: No. Google, Meta, Apple have explicit L7 (Senior Staff). Amazon uses Principal at the L7-equivalent position. Stripe goes Staff → Principal directly with no intermediate. Netflix has a flatter structure with 'Senior Software Engineer' covering a wide compensation range that overlaps L5-L7 at peer companies. Anthropic uses 'Member of Technical Staff' as an umbrella title without explicit L7 differentiation externally. The practical guidance: research the specific company's ladder via levels.fyi.
What's the path from staff to L7 if my company doesn't have an L7?: Move companies, or accept that your terminal level is staff at this company. At Stripe (Staff → Principal direct), staff engineers who want L7-equivalent scope often need to make the staff → principal jump, which is empirically rarer at Stripe than the L6 → L7 jump at Google. Engineers in companies without L7 distinctions sometimes find that an external move to a company with the level (and slot availability) is the practical path forward.
Is L7 worth it for the comp delta from L6?: Sometimes. The total comp delta from L6 to L7 averages $200k-$300k/year, mostly in stock. For engineers with 4+ years at L6 with stacked refresher RSUs, the delta narrows. Non-comp considerations: L7 has more strategic involvement, more visibility, more influence on technical direction. But also more org-political overhead, more meetings, less hands-on coding. Engineers who prefer technical depth over strategic involvement often find L6 staff more sustainable; engineers who want broader influence find L7 worthwhile.
How does L7 IC compare to engineering Director?: Roughly comp-equivalent at most FAANG. Total comp typically within 10-15% of each other; specific variation depends on company and stock performance. Work fundamentally different: L7 IC ships through technical artifacts (RFCs, design docs, code on the highest-leverage problems); Director ships through people management (hiring, performance reviews, team strategy). The choice is about work, not compensation. Reference: Charity Majors's 'Engineer/Manager Pendulum' (charity.wtf/2017/05/11).
What's the hiring committee process for L7 promotion?: More rigorous than L6. At Google, L7 promotion requires the L6 → L7 calibration committee plus often a senior leadership review (Director / VP). Promo packets are longer (10-20 pages typically) with extensive evidence of org-level scope. Cross-team impact letters from staff and director-level partners are common. The decision is rarely individual-IC-level; it's a strategic decision about whether the org needs another L7 in this area. Reference: Lazlo Bock's 'Work Rules!' chapter on calibration.
Do L7 engineers still write code?: Less than L6, and on the highest-leverage problems only. The work shifts further toward strategic technical leadership: RFCs, multi-team architecture, mentoring staff, executive-level conversations. Engineers who reach L7 often miss hands-on coding and either find ways to do it (taking on specific deep-technical projects) or transition into engineering management where the work is more uniformly strategic. Reference: Tanya Reilly's 'The Staff Engineer's Path' chapter 5 covers technical work at staff+ levels.
Should I aim for L7 or for engineering Director?: Different work. If you energize on deep technical problems and dread people management overhead, L7 IC. If you energize on team building and people decisions, Director. Compensation is comparable; track choice should be about long-term work satisfaction. Many engineers oscillate between the tracks (Charity Majors's pendulum); some commit to one. The wrong basis: 'managers earn more' (false) or 'IC has more flexibility' (also often false at L7). Right basis: which work do you want to do for the next 5-10 years.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about product design, hiring technology, and ATS optimization. More writing at blakecrosley.com.