What should an engineering manager do in the first 90 days?

Listen more than you change. Map people, systems, and stakeholders. Run solid 1:1s. Ship a few small, visible improvements. Save reorgs until you understand the “why.”

Should new EMs change processes immediately?

Usually no. Take notes on friction for 30 days, then run experiments with clear outcomes. Premature process is how you lose the room.

How do I build trust with a new software engineering team?

Keep 1:1s, follow through on commitments, ask for feedback, and don’t dunk on the previous manager. Consistency beats charisma.

10 Tips for Your First 90 Days as an Engineering Manager

Your first 90 days as an engineering manager are not about proving you can still code. They’re about learning the shape of this team so your skills actually land. Here’s a practical 10-tip playbook.

Use this ramp to avoid the common engineering manager mistakes that stall new leaders.

1. Listen for 30 days before you reorganize anything

Write down what looks broken. Many “inefficiencies” exist for political or historical reasons. Ask “why” before “why don’t we.”

2. Schedule 1:1s with everyone in week one

Same questions for all: what’s working, what’s not, what should I know that nobody will say in Slack. Take notes you’ll reuse in month three.

3. Map the deployment and decision paths early

How code ships, who can say no, where incidents go. Triage your ignorance: production path day one; perf review cycle by day thirty.

4. Find the longest-tenured person and buy them coffee

Ask about abandoned initiatives and unspoken rules. Their mental map of the org is worth more than the wiki.

5. Meet your peer managers and key stakeholders

Product, design, support, the EM next door. Ask how your team is perceived. You’ll hear the reputation gap early.

6. Keep one small win in flight

Kill a painful meeting, fix a noisy alert, unblock a hire. Proof you can improve the system without a grand strategy deck.

7. Don’t dunk on the previous manager

Even if they earned it. The team hears disrespect for history as disrespect for them. Change the system; skip the roast.

8. Clarify goals with your boss by day 30

What does success look like in 90 days? Write it down together. Ambiguous mandates create thrash you can’t manage away.

9. Ask for ground truth beyond your directs

If you manage managers — or want signal from ICs — run a short listening pass with the same questions for everyone. Patterns beat anecdotes.

10. Share a 90-day readout with the team

What you heard, what you’re changing, what you’re not. Transparency turns “new manager anxiety” into a shared plan.

For the standing habits after day 90, read 9 things every new engineering manager should know.