The job that quietly disappears
Somewhere past sixty engineers, the job you were good at quietly disappears. You can no longer know everyone, follow every decision, or fix what drifts by stepping in — and every habit that got you here starts working against you.
What scales instead is the layer of managers between you and the code. This book is about building that layer well: hiring people who can actually lead engineers, growing the ones you already have, designing teams so the architecture follows, and holding the quality line without writing a single review.
No frameworks, no career ladders — field notes from twenty years of doing it, including the parts that went wrong.
What makes it worth two hours
One transition, covered properly
Not another whole-career survey. The entire book is about the specific point where an org outgrows its leader's head — what breaks, what you still control, and what to build next.
A manager interview loop you can run next week
Four signals that separate people who lead engineers from strong engineers with a title — with the actual questions, the follow-ups, the loop structure and the one-question reference call.
Numbers from a real platform, not a whiteboard
Written from running 90+ engineers across a dozen squads on a multi-country commerce platform — including the modernization programme that retired 77% of upgrade-blocking platform debt.
The chapters other books skip
When a manager isn't working. The promotion that quietly caps a team. What the transition costs the person going through it. The uncomfortable parts get whole chapters, not paragraphs.
Short on purpose
Fourteen tight chapters, around two hours cover to cover. Written for people who do not have time for padding — because the author didn't either.
Four parts, fourteen chapters
Part I — When it stops fitting
The day the org outgrows your head, the intervention trap, and the four levers you actually control.
Part II — Building the layer
Hiring managers, the promotion default, growing the managers you have, and what to do when one isn't working.
Part III — The org is the system
Team boundaries as architecture, distributed work, evidence-led priorities, and bad news at the speed of safety.
Part IV — Holding the line
Measurement and refusal, standing functions over sprints, and what the transition costs you personally.
Full chapter list
- The day the org outgrows your head
- The intervention trap
- What you actually control
- Hiring managers is a different craft
- The promotion default
- Growing the managers you have
- When a manager isn't working
- Team boundaries are architecture
- Distributed by design
- The room where priorities get set
- Bad news at the speed of safety
- Measured and refused
- Standing functions beat sprints
- The uncomfortable part
Who it's for
- Senior engineering managers stepping up to lead through other managers
- New directors and heads of engineering whose org just stopped fitting in their head
- Staff-plus engineers deciding whether they want the second job
- Founders whose engineering team tripled and now feels opaque