Lesson 1 said the CTO title is at least three different jobs. The line that causes the most confusion is the one against VP of Engineering, so this lesson makes it precise.
There is one asymmetry that explains most of the rest.
The VP of Engineering is usually at the top of the management career ladder for engineers. It is a summit. You reach it by being an experienced manager of people, projects, teams and departments, and the ladder below it is made of the same material.
The CTO is not the top of any ladder. Lesson 1 spent four sentences on that. It is a lateral entrance into a different job.
Fournier’s split is one sentence: the VP is usually the one pushing the execution of ideas, while the CTO focuses on larger strategy and the position of technology within the company.
The VP’s work, in her description: a solid handle on processes and details, several in-flight initiatives tracked at once, the development roadmap aligned to the hiring plan, the recruiting process running, and coaching for the engineering management team. She also notes that the VP often owns organizational strategy entirely, and needs a strong business and product instinct to keep the roadmap realistic.
So this is not thinker versus doer. Both roles carry strategy. They carry different strategies: the CTO owns where technology sits in the business, the VP owns how the organization is shaped to deliver it.
At small scale, one person does both, and the two halves compete for the same hours.
Execution work wins that competition by default, because it is urgent, legible and has other people waiting on it. Strategy work has no deadline attached to any single day of it. So the common outcome is a well-run engineering organization whose technology bet has not been re-examined in a year, and nobody notices, because everything visible is going fine.
The tell is not that the person is overworked. It is which half is being starved. The company outgrows one person doing both well before the person notices, because the half that goes missing is the half nobody is filing tickets about.
The most useful sentence in Fournier’s chapter is about what happens when a CTO scales up and hands management to VPs.
Many CTOs give up all their management responsibility, sometimes to the point where the VPs do not report to them. Her verdict: you cannot give up the responsibility of management without giving up the power that comes with it.
If you have no power over business strategy and no ability to allocate people to important tasks, you are at best at the mercy of your influence with other executives, and at worst a figurehead. The managers do not have to disagree with you. They only have to have their own roadmaps, which they do.
Her summary for aspiring CTOs: it is a business strategy job first, and it is also a management job. If you do not care about the business, and you are not willing to take ultimate responsibility for a large team of people attacking that business, this is not the job.
Fournier asks two sets of questions. They are about what you want to spend a Tuesday doing, not about what you would like to be true of yourself.
Signs you might be a good CTO: you might cofound a company one day. You want to oversee technical architecture and the guidelines for evolving it. You are willing to go deep on the business side to ground that architecture in the company’s growth. You are willing to do external events, speaking, selling to customers, and recruiting senior managers and engineers. You are willing to manage and mentor senior individual contributors.
Signs you are on the VP of Engineering path: you enjoy managing people. You enjoy making engineering processes more efficient. You like a broad view of the team’s work and a hand in prioritizing it. You are fascinated by organizational structure. You are good at partnering with product managers. You will trade depth of focus on technology for focus on the effectiveness of the whole team. You would rather sit in a roadmap-planning meeting than an architecture review.
That last one is the sharpest question in the chapter.
One practical note, because it explains something you will run into from either seat.
VP of Engineering is unusually hard to hire, and most companies have to hire it from outside. The job needs someone who can quickly read an organization and win people’s trust. But engineers are reluctant to trust leaders without technical credibility, and managers senior enough to do the job have been out of the code for years and are not interested in a hard technical interview for a role that is mostly organizational management.
Both requirements are legitimate. They just do not fit the same candidate easily, which is why this search takes longer than the headcount plan assumes. Lesson 0017 comes back to what an executive actually does about a search like this.
The fastest route to CTO is to be a technical cofounder, though that guarantees the job only as long as you and the startup grow together. The fastest route to VP of Engineering is to get management experience at a larger organization, then join a growing startup.
Fournier ends the chapter with advice she was given: wanting to be a CTO is like wanting to be married. It is not just the title, it is also the company and the people.
Source: Camille Fournier, The Manager's Path, Ch. 8 'The Big Leagues'
Answer to reveal the explanation. Nothing is scored.
1A CTO moves all four VPs to report to the COO so she can focus on technology strategy. What has she traded away?
Fournier's rule is that you cannot give up the responsibility of management without giving up the power that comes with it. She watched senior people hold the CTO title for large business areas, be respected and technically capable, and still fail, because without direct management they could not put people behind the problems they cared about. A strategy you cannot staff is a suggestion.
2Why is VP of Engineering so hard to hire for?
Two requirements pull against each other. The team needs to believe you could have done the work; the candidate pool at that seniority has been out of the code for years and has better offers than one gated behind an algorithms screen. Most companies still have to hire this role from outside, which is what makes the squeeze bite.
3A company has one person holding both jobs. Which symptom suggests the halves have started to fight?
The tell is not overwork, it is which half is being starved. Execution work is urgent and legible, so it wins the calendar by default. Strategy work has no deadline attached, so a year can pass with the ground game in excellent shape and the company's technology bet never re-examined. Starvation in the other direction looks like a beautiful strategy nobody is staffed against.
4By Fournier's self-assessment questions, who is on the VP of Engineering path?
The roadmap-versus-architecture question is the sharpest one she asks, because it is about what you want to spend a Tuesday on rather than what you would like to be true about yourself. The other three options are all from her CTO list.
5What is the structural asymmetry between the two roles?
The VP role is a genuine career summit, and you get there by being an experienced manager of people, projects, teams and departments. The CTO role is a lateral entrance into a different job, which is why lesson 1 spent four sentences saying it is not the top of the technical ladder. Reporting lines between the two vary by company.