Moving from senior IC to engineering manager is the hardest career transition in tech. This guide covers the skills you need to develop, the internal politics you will face, and how to demonstrate management readiness at Google, Amazon, Meta, and beyond.
Is the Engineering Management Path Right for You?
The decision to move from senior IC to engineering manager is not a promotion — it is a career change. The skills that made you a great engineer are not the skills that will make you a great manager. Before committing, ask yourself honestly:
- Do you get more satisfaction from unblocking others than from solving problems yourself?
- Can you have difficult conversations — performance issues, compensation discussions, letting people go?
- Are you comfortable with less concrete feedback? Code compiles or it does not. People management is never binary.
- Can you let go of technical control? Your team will write code you disagree with, and you will need to accept that.
Going back to IC after becoming an EM is harder than you think. You lose technical depth quickly. Make this decision intentionally — it is not easily reversible.
The Skill Shift — What Changes at Each FAANG Level
The transition from senior IC (L5) to engineering manager (L6/M1) requires a fundamental shift in how you spend your time and measure success:
How Your Time Allocation Changes
As a senior engineer, your time was roughly 70% coding, 20% design/review, 10% meetings. As an EM, expect:
- 10% coding (and this should trend toward zero within 6-12 months)
- 20% 1:1s with direct reports — this is your most important work
- 25% cross-functional meetings — product, design, other teams, leadership
- 25% planning, prioritization, and process improvement
- 20% hiring, performance reviews, and organizational work
How Success Is Measured Differently
Your performance is no longer about your personal output:
- Your team's delivery becomes your delivery — if the team succeeds, you succeed
- Team health metrics (retention, engagement, growth of team members) become your KPIs
- Hiring becomes one of your primary responsibilities — at FAANG, EM hiring targets are explicit and tracked
- Your technical influence shifts from "personally building" to "creating an environment where great engineering happens"
How to Prove You Are Ready for the EM Transition
FAANG companies do not promote engineers to EM because they ask. You need to demonstrate management readiness before the role is offered. Here is how:
- Lead a project with 3+ engineers where you do minimal coding — focus on unblocking, coordinating, and ensuring delivery
- Mentor 2-3 junior engineers formally — document their growth and feedback you provided
- Drive a cross-team initiative that requires influencing engineers you do not manage
- Participate in hiring — conduct technical interviews, write feedback, and participate in hiring debriefs
- Document everything: Write a "readiness doc" summarizing your leadership contributions with specific examples and impact metrics
- Ask your manager explicitly: "What specific gaps do I need to close before I am ready for an EM role?" Then close them.
Create a written case for your promotion. List specific examples with dates, team size, and quantified impact. Share this with your manager, skip-level, and HRBP — do not assume they are tracking your leadership contributions.
Your First 90 Days as a New Engineering Manager
The first 90 days set the tone for your entire tenure as an EM. Here is the blueprint successful first-time EMs follow at FAANG:
- Days 1-30: Build relationships. Have 1:1s with every direct report, your manager, your skip-level, product manager, and key stakeholders. Listen — do not propose changes yet.
- Days 30-60: Understand the systems. Learn the team's tech stack, deployment process, on-call rotation, and delivery cadence. Identify the top 3 bottlenecks.
- Days 60-90: Make one visible improvement. Do not try to fix everything. Pick the single biggest bottleneck and fix it well. This builds credibility.
- Ongoing: Protect 1:1 time religiously. Never cancel a 1:1 unless absolutely necessary. The message it sends to your report when you cancel is "you are my lowest priority."
Mistakes New Engineering Managers Make at FAANG
These patterns consistently derail first-time EMs:
- Still coding too much — you are now a multiplier, not an individual contributor. Every hour you spend coding is an hour not spent developing your team.
- Avoiding difficult conversations — addressing underperformance early prevents team morale from collapsing. Waiting makes it worse for everyone.
- Not delegating technical decisions — you do not need to approve every design. Build trust, then let go.
- Treating everyone the same — different engineers need different management styles. Some need structure, others need autonomy. Learn which is which.
- Ignoring team dynamics — interpersonal conflicts do not resolve themselves. Unaddressed, they poison the entire team.
- Failing upward — managing up (your manager, skip-level, VP) is as important as managing down. Your team needs a leader who can advocate for resources and navigate organizational politics.
The best new EMs spend their first year learning to be a good manager. The worst new EMs spend their first year trying to prove they are still good engineers. Let go of being the best coder in the room.
Frequently Asked Questions
Tags
Take It Further with 1-on-1 Coaching
Reading guides is step one. Working with an ex-FAANG engineer on your specific gaps is step two.
Book a Session from $99