What should a new engineering manager focus on first?

Relationships and clarity: 1:1s, how work gets decided, and what “good” looks like for the team. Big process changes can wait until you understand why things work the way they do.

Should new engineering managers still write code?

Stay technically credible through design reviews and pairing — but avoid owning critical-path tickets. If the team can’t ship without you coding, you haven’t built a team yet.

How long until a new EM feels effective?

Most people feel useful around 90 days and competent around six months. The curve is normal — don’t measure yourself by your old IC output.

9 Things Every New Engineering Manager Should Know

Your first months as an engineering manager feel like someone swapped your job while you weren’t looking. The skills that got you promoted — shipping, deep focus, being the hero — can actively hurt you now. Here’s what I wish someone had told me on day one.

New to the role? Start with a concrete plan for your first 90 days as an engineering manager.

1. Your success is no longer your personal output

You’re measured by team outcomes: delivery, quality, retention, and growth. If you still optimize for “I closed the hardest ticket,” you’ll bottleneck the people you’re supposed to multiply.

2. You’re not the best engineer on the team — and that’s fine

Your job is judgment, coaching, and clearing paths. Technical credibility matters; being the strongest coder does not. Ask questions that make seniors sharper instead of answering for them.

3. Protect recurring 1:1s like production

Weekly, on the calendar, rarely cancelled. Report-owned agenda. If you reschedule twice in a row, you’re teaching them they don’t matter. Status goes async.

4. Feedback is a weekly habit, not a review-season event

Small, specific, timely. Situation → Behavior → Impact. Waiting until calibration is how you create surprise — and lose trust.

5. Create clarity and capacity before you create process

On a struggling team, answer two questions first: What’s the goal? Who has time to do it? New rituals on top of chaos just add noise.

6. Don’t take critical-path work

If you’re on the critical path, every meeting you attend delays the release. Sponsor someone else. Stay close via reviews, not ownership.

7. Model a sane relationship with work

Your team copies your calendar. Slack at midnight teaches them to stay online. Take PTO. Leave on time sometimes. Say no to fake urgency out loud.

8. Career conversations are part of the job description

Ask where they want to be in a year. Then build projects and sponsorship that move them. Waiting for them to “bring it up” is how you lose your best people.

9. Asking for help is a management skill

Find a peer EM or mentor in week one. Isolation is the default — and it’s optional. The managers who grow fastest borrow playbooks early.

Next: avoid the classic traps. Read the common engineering manager mistakes guide so you don’t learn them the expensive way.