Transitioning to engineering management requires more than desire — it requires deliberate preparation, clear communication, and a plan for your first months in the role. This playbook breaks the transition into actionable phases so you know exactly what to do at each stage.
Phase One: Preparation (Three to Six Months Before)
The preparation phase is where most successful transitions are won or lost. Begin by having a direct conversation with your current manager about your interest in engineering management. This conversation serves multiple purposes: it signals your intent, invites your manager to become an advocate, and opens the door to management-track development opportunities.
During this phase, actively seek out leadership experiences that build your management muscles. Volunteer to lead a project, mentor a junior engineer, or run a hiring loop. Each of these experiences provides both skill development and evidence that you can point to when making your case for the transition.
Invest in learning about management as a discipline. Read foundational books on engineering management, attend meetups or conferences focused on engineering leadership, and seek out mentors who have made the transition successfully. The goal is not to become an expert before starting — it is to develop enough fluency to avoid the most common first-time manager mistakes.
Phase Two: The Transition (Month Zero)
Whether you are promoted internally or hired externally, the transition moment itself requires deliberate handling. Communicate clearly with your new team about your management approach, your expectations, and how you plan to support them. If you are transitioning from being a peer, acknowledge the change in dynamic directly — pretending nothing has changed creates awkwardness that undermines trust.
Set up your management operating system immediately. Establish a regular one-on-one cadence with each direct report, schedule recurring team meetings, and create channels for team communication. These structures provide stability during a period of change and signal that you are taking the role seriously.
Have an initial conversation with your own manager about expectations, success criteria, and the support available to you. Understanding what 'good' looks like in your first ninety days prevents you from optimising for the wrong outcomes. Ask for regular feedback during the transition period — weekly check-ins with your manager are not excessive during your first month.
Phase Three: Your First Ninety Days
The first ninety days should be structured around listening, learning, and building trust. Conduct a thorough listening tour — extended conversations with each team member, your product manager, your designer, and key stakeholders. Ask open-ended questions about what is working, what is not, and what they need from their engineering manager.
Resist the temptation to make immediate changes to processes, tools, or team practices. You do not yet understand why things are the way they are, and changes made from a position of ignorance often create more problems than they solve. Instead, document your observations and hypotheses, and plan to validate them over the coming weeks before acting.
By the end of the first ninety days, you should have a clear understanding of each team member's strengths, development areas, and career aspirations. You should have identified the team's most pressing challenges and have a plan to address them. And you should have established enough trust that your team is comfortable giving you honest feedback about your own performance as their manager.
Common Transition Mistakes to Avoid
The most common mistake is continuing to code at the same volume as before. New managers often maintain a full coding workload because it provides a sense of productivity and competence that the ambiguous, feedback-delayed world of management does not. This comes at the cost of neglecting your management responsibilities — the one-on-ones get cancelled, the feedback gets deferred, and the team suffers.
Another frequent mistake is avoiding difficult conversations. New managers often want to be liked and may shy away from giving critical feedback, addressing underperformance, or making unpopular decisions. This avoidance backfires — problems grow worse when ignored, and your team loses respect for a manager who will not address issues directly.
A third mistake is trying to apply engineering thinking to management problems. Engineering problems have deterministic solutions — you can test, debug, and verify. Management problems involve human beings, who are unpredictable, emotional, and complex. Approaches that work brilliantly in code — optimisation, automation, abstraction — often fail when applied to people and organisational challenges.
- Do not maintain a full coding workload — your primary job is now management
- Do not avoid difficult conversations — address issues directly and promptly
- Do not apply engineering problem-solving to people problems uncritically
- Do not make sweeping process changes in your first month
- Do not skip or cancel one-on-ones — they are your most important meetings
Building Momentum After the Transition
Once you have completed the initial transition, focus on building a rhythm that is sustainable long-term. Establish regular practices — weekly one-on-ones, bi-weekly retrospectives, monthly career conversations — that become the predictable foundation of your management approach. Consistency builds trust, and trust is the currency of effective management.
Seek feedback actively and act on it visibly. Ask your team how you are doing, what they need more of, and what you should change. When you receive feedback, demonstrate that you have heard it by making observable adjustments. This feedback loop is how you accelerate your development as a manager and deepen your team's confidence in your leadership.
Connect with other engineering managers in your organisation or community. The transition to management can be isolating — your former engineering peers may not understand your new challenges, and your new management peers may not be available to support you. Building a support network of fellow engineering managers gives you a space to share challenges, exchange ideas, and maintain perspective during difficult periods.
Key Takeaways
- Invest three to six months in deliberate preparation before making the transition
- Set up your management operating system immediately — one-on-ones, team meetings, and communication channels
- Spend your first ninety days listening and learning rather than making immediate changes
- Avoid the most common mistakes: over-coding, avoiding difficult conversations, and applying engineering thinking to people problems
- Build a sustainable rhythm and a support network of fellow engineering managers
Frequently Asked Questions
- Should I tell my team I am new to management?
- Yes. Transparency about your experience level builds trust rather than undermining it. Your team already knows you are new to management — pretending otherwise is unconvincing and creates an awkward dynamic. Instead, acknowledge that you are learning, ask for their patience and feedback, and demonstrate through your actions that you are committed to being an excellent manager. Most teams respond positively to this honesty.
- How much should I code in my first management role?
- In your first management role, limit coding to no more than twenty per cent of your time, and ensure that nothing you code is on the critical path. Your primary job is management — one-on-ones, team health, hiring, and stakeholder communication. If you find yourself coding more than this, it is usually a sign that you are avoiding the harder, less comfortable work of management. Some new managers find it helpful to go cold turkey on coding for the first three months to force themselves to fully invest in the management role.
- What if my team does not respect me as a new manager?
- Respect is earned through consistent, competent action, not through the title itself. Focus on being genuinely helpful — remove blockers, advocate for the team's needs, give useful feedback, and make decisions that demonstrate good judgement. If specific individuals are resistant, have direct one-on-one conversations to understand their concerns. Most resistance to new managers dissipates within the first few months as the team sees evidence of your commitment and capability.
Get Hired as an Engineering Manager
Preparing for the transition? Our programme includes CV templates, interview preparation with model answers, and a step-by-step career strategy for aspiring engineering managers.
Learn More