How to Get Promoted from Engineering Manager to Senior EM at Google
CareerClimb
Building your promotion case?
Get AI coaching on what to document and how to present it.
Your team ships on time. Your engineers are growing. Your skip-level gives you positive feedback, and your Googler Reviews and Development (GRAD) ratings have been consistently strong. You are doing everything right as an L6 Engineering Manager (EM) at Google.
And yet the promotion to L7 Senior EM feels like it isn't moving.
That's because L7 Senior EM is not a reward for being a great L6 EM. It is a structurally different role, and it comes with a constraint that IC promotions don't have: the organization has to need the position. Your director or VP may need to submit a business case justifying why a senior manager role should exist on your team before the promotion committee even evaluates your packet. You can be performing at L7 scope and still not get promoted because the org structure doesn't support it.
Here's what actually changes, how the process works for managers, and how to build a case that clears both the committee bar and the organizational bar.
What Changes from EM to Senior EM
The gap between L6 EM and L7 Senior EM is not about running your team better. It is a different job with a fundamentally different relationship to the organization.
| Dimension | L6 EM | L7 Senior EM |
|---|---|---|
| Scope | One team, one roadmap | Multiple teams or a significantly larger organization |
| Day-to-day involvement | Directly involved in team execution | One step removed from day-to-day; sets direction, doesn't manage execution |
| Accountability | Your team's output | Cross-team delivery and org-level outcomes |
| People leadership | Grows ICs (L3-L5 engineers) | Grows other managers; builds management capability across the org |
| Technical direction | Partners with tech leads on team strategy | Sets technical strategy for the org; accountable for architectural decisions across teams |
| Organizational design | Executes on team structure | Proposes and implements org structure; makes spans-and-layers decisions |
| VP relationship | Periodic touchpoints; VP is aware of your work | Regular VP-level engagement; known by name, by work, and by judgment |
| Strategic contribution | Executes the strategy your director sets | Co-authors strategy with your director; shapes the roadmap, not just executes it |
The clearest way to describe the shift: at L6, you are a direct line manager with day-to-day involvement in what your team builds. At L7, you are one step removed from day-to-day execution, managing an organization rather than a team, and your impact is measured by what the broader org delivers under your leadership.
L7 Senior EM sits at the same level as L7 Senior Staff Engineer on Google's ladder. The scope, the compensation, and the committee scrutiny are equivalent.
"The EM-to-Senior EM jump is harder to see from the inside than any IC promotion. You can be the best manager in your org and still not be promotable because the org doesn't have room for the role. That's not a performance problem. It's a structural one."
-- Paraphrased from a verified Google EM on Team Blind
How EM Promotions Work at Google
Manager promotions go through the same GRAD-based promotion system as IC promotions. Your manager writes a promotion packet, peer reviews are collected from engineers, partner EMs, and cross-functional stakeholders, and a calibration committee evaluates the case. The committee decides -- not your manager, not your director.
But EM promotions at L6 to L7 carry additional constraints that don't apply to most IC promotions.
The business case requirement. Some organizations require a formal business case justifying the creation of a Senior EM position before your promotion packet is even submitted. This means your director or VP must argue that the org's structure, headcount, and roadmap warrant a senior management role. If the business case isn't approved, your packet doesn't reach the committee. This is the single biggest difference between EM and IC promotions at this level: ICs need to demonstrate they are already operating at the next level. EMs need that plus organizational justification that the role should exist.
Dual committee review for all L7+ promotions. Every L6-to-L7 promotion -- manager or IC -- goes through two independent committees. The first committee evaluates your packet and votes. If approved, the case automatically routes to a second committee. Either committee can block the promotion. This is structural scrutiny, not an appeal process, and it applies to every senior promotion at Google.
Promotion budget explicitly capped since 2023. Google told employees in March 2023 that fewer would be promoted to senior levels. The committee stack-ranks packets and promotes a fixed number per cycle. A strong packet can still be deferred because the slots ran out. Budget limitations apply especially hard above L6 -- there are simply fewer senior management positions to fill than there are qualified managers.
GRAD ratings apply the same way. Performance ratings under Google's GRAD system -- Significant Impact (SI), Outstanding Impact (OI), and Transformative Impact (TI) -- are deliberately separate from promotion decisions. You don't need Transformative Impact to be promoted. That said, sustained Outstanding Impact ratings across multiple cycles are the practical baseline for a credible L7 EM case. A packet built on intermittent Significant Impact ratings will face harder scrutiny.
Two promotion cycles per year. Google runs promotions on a March cycle (primary, more slots) and a September cycle (off-cycle). Manager promotions can be submitted in either cycle, but March carries more weight for L7 cases. If your packet doesn't make it, the next opportunity is roughly six months away.
Heavier political dynamics for manager promotions. EM promotions are more sensitive to org politics than IC promotions because managers compete for organizational resources -- headcount, budget, and decision-making authority. A strong packet can still be blocked if there isn't organizational will to expand your scope. Your director's support and your VP's willingness to restructure the org matter more here than they do for individual contributor packets.
How Long EM to Senior EM Should Take
Google doesn't publish a timeline, and the variance is wide because scope availability is a structural constraint. What patterns emerge from managers who've been through it:
| Timeline | What it looks like | How common |
|---|---|---|
| 2-3 years | Exceptional. Usually means inheriting multi-team scope through a reorg or managing through rapid org growth. | Very rare |
| 3-5 years | The standard successful path. Multiple cycles of sustained evidence, clear scope expansion, business case approved. | Most common for those who get promoted |
| 5+ years | Includes budget deferrals, scope limitations, org restructurings, or a structural ceiling. Google requires 5+ years of technical leadership experience for L7 EM. | Common |
| Never | Many EMs stay at L6 permanently. The org may never need the role. This is not a failure. | Common |
The compensation difference is substantial. Median total compensation moves from approximately $620K at L6 EM to $900K at L7 Senior EM -- a gap of roughly $280K annually, driven almost entirely by equity. EM compensation tracks the same level structure as IC compensation: L7 Senior EM earns the same as L7 Senior Staff Engineer.
What Actually Gets You Promoted
Org-level impact beyond your team
The committee distinguishes between an EM who influences other teams and an EM who is accountable for what multiple teams deliver. Influence is L6. Accountability is L7.
What this looks like in practice: you are responsible for delivery outcomes across at least two teams. When a project slips or a team struggles, your name is on the outcome -- not as a peer who helped, but as the manager who owns the result. This requires actual organizational expansion -- managing additional teams directly or managing through another manager who reports to you.
If you are only responsible for one team, the evidence ceiling is L6 regardless of how well that team performs. The committee has seen hundreds of excellent single-team managers. Single-team excellence does not clear the Senior EM bar.
Growing other managers
At L6, you grow individual contributors -- L3s to L4s, L4s to L5s. At L7, the committee expects you to be developing other managers or building management capability that didn't exist before.
This could mean:
- Managing an EM who reports to you -- direct evidence of L7 scope
- Mentoring a tech lead moving into management -- and that person succeeding in the role
- Building management processes for the broader org -- onboarding frameworks, management development programs, calibration improvements that scale beyond your team
If all your people development evidence points to IC growth, the committee reads that as strong L6 EM work, not L7 work.
Strategic scope that justifies the business case
This is the dimension most unique to EM promotions. The committee isn't just asking whether you operate at L7 scope. It's asking whether the organization benefits from having a Senior EM in your position. You need to demonstrate that your strategic contributions -- roadmap shaping, org design, cross-org alignment -- create value that wouldn't exist without a senior management role.
The evidence here is specific:
- Roadmap ownership -- you co-authored the org's technical and product roadmap with your director, not just executed what was handed to you
- Org design decisions -- you proposed structural changes (new teams, team splits, role realignments) that improved the org's ability to deliver
- Resource allocation -- you made budget, headcount, or prioritization decisions that affected multiple teams
If your director could remove your role tomorrow and redistribute your responsibilities across existing L6 EMs without losing anything, the business case doesn't hold.
VP-level visibility earned through the work
At L7, VPs should know your name, your domain, and your judgment -- not because your director arranged introductions, but because your work at org scale surfaced to that altitude on its own.
What this looks like: you present org-level results directly to VPs. You are consulted on decisions that span your director's entire organization. When a VP asks about the technical health or delivery track record of your area, your director references your leadership as the reason things work.
If your visibility exists only because your manager told the VP about you, the committee will see the gap between the narrative and the evidence.
Mistakes That Keep Managers at L6
Running one team exceptionally well. The most common blocker and the hardest to see from inside it. Your team ships consistently, your engineers give you strong peer reviews, your director is happy. But the committee evaluates scope, not execution quality. A single team managed flawlessly doesn't clear the Senior EM bar. No amount of excellent L6 execution accumulates into L7 evidence. The committee needs organizational scope.
Confusing influence with accountability. Many L6 EMs have significant cross-team influence. They're consulted on decisions, they build relationships with peer EMs, they sit in alignment meetings. The committee is not looking for an influential EM. It's looking for an EM who is accountable for multi-team outcomes. Sitting in the meeting is not the same as owning the outcome. There is a large gap between these two things, and the committee sees it clearly.
Not growing other managers. If every piece of people development evidence in your packet points to IC growth -- coaching L4s to L5, developing senior engineers -- the committee reads that as L6 work. L7 EMs build management capability. If you haven't managed another manager, mentored someone into their first management role, or built management infrastructure for the broader org, you are missing a key dimension of the L7 case.
Ignoring the business case. Some EMs focus entirely on performing at L7 scope and assume the promotion will follow. But EM promotions carry a structural constraint: the org must need the role. If your director hasn't signaled that they're willing to restructure the org to create a Senior EM position, no amount of preparation closes that gap. Have an explicit conversation: "Is there a realistic path to multi-team scope here, and is the org willing to support a Senior EM role?" If the answer is no, a team or org change may be the only way forward.
Building the case too late. Manager promotion packets are evaluated as a body of evidence over multiple cycles, not a snapshot. If you start documenting multi-team impact three months before the promotion window, the packet feels thin. The evidence needs to span at least two to three GRAD cycles. Start building the case 12 to 18 months before you expect to submit -- ideally as soon as you and your director align on the path.
Frequently Asked Questions
How does the EM-to-Senior EM bar compare to the L6-to-L7 IC bar?
Both are L6-to-L7 promotions evaluated at the same level of the organization. Both face dual committee review and the same budget caps. Both require evidence of impact beyond a single team and evidence of growing people at the next level -- other managers for Senior EM, other Staff engineers for Senior Staff. The committee scrutiny is comparable in difficulty. The key difference: EM promotions carry an additional structural constraint. The organization must justify the role, which sometimes requires a formal business case. IC promotions don't have this requirement -- if you demonstrate L7-scope work, the committee evaluates the evidence without asking whether the org "needs" another Senior Staff engineer.
Does my GRAD rating affect promotion eligibility?
Under the GRAD system, performance ratings are deliberately separate from promotion decisions. A Significant Impact rating doesn't block promotion, and Transformative Impact doesn't automatically trigger one. The committee evaluates your packet as a body of evidence -- the scope of your work, the quality of your peer reviews, and the organizational impact you demonstrate. That said, a history of Outstanding Impact ratings signals a sustained trajectory that makes the packet more credible. Consistent Significant Impact with no Outstanding Impact will face harder committee scrutiny at the L7 level.
What if my org doesn't have room for a Senior EM role?
This is a structural problem that no amount of preparation solves. If your director has no intention of expanding your scope to multiple teams, or if the org's headcount and budget don't support a larger management structure, the path to L7 Senior EM on that team is blocked. The honest conversation is: "Is there a realistic path to multi-team scope here, and are you willing to support the business case?" If the answer is no, an internal transfer to a growing org or a team change may be the only viable path. Some managers find that leaving Google and returning at L7 is faster than waiting for internal scope to materialize.
Should I consider leaving and coming back at L7?
Some managers find that the external hire path is faster than internal promotion, particularly if their current org doesn't support expansion. Getting hired elsewhere at a Senior Director or VP equivalent builds a track record outside Google's internal constraints and can result in returning at L7 or higher. Whether this makes sense depends on how confident you are that the internal path is viable, how much organizational capital you'd be leaving behind, and your risk tolerance. It is worth evaluating honestly if you've been at L6 EM for several years without a clear expansion path -- but it's not the right move for everyone.
How important are peer reviews from outside my team?
Very important. The committee evaluates cross-org accountability and alignment by examining what peers outside your team say about you. If every reviewer is someone on your direct team, the multi-team accountability claim doesn't hold. You need peer reviews from partner EMs, adjacent tech leads, PMs from other organizations, and directors who've seen you operate across team boundaries. These relationships take time to build. Start at least two GRAD cycles before your expected promotion window.
CareerClimb tracks your wins, maps them to what Google's promotion committee evaluates, and tells you exactly what evidence you're missing. When the next promotion window opens, your case is already built. Download CareerClimb