Founder's Desk
As it is with many things in software engineering, there's no single agreed-upon answer to what an engineering manager should actually be doing. Before answering "how to become one," it helps to look at where the disagreement comes from, since the path into the role looks different depending on which version of the job you're aiming for.
Three different schools of thought
There are genuinely different schools of thought about what an engineering manager is supposed to do day to day, and that disagreement isn't just academic. It shapes what companies actually look for when they promote someone into the role, and it explains why moving from one engineering organization to another can feel like a completely different job despite the same title.
One school treats the engineering manager as a promoted senior engineer: the strongest technical contributor on the team, elevated to also own people and process. Another treats the role as closer to a product or project manager with technical fluency, someone whose real value is coordination and delivery, not code. A third treats it as a coaching role first, someone whose job is to develop the people on the team, with technical depth as a supporting skill rather than the main event.
None of these is simply wrong. Different organizations, at different stages, genuinely need different blends. But a candidate for the role benefits enormously from knowing which blend a given company actually expects, since the day-to-day job varies significantly depending on the answer.
The skills that actually transfer
If you're considering the move, the most useful preparation isn't a course or a certification. It's spending a few months deliberately practicing the skills above inside your current role, giving feedback proactively, making a call under uncertainty and owning the outcome, mentoring a junior engineer, before the title changes and the stakes of getting it wrong go up.
Preparing for the move before the title changes
Regardless of which school an organization leans toward, a few skills reliably transfer from strong individual contributor to strong manager: the ability to give feedback that's specific enough to act on, the discipline to make decisions with incomplete information rather than waiting for certainty, and enough technical judgment to ask good questions even in areas you no longer code in daily.
What doesn't automatically transfer is the instinct to solve problems yourself. The best individual contributors are often the ones most tempted to just fix things directly rather than coach someone else through fixing it, and that instinct, left unchecked, quietly caps a new manager's team at whatever that one person can personally review and unblock.
The one question worth asking before you accept
Before accepting a management offer, ask directly which of the three models above the company actually expects, and ask for a specific recent example of what the last person in the role spent their time on. The answer will tell you more about the actual job than the title ever will.
