Moving from a hands-on engineering role into your first leadership role can feel like someone just rewrote your job description overnight. Yesterday, you were debugging production issues and pushing code; today, you’re in back-to-back meetings, talking about sprint velocity and resource planning.
This shift is exciting, but it’s also one of the most underestimated career transitions, especially for engineers. And while the examples we drew here are from engineering, the patterns apply to anyone moving from being an expert individual contributor to leading people.
The challenge isn’t just learning new skills. It’s rewiring how you think about your role, your value, and your success. Research from CEB (now Gartner) shows that 60% of new managers underperform in their first two years, and 87% of senior leaders later say they wish they’d had more formal leadership training early on. Without it, trial-and-error is inevitable and costly.
Here are the four biggest challenges engineers face in this transition, and how to navigate them.
1. The Identity Shift: Letting Go of “Being the Engineer”
For years, your identity was tied to solving technical problems. You could point to the code you wrote or the feature you shipped and say, “I did that.” As a manager, your impact becomes less visible and less tangible.
This can trigger what we call the engineering identity crisis. You’re no longer the go-to problem solver. Your value now comes from multiplying your team’s effectiveness, not from being the smartest engineer in the room.
Leaders who succeed here learn to:
- Stay technically sharp enough to be credible and understand trade-offs
- Accept that technical skills are now a tool for better leadership, not the primary way you add value
- Redefine success in terms of your team’s achievements
McKinsey research reinforces this shift: the highest-performing managers focus 70% of their time on enabling their team rather than doing the work themselves.
2. Communication: It’s Not What You Say, It’s How You Say It
As an engineer, “being right” was often enough. As a manager, being right is just the entry fee. The real skill is in how you communicate, whether you’re giving feedback, managing up, or saying no.
A few key shifts:
- From debugging to coaching: You can’t just point out a flaw and offer a fix. People aren’t code. For example, research by DeNisi & Kluger shows that one-third of feedback actually decreases performance, so understanding why a behavior happens and how to best address it with the employee before jumping into the feedback conversation is critical.
- Translating for non-technical stakeholders: Your job is to bridge the gap between technical detail and business priorities, not to “win” the technical argument.
- Protecting your team’s focus: Saying no isn’t about being unhelpful; it’s about helping stakeholders understand trade-offs and make informed decisions.
3. Delegating Without Losing Your Mind
If you’ve always prided yourself on high standards, delegation can be painful. You know exactly how you’d do it, and watching someone else take a different route can be uncomfortable.
But here’s the truth: the goal of delegation isn’t to get your solution. It’s to get a good solution while growing your team’s capabilities.
Yes, step in if quality or risk thresholds are at stake. But resist “reactive micromanagement” where you jump in midstream without giving the person a chance to course-correct. Leadership IQ found that 46% of new hires fail within 18 months, most often due to a lack of coaching and support, not a lack of technical skill. Over-involvement can stifle that growth.
4. Imposter Syndrome: “Do I Deserve to Lead This Team?”
If you’re managing people with skills you don’t have, more experience than you, or who were once your peers, it’s natural to question yourself.
Many new engineering managers try to overcompensate by reviewing every architectural decision, inserting themselves into every technical discussion, or jumping into debugging sessions. This is ego-driven and exhausting.
Your value as a manager is not proving that you’re still the best engineer. It’s creating the conditions for your team to thrive, even when that means admitting you don’t have the answer. Research from the Center for Creative Leadership shows that humility (acknowledging your limits and seeking input) is a stronger driver of team trust and engagement than technical expertise.
The Bottom Line
Transitioning from engineer to manager is like learning a completely new profession while still being expected to perform at a high level. It’s normal to feel awkward, to miss the clarity of your old role, and to wonder if you made the right move.
But when you:
- Redefine your identity around enabling others
- Master communication that inspires action
- Delegate to develop, not to replicate
- Lead with humility rather than proving your worth
…you set yourself up for a leadership career that’s not just successful, but deeply fulfilling for you and your team.
If you’re navigating this shift now, be patient with yourself. And remember, just like you learned to code, design, or debug, leadership is a skill you can (and should) practice deliberately.
If you’d like to dig deeper into building leadership skills without losing your technical edge, check out our Leadership Accelerator program or book The Confident & Competent New Manager.
