How to Get Promoted as an Engineering Manager

Your team ships on time. Attrition is low. Your 1:1s run smoothly, your skip-level has no complaints, and your engineers keep getting promoted.

So why aren't you?

If you're an engineering manager wondering what the next level actually requires, you're dealing with a problem that's specific to the management track: the criteria are vague, the feedback is indirect, and other people's work becomes your report card. IC engineers can point to systems they built. You point to a team that runs well, and somehow that's not enough.

The jump from EM to Senior EM is a completely different job, not a reward for doing the current one well. Until someone explains what that different job looks like, you're building a case for the wrong thing.

Why Engineering Manager Promotions Are Uniquely Hard

Three structural problems make EM promotions harder to earn than IC promotions.

Your output is collective. When your team ships a major feature, a dozen people contributed. Your role in hiring the right people, unblocking the architecture debate in week three, and keeping the PM relationship from derailing the timeline is real. It's also invisible to anyone who wasn't in the room. Will Larson calls this the core management paradox: the better you do your job, the less visible your contribution becomes.

Organizational need is a hard gate. ICs sometimes get promoted because their work justifies a higher title, even if the team doesn't strictly need a Staff engineer. EMs almost never get promoted without a structural need. If there's no team of managers to manage, there's no Senior EM role. Your readiness matters less than whether the org chart has room. At Amazon, Ethan Evans estimates 15,000 to 20,000 Senior Managers compete for roughly 3,000 Director positions. The math is brutal.

The chicken-and-egg problem. To prove you can operate at Senior EM, you need to manage managers. But you can't manage managers until someone gives you the role. ICs can take on Staff-level projects to demonstrate readiness. EMs can't simulate the next level as easily.

These aren't excuses. They're the reality. And once you see them clearly, you can work around them.

What Actually Changes Between EM Levels

The biggest misconception about management promotion is that it means "doing the same thing, but with a bigger team." Each level is a fundamentally different job.

Level	Who You Manage	What You Own	Where You Spend Your Time
EM (line manager)	5-15 ICs	Single team delivery	1:1s, sprint planning, hiring, unblocking
Senior EM	15-50 people, including other managers	Multi-team strategy and execution	Coaching managers, cross-org alignment, organizational design
Director	Multiple teams of managers, 50-100+ people	Org-level outcomes	Strategy, executive communication, organizational health

Lara Hogan puts it bluntly: "Your job should change every six months even if you stay put." At the EM level, your success metric is team velocity and people growth. At Senior EM, it shifts to organizational impact across multiple teams. At Director, you're measured on business outcomes.

The practical difference: a good EM runs effective 1:1s, ships reliably, and grows their direct reports. A Senior EM-ready manager does all of that and also contributes to engineering-wide initiatives, mentors other managers, and makes strategic decisions that affect teams beyond their own.

If you're only proving the first set of things, you're building a case for the wrong level.

Four Mistakes That Keep Engineering Managers Stuck

1. Still Writing Production Code

Charity Majors is direct about this: "Your technical skills stop advancing when you become a manager, and instead begin eroding." That's fine. The problem is when you spend 40% of your time on pull requests and feature work because it feels productive.

Code reviews, on-call shifts, and cleanup work are reasonable. Leading a major feature is not. Every hour you spend in the critical path is an hour you're not spending on the cross-org work, strategic thinking, and relationship building that define Senior EM readiness.

You feel productive because you shipped something tangible. Your promotion committee sees someone who hasn't let go of the IC role.

2. Managing Down but Not Up or Across

Your team loves you. Your skip-level barely knows what your team does.

Will Larson identifies this as one of the primary ways EMs get stuck. You're building what the team wants rather than what the organization needs. You're solving problems locally instead of connecting your work to broader goals. Your engineers get promoted because you advocate for them. Nobody advocates for you because leadership doesn't have the data.

Managing up means making sure the people who decide your promotion understand what you and your team accomplished. If your skip-level doesn't know your work, you're invisible where it counts.

3. Firefighting Instead of Building

Production incidents. Escalations. Process gaps. Attrition. Hiring. If your weeks are consumed by reactive work, you never get to the strategic thinking that separates a good EM from a senior one.

You keep firefighting because it feels urgent and valued. Putting out fires proves you're essential. But being essential at your current level is not the same thing as being ready for the next one. The EM who can't stop firefighting is often the EM who hasn't built the systems, the team bench strength, or the delegation habits that would make firefighting unnecessary.

4. Waiting for Scope to Be Handed to You

In a developing.dev interview about Meta's M1 to M2 promotion, a Senior Manager described the decisive moment: presenting their director with an ambitious plan for responsibilities nobody had asked them to own. The director later said that moment was what convinced him.

The EMs who get promoted propose scope expansion. They identify an unmet organizational need, draft a plan, and pitch it. The EMs who stay stuck assume their manager will notice their readiness and hand them a bigger role. That almost never happens. Nobody is coming to assign you the Senior EM responsibilities. You have to take them.

What Actually Gets Engineering Managers Promoted

Four patterns show up across every source, from Will Larson's writing to Ethan Evans' Amazon VP advice to Team Blind discussions.

Demonstrate Impact Beyond Your Team

This is the single biggest differentiator. Contributing to engineering-wide initiatives, mentoring managers outside your org, leading a hiring bar raiser program, owning a cross-team technical standard. Any of these prove you're operating at organizational scope, not just team scope.

Start before anyone asks you to. If you wait for the Senior EM role to do Senior EM work, you'll never get it.

Get a Sponsor, Not Just a Manager

Your manager alone cannot promote you. At most big tech companies, EM promotions go through calibration or committee review. You need someone senior, ideally outside your direct chain, who has seen your impact independently and will say in the room: "We need to promote this person."

Ethan Evans, who promoted eight reports from L7 to L8 at Amazon and contributed to 25+ Director promotions, says sponsorship is the single most important factor. The sponsor gives your case credibility that a manager's recommendation alone does not. Understanding what managers look for when promoting employees helps you build evidence your sponsor can actually use.

Write Things Down and Communicate Frequently

Regular updates to your skip-level matter more than quarterly presentations. A short weekly email summarizing what your teams shipped, what decisions you made, and what's coming next. Frequency beats magnitude.

This solves two problems at once: it builds visibility with leadership, and it creates a paper trail of your impact. When promotion time comes, the evidence already exists. Writing a structured promotion case covers how to turn that paper trail into a document your sponsor can carry into the room.

Ask the Right Question

Ethan Evans recommends one specific conversation: ask your manager, "What would need to be true for me to be up for promotion in nine months?"

Not "how am I doing." Not "what do I need to improve." A direct, time-bound question that forces your manager to name the specific gaps between where you are and where you need to be. If your manager can't answer it, that tells you something too. Either the criteria are undefined, the organizational need doesn't exist yet, or you need a more honest conversation.

When the Org Isn't Going to Promote You

Sometimes the blockers are structural, not personal. If the company isn't growing, new Senior EM roles don't open. If your skip-level doesn't see you as a candidate, no amount of cross-org work changes the outcome. If you've been at the same level for four or five years with positive feedback but no movement, the environment may be the constraint.

Discussions on Team Blind are consistent about this: external moves are sometimes the only realistic path to the next level. Getting hired as a Senior EM at a different company is, in many cases, easier than being promoted internally. Recognizing organizational constraints and acting on them is a legitimate career move.

The management career track has fewer rungs and fewer spots at each rung. Navigating that honestly means knowing when the opportunity exists where you are and when it doesn't.

Build the Case They Need to See

EM promotion is harder to prove than IC promotion. Your work is collective, the criteria are ambiguous, and the org chart has to cooperate. None of that changes.

You control the scope of your impact, the visibility of your contributions, the relationships you build across the org, and the initiative you show in taking on work nobody assigned. Build the evidence for those four things, and when the organizational need opens, you'll be the obvious choice.