The First 90 Days as a New Engineering Manager

Your job for the first 90 days is not to improve the team — it is to understand it well enough that your future improvements actually work.

New engineering managers almost universally make the same mistake: they act too fast. They see obvious problems (slow deploys, unclear ownership, unhappy engineers) and move to fix them before they understand the root causes, the history, or the human dynamics underneath. Those fixes often make things worse or cost them the trust they needed to make any fix at all.

This guide gives you a concrete 30/60/90-day plan — what to do, what to avoid, and how to build the foundation that makes everything else possible.

The 30/60/90 Framework at a Glance

Days 1-30: The Listening Tour

Week 1: Get Your Bearings

Before you optimize anything, you need a map.

Operational checklist for week one:

• Schedule 30-minute 1:1s with every direct report (book them all this week)
• Ask your manager for the last 6 months of project post-mortems or incident reviews
• Get read access to the team's roadmap, OKRs, and any active project plans
• Join the team's Slack channels and spend two days just reading without commenting
• Identify who the informal leaders are — the people others go to when something breaks

The 1:1 Listening Framework

Your first 1:1 with each direct report is not a status meeting. Use this question set:

1. What do you love most about working on this team right now?
2. What is the biggest thing slowing you down or frustrating you?
3. What does the team do well that you would hate to see change?
4. What do you think I should know that I probably don't?
5. What does career growth look like for you in the next year?

Take notes. Look for patterns across multiple people. The areas where everyone complains are real. The areas where one person complains might be about that person.

The Stakeholder Tour

Your relationships extend beyond your direct reports. In the first three weeks, have informal 1:1s with:

• Your skip-level manager (understand their priorities and how they measure success)
• Peer engineering managers (understand cross-team dependencies and tensions)
• Your product manager counterpart (understand their view of the team's delivery and relationship)
• Design leads and other cross-functional partners
• Key senior engineers in adjacent teams who interact with your team

The goal is not to gather gossip — it is to understand the system your team lives inside.

What Not to Change in Month One

Do not change:

• On-call schedules or rotation structure
• Sprint cadence or planning rituals
• Tool choices or tech stack
• Reporting structure or team composition
• Any existing projects already in flight

You do not yet know why these things are the way they are. Many of them have history you will only learn about by listening.

Days 31-60: Synthesize and Make Targeted Moves

By day 30 you should have a clear picture of: what the team is proud of, what is broken, what is misunderstood by leadership, and what the team wishes someone would fix.

Now you can start acting — carefully.

Write Your Team Assessment

Before taking action, write a private document (share it with your manager) covering:

• Team strengths: What does this team do exceptionally well?
• Visible gaps: Where are there clear performance or delivery problems?
• Hidden risks: What systemic risks have been normalized that leadership may not see?
• Quick wins: What could be improved in the next 30 days with low risk and high visibility?

This document forces you to synthesize rather than just react, and it surfaces your reasoning so your manager can correct you if you've misread something.

Picking Your Early Wins

Good early wins share three properties:

1. Low risk: They do not disrupt existing team velocity or relationships if they go sideways.
2. High visibility: People can see that something improved.
3. Aligned with team pain: You heard about this from multiple people in your listening tour.

Examples of good early wins:

• Fixing the broken CI pipeline that adds 20 minutes to every deploy
• Writing the runbook that does not exist for the most common incident type
• Getting a long-delayed architectural decision unstuck by facilitating the right meeting
• Removing a redundant approval step in the release process that annoys everyone

Examples of bad early wins:

• Rewriting the onboarding docs based on your own experience (not your team's experience)
• Moving to a new project management tool because you prefer it
• Restructuring code review norms before understanding why they exist

Your 1:1 Operating Rhythm

By day 45, your 1:1s should shift from listening-heavy to a steady rhythm:

• Weekly 30-minute 1:1s with every direct report (do not cancel these)
• A consistent agenda: current work blockers, career development, and one open-ended question you rotate each week
• Private written notes after every 1:1 — you will reference these in performance reviews

See Questions to Ask Your Manager in 1:1s for examples you can adapt for your own 1:1s.

Days 61-90: Build the Foundation for Scale

Write Your Team Strategy

By day 90, you should be able to articulate in writing:

1. Mission: What does this team exist to do? (One sentence.)
2. Current state: Where are we now, honestly?
3. Target state: Where should we be in 6-12 months?
4. Priorities: What are the three most important things we will focus on?
5. Investment decisions: What will we deprioritize to make space for priorities?

This document does not need to be long — one to two pages is ideal. Share it with your manager, your skip-level, and your team. The act of writing it will surface misalignments you need to resolve.

Establish Your Operational Rituals

Consistent rituals create predictability, and predictability builds trust. By day 90, establish:

• Weekly team sync: Stand-up or weekly planning meeting with a consistent format
• Monthly retrospective: What is working, what is not, what will we change
• Quarterly career conversations: Dedicated 1:1s focused entirely on each person's growth and trajectory (separate from your weekly operational 1:1s)
• On-call review: Post-incident or post-on-call-rotation debrief to close the learning loop

Growing Your Engineers

One of your most important functions as a manager is growing the people on your team. Start laying groundwork in months two and three:

• For each direct report, have a clear understanding of where they are on the career ladder and where they want to go
• Identify the one or two stretch opportunities each person needs in the next quarter
• Connect engineers to opportunities for visibility beyond your immediate team (cross-team projects, presentations, design reviews)

If you are newer to thinking through career ladders, Am I Ready for Promotion? A Self-Assessment Guide gives you the IC perspective — useful to understand as you begin thinking about how to frame development conversations with your team.

The Trust Equation

Everything in your first 90 days is ultimately about building trust. Trust with your direct reports. Trust with your manager. Trust with peers.

Trust as a manager is built through:

Consistency: Do what you say you will do. Cancel nothing. Follow up on everything.

Transparency: Tell people what you know, what you do not know, and when you will know more. Uncertainty is fine; silence is not.

Advocacy: Actively represent your team's interests in the rooms they are not in. When your team does good work, make sure the right people hear about it.

Competence signals: You do not have to be the best engineer on the team. You need to demonstrate that you understand the technical domain well enough to make good decisions and support your team effectively.

Common Mistakes New EMs Make

Moving too fast. The urge to prove yourself is real. Fight it. Speed without understanding creates churn and damages trust.

Reverting to IC work. Writing code to feel productive is comfortable, but it crowds out the work only you can do: setting direction, removing blockers, developing people.

Avoiding difficult conversations. Performance problems that existed before you arrived are now yours. Ignoring them signals to the team that you will not hold the bar.

Over-promising to your team. New managers often make commitments upward or downward they cannot keep. Under-promise and over-deliver in your first 90 days.

Treating your manager like a boss, not a partner. Your manager is the most important relationship you have right now. Keep them informed, ask for their perspective before making major decisions, and use them as a sounding board.

Related reading

• Senior Engineer Skills That Transfer to Management — Understanding what transfers from IC work and what you need to rebuild from scratch.
• Am I Ready for Promotion? A Self-Assessment Guide — Useful lens for thinking about where your own reports are in their career trajectories.
• Questions to Ask Your Manager in 1:1s — Frameworks you can adapt for both your 1:1s up and the 1:1s you run with your team.

Track Your Management Growth

Seekersy helps engineering managers build a structured record of team outcomes, development conversations, and leadership evidence — so your growth is visible when it matters.

Start Building Your Management Record