The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change
The clearest map I know of the journey from senior engineer to CTO — and the one book I recommend to every technical person dreading their first management role.

The Field Guide for Engineers Who Suddenly Lead
Almost every engineer I coach hits the same wall. They are the strongest individual contributor on the team, so the org does the obvious thing and makes them a manager. Six months later they are exhausted, their code output has collapsed, and nobody has told them whether that is normal. It is. Camille Fournier wrote the book that should have been handed to them on day one.
A ladder, told one rung at a time
The structure is the genius of it. Fournier takes the engineering career ladder and devotes a chapter to each stage — mentoring, the tech lead, managing one person, managing a team, managing managers, and finally the senior roles of director, VP, and CTO. At every rung she answers the question the title implies: what is the job now, and what do you have to stop doing to be good at it? Because she has held these roles — CTO at Rent the Runway, an engineer long before that — none of it reads as theory. It reads as field notes.
What it gets right
The chapters on the first two transitions are worth the price alone. The move from senior engineer to tech lead, and then to manager, is where most careers quietly stall, and Fournier is unsentimental about the trade. She is also refreshingly concrete: how to run a one-on-one that is not a status meeting, how to give feedback that lands, how to debug a struggling team the way you would debug a system. For leaders in India's growth-stage companies, where titles often outrun any real management training, that practicality is gold.
Where it falls short
It is written from inside the well-funded, fast-scaling startup world, so a few situations — generous headcount, rapid promotion cycles — will not map cleanly onto a leaner org. And the higher you climb, the thinner the later chapters become; the VP and CTO sections gesture at the terrain more than they map it. By then, though, you have the thinking tools to fill the gaps yourself.
The coaching note
The deepest idea in the book is also the quietest: at every level, growth means giving up the thing that just got you promoted. The engineer gives up the code. The manager gives up the team's daily detail. The director gives up being the smartest person in the room. Most of the leaders I work with are not short on capability — they are holding on to an old definition of their job. Read this with a pen, and mark every place it asks you to let go.
On this page
Key Takeaways
- Management is a discipline, not a reward. Being a brilliant engineer earns you the option, not the skills — treat the switch as a career change, not a promotion.
- The one-on-one is your highest-leverage meeting. Not a status update — a regular, protected space for the human and the hard conversations.
- Delegate the work you love. Holding on to the satisfying technical tasks is the most common way new managers throttle their team.
- Your scope changes faster than your instincts. Each rung asks you to let go of what you were just rewarded for; the discomfort is the job.
- Culture is set by what you tolerate. Standards, not slogans, are what your team actually inherits.