Mostly harmless, conspicuously useful
The Hitchhiker's Guide to Becoming an Engineering Manager
An engineering manager leads software engineering teams, growing people and shaping processes so teams deliver sustainably, which is a perfectly reasonable ambition until you recall that the one-on-one is a meeting that produces no artifacts and all the value, that the estimate is a number pretending to be a promise, that the team is productive until you measure it, and that the underperformance conversation has been postponed into indefinite politeness. You learn to translate "we will ship it soon" into plans, priorities, coaching, and feedback that survive contact with a quarter that has its own opinions. The grand objective is a team that delivers sustainably and grows its people; the daily evidence is usually a one-on-one that surfaced a real concern, an estimate that became a commitment the team can meet, and an underperformance conversation that happened. This guide travels from observing a team to governing engineering strategy, with practical stops at coaching, delivery, technical judgment, and the recurring discovery that the team's health is measured before it is felt.
Level 1 · Novice
Sit in the one-on-one and resist solving it for them
You observe one-on-ones, standups, and retrospectives without leading them, learning how a meeting that produces no artifacts produces all the value and how a team's health is felt before it is measured.
You begin with read-only access: a calendar of one-on-ones, a backlog, a set of standup notes, a retrospective document, and a team health survey expressing recent opinions. Coaching and feedback is the practice of growing engineers through regular one-on-ones, feedback, and career support; team health is the practice of building psychological safety, motivation, and sustainable pace. A one-on-one is a meeting that produces no artifacts and all the value; an estimate is a number pretending to be a promise. You sit with an experienced manager, observe one-on-ones and retrospectives, and read the backlog so you can distinguish a healthy team from a productive team, which are not always the same set.
Suppose you shadow a one-on-one in which an engineer describes a blocker they have not raised in standup. You observe the manager ask, listen, and resist solving it for them; the engineer names the blocker, the manager asks what they have tried, and the engineer proposes a next step. The meeting produces no artifact and all the value: the engineer leaves with a plan they own, and the manager leaves with a concern the standup did not surface. You record the observation, the pattern, and the contrast with the standup where the same engineer said "nothing blocking." One brisk shadow is an anecdote with good posture, not a management practice; but it prevents the assumption that the standup is the team's health.
Words from the spaceship manual, translated
- One-on-one
- A regular meeting between a manager and an engineer, producing no artifact and all the value. It is where the blocker the standup did not surface surfaces, and where the career the review did not discuss is discussed.
- Psychological safety
- The shared belief that the team can raise concerns, admit mistakes, and ask questions without punishment. It is the difference between a team that reports "nothing blocking" and a team that is blocked.
- Standup
- A short daily sync in which engineers report progress, plans, and blockers. It is the meeting that surfaces the blockers the engineer is willing to admit in front of the team, which is not always the same set as the blockers.
- Retrospective
- A periodic review of what worked, what did not, and what the team will change. It is the meeting that turns a quarter's surprises into the next quarter's defaults, when the action items are owned and not merely listed.