Short answer
Management is a different job, not a senior version of your old one. You stop being measured on what you build and start being measured on what your team ships, which removes the daily feedback loop that made you feel competent. Expect roughly six months before the new job feels like a job you are good at.
The most common piece of advice given to new engineering managers - "it's just like tech lead but with more meetings" - is wrong in a way that costs people their first year. Tech lead is a senior version of engineering. Management is a different profession that happens to require engineering context.
The Feedback Loop You Are Giving Up
As an engineer you had a tight loop: write code, run tests, ship, see it work. That loop is where your sense of competence came from. As a manager the loop stretches to weeks or quarters and the signal is noisy - a good hire pays off in six months, a good coaching conversation pays off in three. Many new managers describe this as feeling useless, when what they actually mean is that the feedback got slower.
What actually changes
- Your output becomes other people's output. You will end weeks with nothing you personally made. This is the job working correctly, not you failing at it.
- Your calendar stops being yours. Maker schedule becomes manager schedule. Deep work has to be defended explicitly or it disappears entirely.
- Information becomes asymmetric. You will know things you cannot share - reorganisations, performance issues, salaries. This is quietly one of the most isolating parts of the job.
- Your mistakes get slower and more expensive. A bad deploy is reverted in ten minutes. A bad hire, a mishandled performance conversation, or a demoralised senior engineer takes months to undo.
Should you do it? Three honest tests
Wanting more money or more influence is a reason to seek a promotion, not specifically this one. Better tests:
- Do you find other people's problems interesting? Not tolerable - interesting. If untangling why two engineers keep disagreeing sounds like a distraction from real work, management will feel like a distraction from real work indefinitely.
- Can you get satisfaction from indirect credit? The team ships, the team gets praised, and your contribution is invisible by design. Some people find this genuinely rewarding and some find it hollow. Both are legitimate.
- Are you willing to be bad at something for six months? You are leaving a role where you were strong for one where you are a beginner, usually without a beginner's permission to be slow.
Keeping technical credibility without doing the work
New managers often try to hold onto credibility by staying on the critical path. This fails twice: you become a bottleneck, and you do the management badly. What actually preserves credibility:
- Review designs, not pull requests. Design review keeps you in the architecture conversation without putting you in anyone's merge path.
- Take the unglamorous small work. Flaky test fixes, dependency upgrades, documentation. Nobody is blocked on you, and you stay fluent in the codebase.
- Ask specific questions in review. "What happens if this retries twice?" demonstrates more technical presence than writing the code would.
Going back is not failure
Some of the strongest staff and principal engineers in the industry managed for two years and returned to individual contribution deliberately. They are usually better ICs for it - they understand roadmaps, headcount and priorities from the inside. If you decide the job is not for you, say so clearly and early rather than quietly doing it badly. "I've given this a real go and I want to go back to building" is a respected sentence in almost every engineering organisation.
Frequently asked questions
Is engineering management a promotion?
It is usually a sideways move with a different scorecard, not a step up the same ladder. Most mature engineering organisations have parallel IC and management tracks where staff engineer and engineering manager sit at the same level and pay band.
How long does it take to feel competent as a new engineering manager?
Around six months to stop feeling like an impostor and roughly a year to feel genuinely good at it. The delay is mostly structural: the feedback loop for management decisions is measured in months, so you accumulate evidence about your own competence slowly.
Should I keep coding as an engineering manager?
Keep enough to stay technically fluent, but stay off the critical path. Design reviews, small non-blocking fixes and reading code work well; owning a feature with a deadline does not, because your management work will always preempt it and you will miss the date.
Can I go back to being an individual contributor?
Yes, and it is common enough to be unremarkable at most companies. Engineers who have managed often return as unusually effective senior or staff engineers because they understand how prioritisation and headcount decisions actually get made.