CTO and VP Eng are different jobs disguised as the same title.
The confusion between CTO and VP Engineering is not a labeling problem — it's a signal that most companies haven't thought hard about what they actually need. Our simple framing: CTO is the person responsible for whether the technology is right. VP Engineering is the person responsible for whether the team is functioning. At a Series A these can be one person. At a Series C they usually can't, and the companies that keep pretending they can are the ones where engineering is quietly struggling.
The failure mode we see most often is a brilliant first-engineer CTO who is now trying to manage 40 people and hating every minute of it, while the CEO keeps asking when the new product will ship. That's a VP Engineering-shaped hole, and the fix is to hire one — not to 'develop management skills' in a founder who signed up to build things. The symmetric failure is a company that hires a VP Eng first and then wonders why technical direction is muddled and architectural decisions keep getting overturned.
For an engineer thinking about which path to pursue, the honest test is which kind of day you want to have. If your best day is a hard technical call made correctly, aim for CTO. If your best day is a team member you hired turning into someone great, aim for VP Eng. Most engineers lean hard one direction.