The transition from individual contributor to engineering manager is one of the most challenging career shifts in technology. You are moving from a role where your value was measured by your own output to one where your value is measured by your team's output. This guide helps you navigate the first months of management and build a foundation for long-term success.
Navigating the Identity Shift
Your identity as an engineer is built on technical expertise - you know how to solve problems, write clean code, and debug complex systems. As a manager, these skills become secondary. Your primary skills are now communication, coaching, decision-making, and organisational navigation. This identity shift is disorienting and takes time to process.
Expect to feel less productive initially. Engineering provides constant, tangible feedback - code compiles, tests pass, features ship. Management feedback is delayed and ambiguous - did that one-on-one actually help? Is the team improving because of your leadership or despite it? Learning to measure your impact through different signals takes practice.
Do not abandon your technical identity entirely. You bring a technical perspective that is valuable in management, and maintaining some technical fluency helps you earn credibility and make better decisions. But accept that your primary contribution is now through people, not code.
Your First 90 Days as a Manager
Spend your first month primarily listening and observing. Have one-on-one conversations with every team member to understand their goals, frustrations, and perspectives. Observe team dynamics without immediately trying to change them. This listening period builds trust and gives you the context needed to make informed decisions.
In the second month, start making small, deliberate improvements based on what you learned. Address the low-hanging fruit - a broken process, an unresolved conflict, or a missing team ritual. Early wins build credibility and momentum.
By the third month, you should have a clear picture of the team's strengths, weaknesses, and priorities. Share your observations with the team and your own manager, and begin working on longer-term improvements. Do not try to change everything at once - sustained, incremental improvement is more effective than revolution.
Essential Management Practices to Establish
Hold regular one-on-ones with every direct report - weekly is ideal, bi-weekly at minimum. These meetings are the most important tool in your management toolkit. They are the space for building relationships, providing feedback, discussing career development, and identifying problems early.
Learn to give and receive feedback effectively. Feedback should be specific, timely, and actionable. 'Your pull request descriptions are too brief - they should include the context of why the change is being made so reviewers can evaluate the approach' is good feedback. 'You need to communicate better' is not.
Establish a regular team cadence: standups, planning sessions, retrospectives, and demos. These rituals provide structure that helps the team operate predictably and gives you regular touchpoints to assess team health and progress.
Common First-Time Manager Mistakes
Continuing to do individual contributor work is the most common mistake. New managers often hold onto coding tasks because it feels productive and comfortable. But every hour you spend coding is an hour you are not spending on the management work that the team needs from you. Delegate technical work and trust your team.
Avoiding difficult conversations is another common mistake. Many new managers are afraid to give critical feedback, address performance problems, or push back on their own management. These avoidance patterns allow small problems to become large ones. Learn to have difficult conversations early and directly.
Trying to be everyone's friend rather than their manager creates problems when you need to make unpopular decisions. You can be friendly, approachable, and empathetic without being friends. Maintain the professional boundaries needed to give honest feedback, make hard calls, and treat everyone equitably.
Building Your Support System
Find a management mentor - ideally an experienced engineering manager who can provide guidance, perspective, and a safe space to discuss challenges. Management can be lonely, and having someone who has faced similar situations is invaluable.
Connect with a peer group of other engineering managers. Whether it is a formal programme or an informal group, sharing experiences with peers who understand the role helps you learn faster and feel less isolated.
Invest in your own development. Read management books, attend leadership workshops, and seek out feedback on your management. The best managers are continuous learners who approach management with the same curiosity and rigour they brought to engineering.
Key Takeaways
- Accept that the identity shift from IC to manager takes time - measure your impact through team outcomes, not personal output
- Spend your first 90 days listening, then making small improvements, then addressing longer-term priorities
- Establish one-on-ones, feedback practices, and team rituals as your management foundation
- Avoid common mistakes: clinging to IC work, avoiding difficult conversations, and trying to be everyone's friend
- Build a support system through mentors, peer groups, and continuous learning
Frequently Asked Questions
- Should I still write code as a manager?
- In the early stages of your management career, you may need to write some code, especially on small teams. But your primary value is now in management, and coding should not come at the expense of your management responsibilities. As a guideline, spend no more than 20% of your time coding, and choose tasks that do not block your team if they are delayed. As your team grows, reduce coding further and delegate all technical execution.
- How do I manage engineers who are more technically skilled than I am?
- This is common and completely fine. Your role is not to be the best engineer - it is to create an environment where the best engineers can do their best work. Be transparent about your strengths (people development, strategic thinking, organisational navigation) and respect their strengths (technical depth, architectural vision). The best engineering teams have managers and engineers with complementary, not identical, skills.
- What if I decide management is not for me?
- Trying management and deciding it is not the right fit is a valid and respectable outcome. Many organisations support transitions back to individual contributor roles. If you find that you miss the technical work, do not enjoy the people management aspects, or feel constantly drained by the role, discuss your options with your manager. The experience of management will make you a better IC regardless of whether you stay in management long-term.
Get the New Manager Starter Kit
Download our new manager starter kit with one-on-one templates, feedback frameworks, 90-day planning guides, and common scenario playbooks.
Learn More