The Manager's Path, in detail
The Manager's Path is Camille Fournier's guide to the complete arc of engineering leadership, from tech lead to CTO. Each chapter addresses a different level of the hierarchy and the specific challenges that level introduces — making it unusually useful because you can read the chapter that matches where you are now and the one for where you're going next.
Fournier's central argument is that the skills that get you to each level are not the skills that success at the next level requires. Becoming a tech lead means giving up some individual contribution to create leverage for your team. Becoming an engineering manager means your output is now other people's output. Becoming a manager of managers means you are increasingly removed from the technical details and must lead through culture and systems rather than through direct judgment.
The book is practical and frank about the political realities of large organizations. Fournier writes about how to navigate a bad manager, how to manage someone who is more technically skilled than you are, how to handle the team member who is brilliant but difficult, and how to do a performance improvement plan without it feeling like a formality before a firing. These are the actual problems engineering managers face, and most management books don't touch them.
The later chapters on managing managers and the executive role are less detailed than the early chapters — understandably, since the experiences are rarer and harder to generalize. But the middle of the book, covering the transition from individual contributor to manager and the early years of managing a team, is among the most useful writing available on the subject. Fournier writes from genuine experience rather than theory, and the book reads that way.
The big ideas
- 1.
Each level of engineering leadership requires a different skill set. What got you here won't get you to the next level — and recognizing that transition is the first challenge at every stage.
- 2.
The tech lead role is where many engineers first learn that their output is no longer just their own code. Managing your time so you create leverage rather than just staying productive is the central skill.
- 3.
1:1 meetings are the most important tool a manager has for understanding what's actually happening on their team. They should be regular, predictable, and primarily driven by the direct report's agenda.