The Manager's Path

About the book

Camille Fournier maps the roles a technical leader passes through: intern or new graduate, mentor, tech lead, manager of a team, manager of managers, and director or executive. Each stage gets its own treatment of the skills that change when the job changes. The premise is that management is a craft with learnable mechanics, and that moving from writing code to directing others is the hardest step for most engineers.

The book keeps returning to concrete situations: running one-on-ones, giving feedback that lands, hiring, conducting performance reviews, handling underperformance, and deciding when to delegate technical work. The later sections take up organizational design, managing multiple teams, and the awkward position of a technical leader who must set strategy while staying credible with engineers.

The structure follows career stages rather than abstract principles, so a reader can enter at the chapter matching their current role and read forward. That design suits a reference book as much as a linear read. The subtitle names growth and change, and the book treats both as ongoing problems rather than milestones.

How to read it

Read the chapter for your current stage first, then the one after it. The book works best as a field guide consulted when a specific problem appears, such as a struggling report or a team that keeps missing deadlines. Fournier favors scenarios and checklists over extended argument, so expect short sections and practical advice rather than a sustained thesis.

The prose is direct and unadorned. Some readers will want more depth on organizational politics and executive strategy than the later chapters provide, and the examples lean toward technology companies. Treat the recommendations as starting points to test against your own organization, and note where your context differs from the large-company settings described.

Who it suits

New engineering managers and senior engineers considering a management track will find the most value, especially those promoted for technical skill who need language for conversations they have never had. Tech leads who manage without formal authority will recognize their situation. Experienced managers can use it to structure mentoring of junior leaders. Directors moving into multi-team responsibility will find the later chapters a useful orientation.

Reading considerations

The book reflects the norms of technology companies of its period; hiring practices, remote work, and tooling have shifted since. It is written for software organizations, so managers in other fields should expect to translate. Readers wanting empirical research on management will need other sources, since the guidance rests on practitioner experience rather than cited studies.