Engineering Manager: the path, one step at a time

Your output is the team now

As an engineer, you could point at a pull request and say you built that. As a manager, your work shows up as a team that ships steadily, hires well, and doesn't burn out. That's harder to see, and for the first few months it feels like you're doing nothing. You'll spend your week in one-on-ones, sprint planning, incident reviews, hiring loops, and roadmap talks with product. Your calendar stops being yours. The engineers who do well here learn to find satisfaction in a teammate's promotion packet the way they used to find it in a clean refactor.

From senior engineer to running a group

1. 1

   Senior Software Engineer

   You own big features end to end and review a lot of code. People judge you on whether your designs hold up and whether juniors get better by working near you. This is where most future managers first mentor someone on purpose.

2. 2

   Tech Lead

   You set technical direction for a small group, break down the work, and still write code, just less of it. You're judged on whether the team hits its plans without heroics. It's a common test run for management, and a good place to find out if you like it.

3. 3

   Engineering ManagerThis guide

   You hire, run one-on-ones, write performance reviews, and decide what the team works on with your product partner. People judge you on delivery, retention, and whether your engineers grow. You may still review code, but you shouldn't be on the critical path for any feature.

4. 4

   Senior Engineering Manager or Director of Engineering

   You manage managers, own a budget and headcount plan, and shape the org chart. This is where the ladder forks. Plenty of people step back to the individual contributor track as a Staff Engineer instead, and good companies treat that as a lateral move, not a demotion.

What hiring managers screen for

Postings for this role lean on people skills first, then enough technical depth to earn an engineer's respect in a design review.

The part nobody warns you about

The hardest part isn't the meetings. It's the conversations. You'll tell a well-liked engineer their work isn't meeting the bar, and you'll do it with a written plan and a follow-up date. You'll deliver a reorg you didn't choose and defend it like you did. You'll say no to a product manager you like, then say it again in next quarter's planning. Some people find this draining in a way code never was, and that's a fair reason to step back. Others find that watching a quiet engineer become the person everyone asks for help is the best part of their work life.

Keeping your technical edge without hogging the keyboard

You'll lose some hands-on sharpness. That's normal. The managers engineers trust keep reading design docs closely, sit in on architecture reviews, and pick up small, low-risk tickets like flaky test fixes or internal tooling. What they don't do is grab the interesting feature and become the bottleneck. Your job in a design review is to ask the question nobody else wants to ask, like how the service fails over or who gets paged when the queue backs up. Engineers notice when you've read the doc. They notice faster when you haven't. If you miss building things badly, a tech lead or staff role may suit you better, and saying so early saves everyone a rough year.

What Engineering Manager postings ask for