What does an Engineering Manager actually do?

Question

Accepted Answer

An Engineering Manager (EM) is responsible for the **people, delivery, and health of a team** — not for writing most of the code. Your job is to make the team more effective than the sum of its parts.

## The four core areas

```text
PEOPLE     → 1:1s, feedback, career growth, hiring, performance, retention
DELIVERY   → planning, removing blockers, predictable execution, quality
TECHNICAL  → enough context to make good trade-off and prioritization calls
ORG        → managing up, aligning the team with business goals, cross-team work
```

## A concrete week

A typical EM week includes 1:1s with each report, a team standup or two, planning or backlog grooming, a stakeholder sync, some hiring (interviews or debriefs), and time to unblock people. Coding, if any, is small and non-critical-path so you never become a bottleneck.

## Pitfalls

- **Staying the best IC.** Your value is now the team's output, not yours.
- **Becoming a pure project manager.** You still own technical judgement and people growth.
- **Hoarding decisions.** Good EMs push decisions down to the team.

## Why it matters

Teams succeed or fail on clarity, trust, and momentum — and those are produced by management, not by one more pull request from you.

Companies promote strong engineers expecting they understand this shift.

Showing you do often separates a hire from a pass.