Camille Fournier
b. ~1975-77 · American
American engineering executive and author of The Manager's Path, focused on the IC-to-director engineering management ladder.
Best for diagnosing a stuck manager, team, or career ladder in a growing engineering org

About this perspective
What follows is Invisico's interpretation of Camille Fournier's published thinking — a distinct way of reasoning drawn from Fournier's own work, offered as a perspective rather than a recreation of the person.
Bio
Camille Fournier is an American engineering executive and author. She studied computer science, then joined Microsoft before moving to Goldman Sachs, where she became Vice President of Technology. She later took the CTO role at Rent the Runway, where she built the engineering organization through a period of rapid growth and published one of the first engineering career ladders with an explicit separation between individual-contributor and management tracks. She subsequently joined Two Sigma as a Managing Director, staying through 2024, then moved into independent advising and executive work.
Fournier is the author of The Manager's Path (O'Reilly, 2017), which covers the engineering leadership ladder from tech lead through VP, and Platform Engineering (O'Reilly, 2024), co-written with Ian Nowland. She has written on engineering management since 2012 through her Elided Branches blog and subsequent Medium essays.
Philosophical lens
Fournier's core argument is that each rung of the engineering management ladder is a different job, not a bigger version of the one below it. A first-line manager and a director face different accountability structures, different information problems, and different craft requirements. Most engineering leadership pain, in her view, comes from holding people to a role they don't actually have, or from managers who keep doing the job they were promoted out of.
She is equally skeptical of structural over-engineering. Engineer-turned-managers, she argues, consistently try to treat organizations like software systems: clean trees, API-defined interfaces, neat hierarchies. It doesn't work because humans operate on informal networks, trade favors, and negotiate based on shifting circumstances. She calls this the Hyrum's Law of organizations. Flat structures don't fix it; the instinct to form groups and create leaders is too persistent. The discipline of management is continuous adaptation to current conditions, building accountability systems that will eventually be gamed, and holding imperfect org structures longer than feels comfortable when the alternative is losing the people you need.
Recurring themes
- Each management level is a distinct job with its own craft requirements, not a bigger version of the rung below
- The first diagnostic question is always what the role requires, not what the person is capable of
- Accountability systems are harder to build than micromanagement, and every one of them will eventually be gamed
- Over-rigid org structures cost more than they save when they fail to accommodate how people actually grow
- When a team is stuck, start with the smallest fixable process problems rather than talent overhauls or vision-setting
- Management ability is trainable, not innate; hiring for potential without committing to training sets people up to fail
Key concepts
The stuck-manager diagnostic
When a manager isn't working, Fournier narrows the failure to one of three axes: managing down (the team isn't self-sufficient), managing up (the manager isn't proactively sharing information with the skip-level), or managing sideways (peers don't trust or respect the manager enough). Identifying which axis is failing gives the problem a shape. A related check: is the manager still carrying hands-on work a senior engineer could do, which would mean they haven't actually moved into the manager's job?
The role-definition question
Before any judgment about a person's performance or fit, Fournier asks what the role they occupy actually requires. This applies to engineering ladder design and performance conversations alike. A promotion is not a credential for competence; it is an organizational decision that the role needs filling at the next level. Ladders that work as pure skill checklists, where enough boxes checked guarantees promotion, commit a category error in her view.
Small before big
When a team is in a rut, shipping slowly with unclear priorities, the instinct is to reach for a structural fix or a new vision. Fournier argues the failure usually belongs to the manager, and that the better starting point is identifying the smallest fixable process problems: how the team decides what to work on, who is responsible for what. These small wins build momentum that makes larger changes possible.
The time-horizon question
Org design decisions look different over months than over years. Restructuring for short-term efficiency can be the wrong move if it costs people who need a longer horizon to stay. Accepting an imperfect structure for many months is sometimes correct when the goal is retaining engineers across a multi-year period.
Where this voice fits in your decisions
This voice is useful when the question concerns a specific rung of the engineering management ladder: a manager who is stuck, a team that has stopped shipping, a senior manager weighing the transition to managing managers, or a career ladder that needs more precision than a horoscope. It brings operational specificity to questions about management structure and team accountability that general leadership advice tends to smooth over.
Limitations
Fournier has set her own scope explicitly. She does not cover the staff and principal engineer career path or the individual-contributor track beyond senior engineer, having said she is not qualified to advise on a path she did not follow. She does not offer prescriptions for C-suite or executive management either, viewing that as well-covered ground where she lacks novel insight. Questions about company strategy, board dynamics, or enterprise-scale organizational transformation are outside her documented range.
Selected works
- The Manager's Path (2017) — engineering leadership from tech lead to VP
- Platform Engineering (2024) — platform team structure and management (co-authored with Ian Nowland)
- "How Do Managers Get Stuck?" (2017) — the three-axis diagnostic for stuck managers
- "Structural Lessons in Engineering Management" (2022) — org design and the org-as-software failure mode
- "10 Years of Engineering Ladders" (2025) — ten-year retrospective on engineering career ladder design
Further reading
- Elided Branches blog — long-form essays on engineering management since 2012
- "Founders Create Managers" (2024) — accountability systems and the failure modes of founder-mode management
Background
Contemporary · Living & active · Engineering management tradition