How Engineering Managers Get Promoted

Getting promoted as an engineering manager requires a fundamentally different kind of evidence than getting promoted as an individual contributor — and understanding that difference is the first step.

As an IC, you were promoted based on what you built, the technical decisions you made, and the behaviors you demonstrated. As an EM, you are promoted based on what your team delivers, how well you develop your people, and how much organizational trust you have built.

This guide covers what actually drives EM promotions, how to build your case, and how to avoid the stalls that keep capable managers at the same level for years.

What Gets EMs Promoted (The Real Criteria)

1. Team Outcomes

The clearest signal that you are ready for the next level is a track record of your team delivering meaningful outcomes, not just shipping features.

The distinction matters. Shipping features is output. Outcomes are things like:

• A platform migration that improved deploy frequency from twice a week to multiple times per day
• Reducing critical incident rate by 60% over six months through systemic on-call improvements
• Delivering a product initiative that demonstrably moved a business metric your leadership cares about
• Successfully growing the team's scope to absorb a new product area with no increase in headcount

For each major initiative your team has worked on, you should be able to articulate: what was the measurable impact, what specifically did you do as a manager to enable that impact, and who above your direct manager observed it.

2. Scope Growth

Promotions and scope growth are closely linked for managers. Companies promote managers when they have already demonstrated they can handle more than their current role formally requires.

Scope growth takes different forms at different levels:

First-line EM to Senior EM:

• Managing a larger team (typically 7+ engineers)
• Owning multiple product areas instead of one
• Taking on a team in a different technical domain
• Managing a geographically distributed team

Senior EM to Director:

• Managing other managers
• Owning a full platform or product surface
• Setting technical or organizational strategy for a meaningful portion of the engineering org
• Representing engineering in conversations that span multiple teams

If you have been at your current level for 18+ months and your scope has not grown, that is a signal worth exploring with your manager. Either the opportunity does not exist at your company right now, or there is something preventing your manager from expanding your scope — both are worth understanding explicitly.

3. Growing Other Leaders

At more senior management levels, one of the clearest differentiators is whether you are developing other leaders — not just individual contributors.

Growing other leaders means:

• Identifying senior engineers on your team who have leadership potential and creating opportunities for them to exercise it
• Actively sponsoring engineers for stretch assignments and visibility outside your team
• Having a direct report who got promoted because of the environment you created
• Coaching another manager informally and having that relationship be visible

When calibration committees evaluate senior management promotions, they often ask: "Who has this manager grown?" If you cannot name people whose careers materially advanced because of your investment in them, that is a gap.

4. Organizational Impact

Senior managers and directors are evaluated on impact that extends beyond their team's boundary. This includes:

• Influencing how the broader engineering organization approaches a class of problems
• Building relationships of trust with product, design, data science, or other functions that make cross-functional work faster
• Representing your team's technical perspective in company-level planning conversations
• Contributing to hiring, organizational design, or culture-building work

If your impact starts and stops at your team's Slack channel, you are likely missing a key component of senior-level evaluation.

How EM Promotion Differs from IC Promotion

Understanding this difference is not optional — it is the foundational shift in how you build your case.

The visibility row is particularly important. When you were an IC, your pull requests, design docs, and technical decisions were artifacts that spoke for themselves. As an EM, your most important work is conversations, decisions, and interventions that leave no artifact. This means you have to narrate your impact explicitly — in your self-review, in conversations with your manager, and in relationships with stakeholders above your immediate chain.

See Am I Ready for Promotion? A Self-Assessment Guide for the self-assessment framework — it is written for ICs but the core questions about operating at the next level apply equally to managers.

Building the Promotion Case as a Manager

Start 6 Months Before the Cycle

EM promotions almost never happen in a single review cycle. Start building your case explicitly — in conversation with your manager — at least two cycles before you expect to be promoted.

In that conversation, ask:

• What does the next level look like at this company for a manager at my stage?
• Where do you see my impact most clearly? Where do you see gaps?
• What would make my case undeniable in calibration?

The answers to these questions tell you where to focus your energy.

Your Promotion Document

The same one-page promotion case document that works for ICs works for managers — with different evidence categories.

Header: Your name, current level, target level, date

Team outcomes: The 3-4 most significant outcomes your team delivered in the past 12-18 months, with your specific contribution to each

People development: Engineers or leaders you have invested in, with evidence of their growth (promotions, expanded scope, measurable skill development)

Organizational impact: Cross-team, cross-functional, or org-level contributions that extended beyond your team

Scope evidence: Evidence that you are already operating at or above the next level

Development: Areas you are actively working on

Share this document with your manager at least one calibration cycle before your target promotion. Give them time to use it.

Build Your Skip-Level Relationship

EM promotions go through calibration committees that typically include your skip-level and sometimes their peers. If your skip-level does not have a direct, positive impression of your work, your manager is fighting an uphill battle to promote you.

Build this relationship proactively:

• Ask for a monthly 1:1 if you do not already have one
• Bring prepared topics: org-level problems you are working on, team outcomes worth highlighting, questions about company direction that you can help with
• Look for opportunities to present your team's work in contexts where your skip-level is present

This is not political — it is professional. See How to Ask for a Promotion as a Software Engineer for frameworks on managing the promotion conversation itself; most of the principles translate directly to the EM level.

Managing Up Effectively

Managing up is one of the skills that most clearly separates managers who get promoted from those who stall. It does not mean being sycophantic or overly visible — it means keeping your manager informed and aligned so they can do their job effectively.

Keep Your Manager Informed

Your manager is in meetings you are not in. If they do not know about your team's wins, blockers, and context, they cannot represent you accurately.

A weekly written status update (one paragraph in Slack or email) covering:

• What the team shipped or unblocked this week
• Key decisions made and why
• Risks or blockers on the horizon

is more valuable than it looks. It gives your manager the raw material to advocate for your team, and it builds a pattern of reliable communication that compounds over time.

Align Before You Act

Before making a significant decision — changing team structure, escalating a cross-team conflict, hiring for a different profile than planned — brief your manager first. Not to ask permission, but to align.

The managers who get promoted are the ones their managers feel confident delegating to. That confidence is built by demonstrating that you surface the right things at the right time, not by acting independently and reporting later.

Ask for Feedback on Your Promotion Case

Three to four months before the review cycle, explicitly ask your manager:

"If calibration happened today, what would you say about my readiness for the next level? Where would the pushback come from?"

Their answer tells you what to work on. If they are vague, push for specifics. If they say you are ready but then nothing happens, ask what the blocker is.

Common Stall Points for Engineering Managers

Optimizing for team happiness over outcomes. Teams that love their manager but underdeliver do not get their manager promoted. Psychological safety and clear direction matter — but they are means, not ends.

Staying in your lane too strictly. Managers who only own what is explicitly in their job description do not demonstrate readiness for expanded scope. Look for the organizational problems that are not clearly anyone's responsibility and take one on.

Not investing in your reports' growth. If nobody on your team has grown in scope or gotten promoted under your management, that is a visible gap in your record.

Being invisible to leadership. If the people above your manager do not know who you are or what your team does, your manager has to do extra work to champion you. Make their job easier.

Waiting to be asked. The most common reason capable managers stall is that they assume good work speaks for itself. At senior levels, you are expected to proactively manage your own career and have explicit conversations about where you are headed.

Related reading

• Am I Ready for Promotion? A Self-Assessment Guide — The self-assessment framework applies to managers as much as ICs; use it to pressure-test your own readiness before the conversation.
• How to Ask for a Promotion as a Software Engineer — The conversation frameworks and promotion document structure transfer directly to the EM level.
• Questions to Ask Your Manager in 1:1s — Useful both for the 1:1s you run with your reports and for thinking about what you should be asking your own manager.

Build Your Management Impact Record

Seekersy helps engineering managers track team outcomes, development conversations, and organizational contributions — so when promotion season comes, you have a record, not a memory.

Start Tracking Your Impact