The transition from individual contributor to engineering manager is a career shift, not a promotion. Your success is no longer measured by your own code or designs but by your team’s outcomes, growth, and health. The first 90 days set the tone. Here’s how to use them well.
Mindset: You’re a Manager Now
Your job is to enable others, not to be the best coder on the team. That means:
- Delegating even when you could do it faster yourself. Speed today isn’t the goal; building the team’s capability is.
- Spending time on people and context: 1:1s, alignment with product and other leads, and clearing blockers. That is the work.
- Accepting that you’ll feel behind. You’ll know less about every ticket and every line of code. That’s expected. Your leverage is the team, not your personal output.
First 30 Days: Learn and Connect
Listen more than you talk.
Meet everyone on the team and key partners (product, design, other eng leads). Ask: What’s going well? What’s frustrating? What would they change? Don’t promise big changes yet—just learn.
Understand the system and the work.
Review the roadmap, the architecture, and how work gets done (backlog, prioritization, releases). You don’t need to code it all, but you need enough context to ask good questions and support the team.
Establish 1:1s.
Schedule recurring 1:1s with every direct report. Use them to build trust and understand goals, concerns, and preferences. Make it clear the 1:1 is their time.
Clarify expectations with your manager.
What does “success” look like in the first 90 days? What are the biggest risks or priorities? Align on how often you’ll sync and what you’ll report.
Days 31–60: Align and Prioritize
Identify the biggest levers.
Based on what you’ve heard and seen, pick 1–3 areas to focus on: e.g. delivery, quality, communication, or morale. Don’t try to fix everything at once.
Communicate priorities.
Share with the team what you’re focusing on and why. Invite input. Transparency builds trust and sets expectations.
Start making small improvements.
Fix a process, unblock a dependency, or improve a ritual. Show that you listen and that things can get better. Avoid big reorgs or sweeping changes in the first 90 days unless there’s a clear crisis.
Protect your calendar.
You’ll be pulled in many directions. Block time for 1:1s, thinking, and your own manager’s expectations. Say no to meetings that don’t need you so you can be present where it matters.
Days 61–90: Stabilize and Set Direction
Solidify rituals and norms.
By now you know what’s working. Lock in standups, planning, retros, and 1:1s. Document how the team works so it’s clear for everyone, including new joiners.
Give and ask for feedback.
Start sharing feedback with reports and peers. Also ask for feedback on your management: what’s helping, what’s not. Use it to adjust.
Set goals for the next quarter.
Work with the team and your manager to define clear outcomes for the next 90 days. Tie them to delivery, quality, or team health so everyone knows what “good” looks like.
Reflect on your own growth.
What’s been hardest? What do you need to learn (e.g. delegation, difficult conversations, prioritization)? Share that with your manager and get support—coaching, training, or peer advice.
What to Avoid in Your First 90 Days
- Big, sudden changes to process, structure, or people without listening first.
- Staying in the code as the “tech lead who also does 1:1s.” You have to let go of IC work enough to lead.
- Trying to be everyone’s friend at the cost of clarity and feedback. Be kind and fair; don’t avoid hard conversations.
- Ignoring your own wellbeing. The role is demanding. Protect sleep, boundaries, and support so you can show up consistently.
The first 90 days as an engineering manager are about learning, connecting, and making a few high-impact moves. Focus on the team, align with your manager, and set a rhythm you can sustain. You’ll build the foundation for a successful transition from IC to engineering manager.