Why This Book Matters
Published in 2017, Camille Fournier's The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change filled a gap that the technology industry had ignored for years. Plenty of books covered general management theory, but almost none addressed the specific, stage-by-stage challenges of growing from an individual contributor into a senior engineering leader. Fournier, a former CTO of Rent the Runway, wrote the book she wished she had when she started managing.
The book's structure mirrors the career ladder itself. Each chapter focuses on a distinct role — from mentoring and tech lead responsibilities through managing managers, running a department, and eventually operating as a VP or CTO. At each level, the skills that made you successful at the previous level become insufficient, and sometimes counterproductive. Fournier is direct about this: the transition from one level to the next is not a promotion. It is a career change.
The Leadership Ladder
Individual Contributor
Your value comes from the work you produce directly. You build technical credibility by writing excellent code, solving hard problems, and understanding systems deeply. The IC stage is also where you begin learning to be managed — understanding what good management looks like from the receiving end. Fournier emphasizes that being a good IC is not just about technical skill; it is also about communication, reliability, and the ability to work within a team without constant direction.
Tech Lead
The tech lead role is the first major transition point. You are still writing code, but you are also responsible for technical direction, project coordination, and unblocking others. Fournier describes this as the hardest role on the ladder because it is genuinely split between two types of work. The most common failure mode is continuing to operate as an IC — heads-down in code — while the coordination and communication work goes undone. Great tech leads spend as much time ensuring the team is working on the right things as they do working on things themselves.
Engineering Manager
The shift from tech lead to engineering manager is where you give up being the person who does the work and become the person who builds the team that does the work. Your output is no longer measured in code or technical decisions — it is measured in team health, delivery cadence, retention, and the growth of your direct reports. Fournier is blunt about the emotional difficulty of this transition: many new managers feel unproductive because they cannot point to a tangible artifact at the end of the day. The work is conversations, one-on-ones, coaching sessions, and organizational problem-solving — all of which feel less "real" than shipping code.
Director
At the director level, you manage managers. Your job is no longer to coach individual contributors — it is to develop the managers who coach them. Fournier identifies the core director skill as organizational design: structuring teams so that the right work gets done by the right people with minimal coordination overhead. Directors also need strong cross-functional partnerships. Your decisions increasingly affect other departments, and your ability to build trust and alignment with peers in product, design, and operations becomes critical.
VP / CTO
At the executive level, you set technical vision and strategy at organizational scale. You are responsible for the culture of the entire engineering function. Fournier notes that VP and CTO roles require fundamentally different communication skills — you need to translate between the technical reality of your teams and the business language of the executive suite. You also need to make decisions with incomplete information on timelines measured in quarters and years, not sprints. Your relationship with the CEO and board becomes a core part of the job.
The Skill Shifts at Each Level
Fournier's most practical insight is that each transition requires you to let go of the skills that made you successful at the previous level. This is counterintuitive and emotionally difficult. The skills you spent years building become the very habits you need to break:
- IC to Tech Lead: Stop solving every problem yourself. Start ensuring the team is solving the right problems. Let go of being the best coder on the team and focus on making the team's code better collectively.
- Tech Lead to Manager: Stop measuring your day by what you shipped. Start measuring it by whether your team is growing, aligned, and delivering. Give up technical decision-making authority on most issues and trust your tech lead to own it.
- Manager to Director: Stop managing individuals. Start developing managers. Let go of knowing the day-to-day details of every project. Focus on whether your managers have what they need to succeed.
- Director to VP/CTO: Stop thinking in team-sized units. Start thinking in organizational and company-sized units. Your decisions about architecture, hiring strategy, and technical direction now affect hundreds of people and multi-year timelines.
When to Use This Framework
- You are about to take on your first management role. The Manager's Path is the most practical guide available for the IC-to-manager transition in technology. Fournier covers everything from running your first one-on-one to handling your first performance improvement plan. Read the relevant chapter before your first week.
- You are a manager who has just been promoted to manage managers. The jump from managing ICs to managing managers is where many engineering leaders struggle most. Fournier's chapter on this transition covers the specific skill shifts required and the common failure modes that derail new directors.
- You are deciding whether management is right for you. Fournier does not assume everyone should become a manager. She describes the trade-offs honestly — what you gain and what you give up — so you can make a deliberate choice rather than defaulting into management because it is the only visible promotion path.
- You are building a career ladder or engineering growth framework. The book provides a well-structured model for what "senior" means at each level, which translates directly into leveling guides and promotion criteria.
Common Mistakes
- Continuing to code when you should be managing. New managers almost universally struggle with this. Writing code feels productive and familiar. Management work — coaching, aligning, unblocking — feels ambiguous. But if you are still writing critical-path code as a manager, you are not doing the management job. Fournier recommends limiting yourself to non-blocking technical work (code reviews, tooling, documentation) and shifting your production energy fully to people and process.
- Skipping levels in the framework. Each level builds on the previous one. Engineers who jump from IC to director (which happens at fast-growing startups) often miss the foundational management skills — running one-on-ones, giving feedback, coaching performance — that the manager stage teaches. The gaps show up later as the organization scales and requires those fundamentals.
- Treating the ladder as the only path. Fournier acknowledges that management is not for everyone. Strong ICs who are pushed into management against their instincts often become unhappy managers and lose their technical edge. The best organizations offer parallel tracks — Staff Engineer, Principal Engineer — that provide career growth without requiring a management transition.
Putting It Into Practice
Identify which stage of the ladder you are currently at, and read (or re-read) the corresponding chapter of The Manager's Path. Then ask yourself two questions: "What skill from my current level am I still relying on too heavily?" and "What skill from the next level do I need to start building now?" Write down one specific behavior you will practice this week that corresponds to the next level — whether that is delegating a technical decision, running a skip-level one-on-one, or drafting a team strategy document.
If you manage managers, use the framework as a coaching tool. In your next one-on-one with each direct report, ask them which level transition they find hardest and what specific skill they want to develop. The shared vocabulary of the framework makes these conversations concrete rather than abstract.
Cabinet includes The Manager's Path in its coaching library, with structured exercises for each career stage and guided reflection prompts that help you identify the skill shifts required at your current transition point.