These two titles get used interchangeably at small companies, and that causes real hiring mistakes. A founder posts for a CTO, interviews people who are great managers, and hires one. A year later the architecture is a mess and nobody senior is thinking about it.
The roles are different jobs that happen to sit at the top of the same team. Investors and operators also disagree, sometimes strongly, about which one a startup should hire first. This guide sets out the difference, the main arguments on each side, and a simple test for your own team.
CTO vs VP Engineering in one table
Investor Fred Wilson wrote the line most people still quote, in a 2011 post on AVC: "The CTO makes sure the technical approach is correct and the VP Engineering makes sure the team is correct." He describes the ideal CTO as the strongest technologist in the company, and the ideal VP of Engineering as a strong manager, recruiter and problem solver whose job is "to make everyone in the engineering organization successful".
| Dimension | CTO | VP of Engineering |
|---|---|---|
| Main question | Are we building the right thing in the right way? | Is the team shipping well, and is it the right team? |
| Spends time on | Architecture, technical bets, prototypes, research, key customers | Hiring, one-to-ones, planning, delivery, cross-team issues |
| Success looks like | Systems that still work at ten times the load; good technical calls | Predictable releases, low regret on hires, people who stay |
| Often comes from | The technical cofounder | An outside hire with a record of managing managers |
| Direct reports | Few, or a small architecture group | Most of the engineering organization |
| Typical failure | Brilliant, but the team drifts and deadlines slip | Calm and organized, but the technology stops moving forward |
| US pay signal | $184,869 average base on Payscale | $193,048 average base on Payscale |
Payscale's ranges are $107k to $311k total pay for CTOs and $141k to $291k for VPs of Engineering, from pages updated in September and October 2026 and covering every kind of employer. The VP average sitting above the CTO average surprises some founders. Our guess at the reason: plenty of people with the CTO title run very small companies, while the VP title mostly appears once there's a sizeable team to run. At a startup, equity and the founder relationship matter more than either number.
The two schools on who comes first
Hire the VP of Engineering first
Bobby Mukherjee argues this in Built In. He sees the two as "opposing ends of a spectrum", with the people-oriented leader at one end and the deeply technical one at the other. His view is that a startup needs the VP first, and doesn't need its "problem-focused, deeply technical CTO until later in the journey". He also warns about timing: bring the VP in too early "and often the engineering team will become burdened with process". His trigger for the CTO: "Once you're comfortable with your cadence and your quality."
Keep a builder in charge
Jason Lemkin of SaaStr calls a mediocre CTO or VP of Engineering the worst mis-hire a scaling company can make, "because it becomes the death of innovation". He describes the pattern: a company reaches a few million in annual revenue, can't scale, hires a pleasant outside manager, and things get calmer. Then innovation stops, and the founding CTO drifts away. His advice is to look for "an epic hacker and engineer, not just a manager".
Wilson sits between them. He says either model works, that the choice depends on the people you already have, and that it's rare for one person to do both jobs well because they "require very different skills and very different time allocations". That's our view too. Hire for the half of the job your current leader does least well, and make sure the person in charge of the technology can still read the code.
Who to hire first at each stage
Engineering headcounts here are rough markers, our suggestion rather than a rule from the sources.
- Founding team, up to about 5 engineers. Neither title as a separate hire. Wilson notes that early companies usually have neither, and a technical cofounder covers both. If you have no technical cofounder, read how to find one before you hire an executive.
- About 5 to 15 engineers. The technical leader starts losing days to one-to-ones, recruiting and planning. Decide which half they want to keep. A cofounder who loves architecture keeps the CTO title and you hire a VP or head of engineering. A cofounder who enjoys managing may become the VP, and you promote or hire a CTO later. Wilson says the first pattern is more common.
- About 15 to 50 engineers. Both roles usually exist. The VP runs delivery and hiring, and the CTO owns architecture and the technical roadmap. Write down who decides on a new database or a rewrite.
- Beyond that. The VP may have directors under them, and the CTO's role often turns outward, toward big customers, partners and long-range bets.
There's a middle step that founders often skip. Instead of a VP, hire a head of engineering or an experienced engineering manager who still writes some code. The title is smaller, and the role can grow into a VP seat if the team grows. It also avoids handing a senior title to someone before you know how the team will look in two years. If the person outgrows it, promote them. If the company outgrows them, a smaller title makes the conversation easier.
A test: is the bottleneck the system or the team?
Look at the last three months and ask which of these problems keeps coming up. Each one points toward a role.
| What keeps happening | Points to |
|---|---|
| Releases slip and nobody can say why until the week before | VP of Engineering |
| Good engineers leave within a year, or hiring takes months | VP of Engineering |
| Product and engineering argue about every deadline | VP of Engineering |
| Outages or slowdowns trace back to the same old design | CTO |
| Big technical choices get made by whoever is loudest that week | CTO |
| Customers ask technical questions in sales calls that nobody senior can answer | CTO |
If both columns are full, you may need both, but hire one at a time. Two new senior engineering leaders at once makes it hard to tell which hire is working.
Signs you chose wrong
- The team got calmer and slower at once. Lemkin's pattern: smoother releases at first, then nothing ambitious ships, and competitors pull ahead.
- The new leader never touches the code base. Lemkin lists this as a warning sign. A VP doesn't need to write code every day, but should be able to read a design document and argue with it.
- Process arrived before there was much to manage. Mukherjee's warning. Ten engineers with a heavy planning cycle spend more time estimating than building.
- The founding CTO checked out. If the cofounder stopped coming to planning after the VP arrived, the split of decisions wasn't agreed.
- The CTO title went to a hire with nobody to work with. A senior architect who joins a three-person team with the title and no clear remit usually leaves quickly.
Engineering work itself lives in your code and issue tools, and Nautis doesn't replace those. Through Integrations, Nautis agents can act in GitHub and Linear, for example creating a Linear issue, with writes asking for approval by default. When you hire, Jobs and Recruitment posts the role on your careers page, can draft the description, and runs candidates through a six-stage pipeline. For the CTO role on its own, see the startup CTO guide.
FAQ
Does a VP of Engineering report to the CTO?
Sometimes. Fred Wilson says the two are often peers, and that a VP of Engineering can report to the CTO or the other way round, with the second less common. Many startups have both reporting to the CEO.
Can one person be CTO and VP of Engineering?
Early on, yes, and that's normal for a technical cofounder. As the team grows, the jobs pull apart. Wilson says few people do both well because they need different skills and different use of time.
Is CTO vs VP engineering a difference in seniority?
Not mainly. The CTO owns technology and the VP owns the team. Both are senior engineering leaders, and which one sits higher depends on the company and the people.
Should a non-technical founder hire a CTO or a VP of Engineering?
If there's no product yet, look for a technical cofounder or a hands-on CTO who will build, not an executive who will manage. A VP of Engineering needs a team to lead, so that hire comes later.