Books › Engineering Manager roadmap
Best books for Engineering Managers
A first-year-to-director arc. The opening three books are manager how-tos for people moving up from individual work. The middle set explains output, feedback, people and delivery evidence. The final set moves from running one team to organising several: structure, strategy and scaling management systems. The list is deliberately people-heavy; technical depth is assumed from your engineering background.
12 books in 3 stages, about 3,370 pages (at least 84 hours of reading). The notes are ours, with no ratings or sales claims.
How to choose your books
A short method, so you read the right book for where you are instead of the longest list.
Find your stage
Getting started · 3 books
The mechanics of the first team: one-to-ones, feedback, hiring and what each rung of the ladder asks of you.
Jump to this stage ↓Doing the job · 5 books
Running a team well: measuring output, giving candid feedback, protecting focus, and using delivery research to guide engineering practice.
Jump to this stage ↓Senior and leading · 4 books
Managing managers: team structures, engineering strategy, and the systems that let a growing organisation run.
Jump to this stage ↓
If you are unsure, start one stage lower than you think. Books in a later stage assume the working knowledge the earlier ones give you.
Begin with one book
Our starting pick
The Manager's Path
by Camille Fournier · 2017
It covers the whole ladder from tech lead upward, so it helps whether you are about to take a team or already running one and wondering what comes next.
See the book ↓Then pick by your situation
Choose the next book by the problem in front of you, not by its place in the list.
If you have just been given your first direct reports
read The Making of a Manager (getting started)
If feedback conversations are being avoided or going badly
read Radical Candor (doing the job)
If you are drawing team boundaries or fixing ownership friction
read Team Topologies (senior and leading)
Check it against what Engineering Manager postings ask for
These skills come from our analysis of live Engineering Manager job postings. If one is new to you, its book list sits one click away.
Each step on the scale reflects how often live job postings name the skill, tool or credential, based on our analysis of those postings.
Set a time budget
| Stage | Books | Pages | Reading | At 3 hrs a week |
|---|---|---|---|---|
| Getting started | 3 | 930 | 23 hrs | 8 wks |
| Doing the job | 5 | ≥ 1,110 | ≥ 28 hrs | ≥ 9 wks |
| Senior and leading | 4 | 1,330 | 33 hrs | 11 wks |
| All 3 stages | 12 | ≥ 3,370 | ≥ 84 hrs | ≥ 28 wks |
Treat this as a ceiling, not a target. Read one book at a time, apply it, then move on; read reference-style books in sections. Totals are approximate.
Judge any book before you buy it
Age
This list runs from 1983 (High Output Management) to 2022 (Scaling People). Older books earn their place by teaching principles that do not change. For tools and platforms, buy the latest edition.
Level
Check the stage before the title. A book from a later stage will make sense only once you have faced the problems it solves.
Format
Some books suit reading start to finish; others work as references. Read the reference-style ones in sections, when a problem calls for them.
Fit
Ask what you will do differently the week after you finish. If you cannot answer, the book is for a different moment. Come back to it when the situation arrives.
Getting started
The mechanics of the first team: one-to-ones, feedback, hiring and what each rung of the ladder asks of you.
Start hereThe Manager's Path
by Camille Fournier · 2017
~240 pages~6 hrs to read
Walks the engineering ladder from tech lead to CTO, with what each rung asks of you. Read it before or just after taking your first team, then reread as the role grows.
View book →
The Making of a Manager
by Julie Zhuo · 2019
~290 pages~7 hrs to read
A plain first-manager guide to 1:1s, feedback, hiring and growing a team, written from the author's own early mistakes. Good for new managers moving up from IC work.
View book →
Become an Effective Software Engineering Manager
by James Stanier · 2020
~400 pages~10 hrs to read
Covers the day-to-day mechanics for engineering managers: 1:1s, team health, delivery, hiring and managing up. A practical map for a new manager in the first year.
View book →
Doing the job
Running a team well: measuring output, giving candid feedback, protecting focus, and using delivery research to guide engineering practice.
High Output Management
by Andrew S. Grove · 1983
~240 pages~6 hrs to read
Grove's model of a manager's output as the output of the team around them. Useful for meeting design, delegation and performance reviews; the examples are dated but the logic holds.
View book →Radical Candor
by Kim Scott · 2017
A framework for giving direct feedback while still caring about the person. Helps managers handle hard performance conversations and build a habit of regular, honest feedback.
View book →
Managing Humans
by Michael Lopp · 2007
~330 pages~8 hrs to read
Short essays from a long-time engineering manager on 1:1s, difficult reports, meetings, hiring and handling org change.
View book →
Peopleware
by Tom DeMarco, Timothy Lister · 1987
~250 pages~6 hrs to read
Argues that software projects fail on people and team issues more than on technology. Worth reading for work environment, team formation and protecting focus time for your engineers.
View book →
Accelerate
by Nicole Forsgren, Jez Humble, Gene Kim · 2018
~290 pages~7 hrs to read
Research on what separates high-performing software delivery teams, including deployment frequency and lead time. Gives managers evidence for talking about delivery and engineering practice.
View book →
Senior and leading
Managing managers: team structures, engineering strategy, and the systems that let a growing organisation run.
An Elegant Puzzle
by Will Larson · 2019
~290 pages~7 hrs to read
Systems-thinking essays on sizing teams, org design, migrations, onboarding and engineering strategy. Suited to managers running several teams or moving into manager-of-managers work.
View book →
Team Topologies
by Matthew Skelton, Manuel Pais, Ruth Malan · 2019
~240 pages~6 hrs to read
Describes four team types and three interaction modes for organizing engineering teams around fast flow of change. Helps when you are drawing team boundaries or fixing ownership and handoff friction.
View book →
Good Strategy, Bad Strategy
by Richard P. Rumelt · 2011
~320 pages~8 hrs to read
Breaks strategy into a diagnosis, a guiding policy and coherent actions. Useful for engineering leaders writing a technical strategy and spotting goal lists that pass for one.
View book →
Scaling People
by Claire Hughes Johnson · 2022
~480 pages~12 hrs to read
A former operating executive's playbook on management systems: planning cycles, hiring, performance, org design and communication. For leaders managing managers as the company grows.
View book →
Book links go to Amazon and are affiliate links. As an Amazon Associate I earn from qualifying purchases.
Frequently asked questions
Which book should a Engineering Manager read first?
The Manager's Path by Camille Fournier. It covers the whole ladder from tech lead upward, so it helps whether you are about to take a team or already running one and wondering what comes next.
Do I need to read all 12 books?
No. The list is a menu, not a syllabus. Find your stage (getting started: 3, doing the job: 5, senior and leading: 4), begin with one book (we suggest The Manager's Path), then pick the next book by the problem you are facing at work. Come back to the others when the situation they cover arrives.
How long does it take to read these books?
The 11 books with a known page count add up to about 3,370 pages, roughly 84 hours at 1.5 minutes a page. At three hours a week that is about 28 weeks; at six hours a week, about 14. The list is meant to be read over time, one book at a time, not in one run.
Are these books up to date?
They range from 1983 (High Output Management) to 2022 (Scaling People). Older titles are included because they teach principles that have not changed; for tools and platforms, we favour recent editions. Check the edition before you buy.
Related reading
Some links are affiliate links: we earn a small commission if you buy, at no cost to you. It does not change what we list.