How to Get Promoted from L6 to L7 at Google

You made Staff. The L5-to-L6 jump was one of the hardest promotions at Google, and now you're looking at L7. Here's what makes this promotion different: you already know how to operate at the Staff level. The L6-to-L7 jump doesn't demand a fundamentally different playbook. It demands the same behaviors at a scale that most engineers never reach.

What follows is what the committee actually evaluates for L7 packets, and how to build a case that clears the bar.

How Google's L7 promotion process works

The mechanics stay familiar: your manager assembles a promotion packet with self-review, peer reviews, and manager assessment. A calibration committee reviews packets cold and decides. But L7 packets face the tightest scrutiny on the engineering IC ladder.

VP-level sponsorship matters here. At L6, your manager's advocacy was enough to push the packet through committee pushback. At L7, the committee expects signals from further up the chain. A former Googler described the dynamic on Hacker News: "Having a VP who knew me and could write about me really made the difference." Your manager still writes the packet, but senior leadership endorsement carries real weight at this level.

Even fewer slots are available. Google told employees in March 2023 that fewer would be promoted to L6+. That constraint bites harder at L7, where the committee still stack-ranks a set number of packets per cycle and draws a line. The line at L7 cuts higher than at any previous level.

Same behavioral bar, higher leverage bar. The behaviors expected at L6 and L7 are similar: creating scope, working through others, setting technical direction. The difference is scale and reach. L7 evidence needs to show influence across an entire engineering organization, not just a team cluster.

What L7 (Senior Staff Engineer) looks like at Google

The gap between L6 and L7 is not a behavioral shift. It is a leverage shift. Both levels operate the same way. L7s operate at a scale that affects significantly more people and systems.

Dimension	L6 (Staff Engineer)	L7 (Senior Staff Engineer)
Scope of influence	Team cluster (~8+ engineers)	Engineering organization (~50+ engineers)
Problem complexity	Solves problems L5s can't	Solves problems L6s struggle with
Technical direction	Sets direction for a team cluster	Defines long-term technical vision for product areas or platforms
People development	Grows L5 engineers into stronger seniors	Grows L6 engineers — highest-leverage mentoring
Decision scope	Architectural decisions adopted by adjacent teams	Decisions that shape entire engineering organizations
Execution model	Works through others across teams	Shapes how work gets done across multiple organizations
Organizational peer	Engineering manager	Senior engineering manager or engineering director

"The behaviors needed for the L6 and L7+ levels are similar. L7s just have much more leverage."

— Developing.dev

L7 engineers are among the top few percent of Google's engineering workforce. They don't just build systems. They shape how engineering organizations approach problems, defining long-term technical vision for products and platforms, and making architectural decisions that other teams build on for years.

The promotion criteria that actually matter for L6 to L7

The committee evaluates the same core dimensions as L6. The evidence bar shifts from team-cluster influence to organization-wide leverage.

Organizational-scale technical strategy. At L6, you set direction for your team cluster. At L7, the committee expects evidence that you defined technical strategy for an entire product area or platform: a migration that affected dozens of services, a reliability framework adopted across an org, or a technical standard that changed how multiple teams build.

Growing L6 engineers. One of the highest-leverage signals the committee can see. At L6, you grow L5 peers. At L7, you help Staff engineers get better. This matters because L6s already drive significant output. Peer reviewers who are L6+ and credit you with changing how they approach problems carry substantial weight in the packet.

"L7 engineers grow L6 engineers, which is high leverage since L6s already get a lot done."

— Developing.dev

Senior leadership visibility. The committee at L7 expects that VPs and directors know your name. Not because you self-promoted, but because your work was visible enough to reach that level naturally. If senior leadership hasn't engaged with your technical decisions or architectural proposals, the org-wide influence narrative doesn't hold up.

Cross-org problem solving at scale. Where L6 packets show cross-team influence across 2-3 teams, L7 packets show cross-org influence. The committee looks for evidence that you identified and solved problems spanning organizational boundaries: the kind of work where no single team could have owned it and someone had to build alignment across competing priorities.

Building your L7 promotion case at Google

Step 1: Secure senior leadership sponsorship

Before anything else: does your VP or director know your work? If not, that is the first gap to close. This does not mean scheduling face time. It means making sure your highest-impact technical decisions are visible to leadership through design reviews, architecture proposals, or technical strategy documents that naturally reach that level. A VP who can speak to the organizational value of your work makes the committee's job substantially easier.

Step 2: Find or create org-wide technical strategy work

Look for problems that span organizational boundaries. Infrastructure that three orgs depend on but nobody owns. Technical debt that creates recurring incidents across multiple product areas. A platform migration that nobody wants to lead because it requires aligning a dozen teams. If your current scope stays within your team cluster, you need to expand it or move to a role where org-level strategy work is available.

Step 3: Invest in growing L6 engineers

Identify Staff engineers in your org and invest in their growth. Help them navigate ambiguous problems, shape their architectural decisions, and challenge their technical thinking. This multiplier effect is exactly what the committee evaluates at L7: your impact measured through the success of people who are already operating at a high level.

Step 4: Build your peer reviewer network at L6+ and leadership level

Your L7 packet needs reviewers who are L6 or above, from outside your immediate team cluster. Directors or senior tech leads from adjacent orgs who saw you drive alignment on cross-org initiatives. If your reviewers are all within your team cluster, the leverage narrative falls flat.

Step 5: Document impact at the organizational level

Track outcomes that span orgs. Not "I led the team to ship feature X" but "I defined the reliability strategy for the payments platform, drove adoption across 4 teams, and reduced org-wide incident rate by 35%." Quantify wherever possible and keep a running log. Reconstructing org-level impact from memory months later almost never produces the same quality of evidence.

Common mistakes that stall L6-to-L7 promotions at Google

Doing excellent L6 work without expanding scope. You keep shipping high-quality technical strategy for your team cluster, but your influence radius hasn't grown beyond it. The committee sees strong L6 evidence, and that is exactly what they categorize it as. L7 requires demonstrating that your work shaped outcomes beyond your immediate area.

No senior leadership sponsor. Your manager writes the packet and advocates at committee, but the committee at L7 expects signals from further up. If no VP or director can speak to the organizational value of your contributions, the packet looks like a strong L6 case without the L7 leverage signal.

Staying in a role without org-wide reach. Not every team or org can support L7-scope work. If the biggest problem in your area stays within a team cluster, the structural ceiling will block you regardless of execution quality. This may require a move to a team or org where the problems are naturally org-wide.

Relying on technical depth without organizational influence. Being the deepest technical expert in your area is necessary but not sufficient. The committee also evaluates whether you shaped how your organization makes technical decisions, resolved cross-org conflicts, and built alignment among teams with competing priorities.

Timeline and realistic expectations for L6 to L7 at Google

Timeline	What it looks like	How common
~2 years	Exceptional. Right org, immediate org-wide impact, strong VP sponsorship.	About 7% of those promoted
3-4 years	Standard successful path. Multiple cycles with sustained org-level evidence and sponsorship.	Most common for those promoted
4-6 years	Includes failed attempts, org changes, scope that didn't materialize, or budget deferrals.	Common
Never	L6 is a strong career destination. Many Staff engineers stay permanently.	Not unusual

The median for engineers who do get promoted is roughly 45 months, about 3.75 years. That figure doesn't account for the majority of L6 engineers who never make the jump at all.

The compensation difference is substantial: median total compensation goes from approximately $580K at L6 to roughly $900K at L7, a jump of over $300K per year driven almost entirely by equity grants.

Some engineers find the external path faster. Leaving Google at L6, joining another company at a Senior Staff-equivalent level, building a year of track record, and returning at L7 is a strategy discussed frequently on Team Blind. Whether it makes sense depends on how much organizational context, relationships, and institutional knowledge you would leave behind.

Frequently asked questions

How long does it take to get promoted from L6 to L7 at Google?

The median among engineers who get promoted is roughly 3.75 years at L6. About 7% reach L7 within 2 years. Many Staff engineers stay at L6 permanently, and it is a well-compensated terminal level with median total compensation around $580K. The timeline depends heavily on organizational scope, VP-level sponsorship, and whether the right cross-org problems are available in your area.

Is L6-to-L7 easier than L5-to-L6 at Google?

In some ways, yes. The L5-to-L6 jump requires a fundamental behavioral change: from solving known problems to finding them, from direct execution to working through others. The L6-to-L7 jump requires the same behaviors at larger scale, so the playbook stays the same. But the bar remains high because L7 slots are scarce, and demonstrating org-wide influence is a structural constraint that execution quality alone cannot solve.

Should I leave Google and come back at L7?

It is a viable strategy, and it is discussed frequently on Team Blind. The combination of limited promotion budget, slot scarcity at L7, and a $300K+ comp difference makes the external path attractive. Engineers leave as L6, get hired at a Senior Staff-equivalent level elsewhere, build a year of track record, and return at L7. The downside is losing accumulated organizational context, relationships, and the institutional knowledge that makes cross-org influence possible in the first place.

What if my org doesn't have L7-scope work?

This is a structural blocker, not a performance problem. If the biggest technical challenges in your org stay within a team cluster, the scope ceiling will cap your evidence regardless of how well you execute. Look for cross-org problems to adopt from outside your team, or consider moving to an org where the problems are naturally at the right scale. Have an honest conversation with your manager and skip-level about whether your current organization can support an L7 case.

---

CareerClimb helps you build your promotion case week by week. Track your wins, map them to what Google's committee evaluates at the Senior Staff level, and know exactly where your evidence stands before your manager writes the packet. Download CareerClimb