How to Get Promoted to Engineering Manager at Google

You've been a strong IC for years. You lead projects, mentor junior engineers, and your team relies on you for technical direction. But making the jump to engineering manager at Google isn't about being a great tech lead. The transition has its own ladder, its own politics, and its own traps that catch experienced engineers off guard.

Most engineers know the broad strokes: become a TLM, manage some people, get promoted. The parts they get wrong are the specifics of what the committee evaluates and how to build a packet that doesn't read like an IC's.

How Google's IC-to-EM Transition Actually Works

At Google, the most common path into engineering management runs through the Tech Lead Manager (TLM) role. There is no single "apply to be a manager" process. Instead, you make a lateral move to TLM, prove you can manage people, and then promote into a full Engineering Manager (EM) role.

Three paths exist:

1. L5 SWE to L5 TLM (lateral move). Take on 2-4 direct reports while staying on the IC ladder. This is the trial run.
2. L5 SWE to L6 EM (diagonal promotion). Demonstrate management capability at L5, then promote directly into a full EM role. Less common.
3. L6 Staff IC to L6 EM (lateral switch). Same level, different ladder. You trade deep technical work for people leadership.

The TLM path is by far the most common. It lets you test management without fully committing. If it doesn't work out, you can switch back to IC without resetting your career ladder.

Promotion mechanics follow the same process as the rest of Google: committee-based, manager-driven, running twice a year through the Googler Reviews and Development (GRAD) system. March is the primary cycle; September is the off-cycle. Your manager assembles your promotion packet and presents it to a calibration committee, following the same performance review process as every other level transition.

The TLM role sits on the IC ladder, which surprises people. You're evaluated on both your technical contributions and your management work. Promoting from TLM to full EM at L6 moves you to the management ladder permanently. Coding becomes optional.

What Engineering Managers Look Like vs. Senior ICs at Google

The gap between a senior IC and a full EM isn't a matter of degree. It's a different job.

Dimension	Senior IC (L5)	Engineering Manager (L6)
Primary output	Technical contributions, design docs, code	Team outcomes, people development, delivery
Scope	Owns projects and technical systems	Owns a team of 8-15 engineers end-to-end
Decision-making	Technical decisions within your area	Hiring, performance reviews, resourcing, career development
Time allocation	80%+ technical work	80%+ people management
Success metric	Personal impact on the codebase	Team's collective impact on the product
Mentorship	Helps junior engineers grow	Accountable for career growth of every direct report

The hardest part of this transition is letting go of the identity that got you here. At L5, you're rewarded for being the person who solves the hardest problems. At L6 EM, you're rewarded for building a team that solves hard problems without you.

"The biggest adjustment was stopping myself from jumping into code reviews and fixing things. My job became making sure my engineers had what they needed to fix things themselves."

The Promotion Criteria That Actually Matter

Google's promotion committee evaluates EM candidates on specific dimensions. Knowing what they look for makes a real difference in how you build your case.

People development. The committee wants evidence that you actively grew engineers on your team. Not "I was available for questions" but specific growth stories with outcomes.

"I identified that an L4 engineer was stuck at feature-level scope, worked with them to take on a design doc for a team-level project, and they shipped it within two quarters. That story carried real weight in my packet."

Team delivery. Your team needs to ship. Not just individually productive engineers, but coordinated execution on priorities that matter. The committee looks for evidence that you set direction, removed blockers, and kept the team focused on the right problems.

Hiring and team building. If you've hired engineers, calibrated candidate quality, and made hard calls on team composition, that carries weight. A TLM who hasn't hired anyone in 18 months has a weaker case than one who built out two new headcount and onboarded them well.

Independent judgment. Can you make hard calls without your manager telling you what to do? Performance conversations, project trade-offs, escalations. The committee wants to see that you handle ambiguity in people situations, not just technical ones.

Step-by-Step: Building Your Case for Engineering Manager

Step 1: Have the Conversation With Your Manager

Don't assume your manager knows you want to move into management. Say it directly: "I want to transition to EM. What would that look like on this team?" Your manager controls whether the TLM path opens up for you. On Team Blind, where engineers are verified by company email, multiple Googlers describe manager support as "at least 85% of the game" for any promotion. If your manager isn't aligned on your promotion timeline, the transition will stall.

Step 2: Take the TLM Path

If your manager supports the transition, the first step is typically becoming a TLM. You'll pick up 2-4 direct reports while continuing your IC work. This is the trial period. Your goal here is demonstrating that you can run 1:1s, give feedback, handle performance conversations, and keep your reports productive.

Step 3: Shift Your Time Toward Management

The TLM trap is spending too much time on code and not enough on people. As a TLM, aim for at least 50% management work. When you promote to full EM at L6, that shifts to 80%. Start building the habit now. Your technical contributions will shrink. That's the point.

Step 4: Document Your Management Impact

The promotion committee reads packets, not minds. Track specific examples as they happen: engineers you grew, hiring decisions, team delivery milestones, hard conversations you handled. At packet time, you'll need concrete evidence, not vague recollections of "managing well."

Step 5: Build Peer Support Across Your Organization

Your peer reviewers matter. Choose people who saw you manage, not just people who like working with you. The PM who watched you navigate a team conflict. The Staff engineer whose new hire you onboarded. The EM on the adjacent team who saw you drive a cross-team initiative. Specific behavioral feedback from these people carries far more weight than generic praise like "great to work with."

Step 6: Time Your Promotion Request

Google runs promotions twice a year through GRAD. March is the primary cycle. Your manager needs to nominate you and write your packet well before the calibration window opens. Have the promotion conversation at least one full cycle before you expect to be ready. If you wait until you think you're "done," you'll often miss a cycle and lose six months.

Common Mistakes That Block the IC-to-EM Transition

Treating management as a side project. TLMs who keep coding 80% of the time and treat management as a checkbox end up with thin packets. Your reports know when you're not invested. The committee will too.

Waiting for the "right" team structure. Some ICs delay the transition because their current team doesn't have open TLM or EM roles. If your manager and skip-level support the move, they can often restructure to create the opportunity. Don't wait for the perfect slot to appear on its own.

Not having hard conversations. The biggest signal that you're ready for EM is handling the uncomfortable parts: critical feedback, underperformance conversations, tough resourcing calls. If your management tenure has been smooth sailing with no difficult conversations, the committee will question whether you've actually been tested.

Confusing technical leadership with people leadership. Being a great tech lead does not automatically make you a great manager. The committee evaluates your people skills separately. If your packet is full of technical wins and light on people development, it reads like an IC packet, not an EM packet.

Going back to IC mode under pressure. Production incidents and tight deadlines pull TLMs back to coding mode. That's natural, but it undermines your management case. The committee wants to see that you coached your team through the crisis, not that you personally saved the day.

Timeline and Realistic Expectations

Path	Typical Timeline	Notes
L5 SWE to L5 TLM	Lateral (no promotion needed)	Usually 1-3 months to arrange with your manager
L5 TLM to L6 EM	1-2 years as TLM	Most TLMs either promote to L6 EM or switch back to IC within this window
L5 SWE to L6 EM (direct)	Uncommon	Requires strong management evidence already gathered at L5
L6 Staff IC to L6 EM	Lateral (no promotion needed)	Same level, different ladder. No committee approval needed for the switch

The fastest TLM-to-EM transitions happen in about 12 months for people who take on substantial management scope right away. The more typical path takes 18-24 months. Google's twice-yearly promotion cycle means you need at least two strong performance periods before the committee sees enough evidence.

The TLM role is not meant to be permanent. If you've been a TLM for three years or more without promoting to EM, your current team may not have enough management scope to support the transition. At that point, consider switching to a team with more headroom.

According to Levels.fyi, the compensation jump from L5 ($418K median total comp) to L6 EM ($570K median total comp) represents roughly a 36% increase. But the real change is in how your day looks and what you're measured on.

Frequently Asked Questions

Can I become an EM at Google without being a TLM first?

Yes, but it's uncommon for internal transitions. The TLM path is the standard on-ramp because it lets you prove management ability with lower risk. Some L6 Staff ICs switch laterally to L6 EM without going through TLM, but that requires strong evidence of people leadership from your IC work. Most external EM hires come in directly at L6, but they've already managed teams elsewhere.

What if I try management and decide it's not for me?

Google's TLM structure exists partly for this reason. Since TLMs stay on the IC ladder, switching back is straightforward. You give up your reports, return to full IC work, and your career ladder doesn't reset. The stigma of "going back" is lower at Google than at most companies, because the TLM role is explicitly designed as a trial.

Do I need to stop coding entirely to be a good EM?

Not immediately. As a TLM, you'll still contribute technically. But by the time you promote to L6 EM, your time allocation should be roughly 80% management and 20% (or less) technical. Full EMs who spend significant time coding often struggle because they're not investing enough in their people. The engineers on your team will notice.

How does this compare to becoming an EM at Meta or Amazon?

Google's TLM path is unusual among big tech companies. At Meta, the IC-to-EM transition is more formal and involves a full role change without the hybrid period. At Amazon, management is embedded into the senior SDE role earlier, with senior SDEs expected to manage smaller teams as part of their responsibilities. Google's approach gives you more time to test the fit before committing to the management ladder permanently.

Is L6 EM a terminal level at Google?

Functionally, yes. Most Google EMs stay at L6 for their entire management career. Promotion to L7 (Senior EM) requires manager-of-managers experience, cross-org impact, and VP-level sponsorship. On Team Blind, L6 EMs regularly describe the L7 promotion as "very hard, 3-5 years or never." For the full breakdown, see Google's engineering manager career ladder.

---

Building a case for EM means tracking more than code contributions. CareerClimb helps you log management wins, people development moments, and team delivery milestones week by week, so your promotion packet writes itself when the time comes.