Most engineers who want to move into management are waiting for the role to open before they start acting like a manager. That’s the wrong order of operations.
By the time an EM role appears, someone in leadership already has a candidate in mind — usually the person who’s been doing parts of the job informally for the past six months. Here’s how to be that person.
Understand what you’re actually signing up for
Engineering management is a different job than engineering. This sounds obvious but a lot of people don’t internalize it until they’re already in the role.
As an IC, your output is code and architecture. As an EM, your output is team performance, project delivery, and the growth of the people on your team. You’re switching from a craft where you directly control the quality of your work to one where your impact is almost entirely mediated through other people. Some engineers love that shift. Some hate it. Know which you are before you make the move.
The skills that made you a strong IC — deep focus, technical precision, the ability to solve complex problems alone — are partially relevant. The new skills you need are substantially different: active listening, feedback delivery, context switching, navigating organizational dynamics, and being comfortable with problems that don’t have clean solutions.
How to become an engineering manager: start before you have the title
The fastest path to an EM role is to already be doing EM work. Here’s what that looks like in practice:
Mentor junior engineers on your team. Not informally — deliberately. Set recurring check-ins, give structured feedback on their code and their growth, advocate for them in performance conversations. Build the track record of developing people.
Run projects, not just features. Volunteer to own the cross-functional coordination on a project: the stakeholder updates, the dependency tracking, the risk communication. This is core EM work. Doing it as an IC demonstrates you can handle it without the title.
Help with hiring. Get involved in the interview process — either as an interviewer or by helping define the criteria for open roles. This gives you visibility with leadership and familiarity with the team-building side of the EM role.
Identify and own a team process gap. Every engineering team has something that’s slow, unclear, or inconsistent: the on-call rotation, the sprint planning, the technical spec process. Find one and fix it. EMs spend a lot of time on process — showing you can improve one signals you’re ready for more of it.
Have the direct conversation
At some point, you need to tell your manager you want to move into engineering management. Not as a hint — as a clear ask. “I’m interested in moving into an EM role and I want to understand what I’d need to demonstrate to be considered.”
This conversation does several things: it puts your intention on record, it gives your manager the information they need to give you the right opportunities, and it tests whether there’s actually a realistic path for you at this company.
Some managers will welcome this and immediately start routing relevant work to you. Others will be vague or noncommittal. If the response is consistently evasive after you’ve had this conversation two or three times, that’s useful information — the path may not exist here.
What if there are no EM openings?
This is the most common constraint. The team is the right size, the current EMs aren’t going anywhere, and there’s no obvious opening.
A few options:
Look at adjacent teams. Are there teams that are growing where an EM opening is more likely? Internal transfers are faster than external searches, and your track record within the company is an advantage.
Consider an earlier-stage company. Startups and growth-stage companies create EM roles faster than large enterprises. A Senior or Staff engineer at a big company often has a shorter path to EM at a company that’s doubling its engineering team.
Take the external path. There’s a version of this where you demonstrate the EM skillset at your current company, build the resume to support the story, and apply for EM roles at other companies where you’re competing as an experienced IC with demonstrated leadership, not as a first-time manager with no track record.
The title transition
When you get your first EM role, expect the first six months to be harder than you anticipated. You’ll miss writing code. You’ll have decisions made above you that you wouldn’t have made. You’ll have feedback conversations that are uncomfortable. That’s normal — it’s a new job, not a promotion of the old one.
The people who make this transition well are the ones who commit to the new job fully rather than half-managing and half-coding. You can always go back to IC if the role isn’t for you. You can’t do both well at the same time.
What to do next
If you want to understand where your overall career trajectory stands, take the RHINO quiz. It gives you a fast read on the five dimensions most likely to affect how quickly you get where you’re going.
If you’re thinking about the career path more broadly — not just the EM title but what’s available past it — read How to Grow Your Product Manager Career Beyond Features for a parallel look at how adjacent leadership paths work in tech.
If you’d like to build a specific plan for making this transition — timeline, positioning, the conversation to have with your manager — book a free strategy call.