When your CTO wants to step down from running engineering and stay on as an engineer, the first decision isn't a job title. It's which seat is about to go empty. Work out whether you're short on strategy or on execution, then choose between a VP of Engineering, a new CTO or interim cover. Do that before anyone announces anything, because the answer also decides what happens to the CTO's title and equity.
This article assumes the CTO is staying with the company in a different role. If they're leaving instead, read what to do if the CTO leaves. For wider reading on this stage, see Startup CTO guides: leadership, diligence and the first hires.
Which gap do you have: strategy or execution?
Riviera Partners, a technology executive search firm, splits the two jobs by direction. The CTO faces outward: technology strategy, architecture, and the board. The VP of Engineering faces inward: delivery, team structure, process, and hiring and developing the engineers. That's the whole definition you need.
Now ask who does each job today. Take six questions and answer them in writing.
- Who decides the architecture and signs off on big technology bets?
- Who talks to the board and investors about technical risk?
- Who closes senior engineering hires?
- Who owns delivery dates and says no to scope?
- Who runs one-to-ones, performance conversations and promotions?
- Who fixes the process when releases slip?
The first three are strategy. The last three are execution. A CTO who says they want to go back to engineering may be telling you they've stopped enjoying the second half. That's our read, not a rule, but it would make the execution seat the likely empty one, and it's the one a VP of Engineering fills.
It also matters what they want to keep. A CTO who wants to code but still wants to set architecture is stepping back from management, not from strategy. A CTO who wants to be an individual contributor with no say over direction is leaving both seats. Those are different hires, so have that conversation first and ask them to be specific.
Riviera calls out a common mistake: keeping a technically strong CTO in a role that includes running the team when the better fix is a VP of Engineering. Don't make the mistake in reverse either. If you promote your best engineering manager to VP and the CTO also leaves the strategy seat, you've covered delivery and left architecture and the board with nobody.
VP of Engineering or new CTO?
Recruiters and commentators publish team-size thresholds for when to add a VP. Treat them as their view, not as a rule. Riviera's view is that the first deliberate hire is typically a VP of Engineering, once the team has grown to the point where delivery and team structure need dedicated attention. It also says that at 150 engineers, running both roles as a single job is a significant organizational risk. Built In, in an article by expert contributor Bobby Mukherjee, argues for bringing in the VP early, warning that if you bring in your VPE too late you risk ceding the opportunity to a competitor or incumbent. It also cautions that a VP brought in too early can burden the team with process at the expense of shipping. These are advisers' views, and the search firm has a market to sell into. Your team's shape matters more than their headcounts.
Here's how we'd map the situations. It's judgment, not sourced data.
| Your situation | Hire | Why |
|---|---|---|
| CTO still sets architecture and talks to the board well, but won't manage people | VP of Engineering | The empty seat is execution. The CTO keeps the strategy seat and stops line management. |
| CTO wants to be an individual contributor with no say on direction | New CTO, or a fractional CTO first | The strategy seat is empty, and a VP can't fill it. |
| Team is small enough that the CTO is also the best coder and reviewer | Senior engineer first, then decide | Hiring a leader doesn't replace the code the CTO ships. |
| Delivery is fine but nobody owns technical strategy or the board relationship | New CTO | The gap is strategy only. |
| You can't tell which gap you have | Interim or fractional CTO | Cover the seat, watch for 60 days, then choose with evidence. |
A new CTO can be a harder sell internally when the old one is still in the building. The team will ask who has the final say on technology. If you go that route, write the answer down before the new person starts. The process for that search is in the full-time CTO search guide.
One more consideration: a VP of Engineering working under a founder-CTO who is now an individual contributor can work well, since the VP gets a clear strategic partner. A VP working under a CTO who has quietly checked out of decisions doesn't. Ask the CTO whether they'll still show up for the architecture arguments. If the honest answer is no, you're hiring a CTO.
What changes for the CTO: title, contract and equity
Treat everything in this section as general information, not legal advice. Have a lawyer read your documents before you announce a change.
Start with the contract. ACAS, the UK employment advice service, says changes to an employment contract need both sides to agree, unless the contract has a clause that lets the employer make a change without agreement. It also lists legal claims, such as breach of contract or constructive dismissal, among the risks of getting this wrong. That's UK guidance only. Other countries have their own rules, so check where the CTO is employed.
Equity is where founders get surprised. Orrick, a law firm, describes standard vesting as depending on the stockholder remaining in continuous service with the company as an employee or consultant. WilmerHale, another firm, notes that if a shareholder ceases providing services to the company, the company has the right to get back any shares that were not then vested.
Neither page says what a role change does. So don't assume the vesting continues, and don't assume it stops. The answer depends on how your stock agreement defines continuous service. A change from CTO to senior engineer is probably still service as an employee, but "probably" isn't good enough when it's the CTO's equity. Read the definition, and read the leaver terms too, in case the conversation turns into an exit.
Two more documents to check before you announce:
- Any board seat is set by your shareholder and investor documents, not by job title. Read them to see whether it's tied to the CTO role or to the person.
- Investor rights or key-person provisions may name the CTO. A role change could trigger a notice you didn't know you owed.
A 90-day handover plan with the CTO still in the building
This plan is editorial judgment, not sourced guidance. The advantage you have over a CTO who resigned is time and goodwill. Use both.
Days 0 to 30: define the split in writing. One page: what the CTO keeps, what moves to the new leader, who decides when they disagree. Share it with the board, then the leadership team, then the engineers. Don't tell the team before the board hears it. Fix the title, contract and equity questions above in this window, not after.
Days 31 to 60: pair on decisions. The CTO and the new VP, new CTO or interim sit in the same reviews, hiring loops, vendor calls and board prep. The CTO hands over the recurring jobs one at a time. For a task-level list of what to hand off and in which order, use the guide to handing off the CTO's workload task by task. Don't hand everything over in one week.
Days 61 to 90: the CTO owns only the new scope, the new leader owns the rest, and you review at day 90. Ask both of them, separately, whether the split is working. If the CTO keeps getting pulled back into management questions, the written boundary was too vague.
How long will the search take, and who covers meanwhile?
The timelines we found come from firms selling search services, so we're not quoting them. Plan from your own last senior hire: how long did it take from opening the role to a signed offer, and add the notice period.
That gap is the real risk. During it, the CTO is half in the old role and half out, and nobody is making execution decisions with authority. A fractional or interim leader covers it. The practical test: if a hard-dated commitment lands in the next quarter, such as a funding round, a launch or a security audit, don't leave the seat unowned.
What this means for your engineering leadership hire
You're deciding which seat to fill, not which title to hand out. Our recommendation, and it's judgment: hire for the empty seat and don't backfill the CTO title by default. If the gap is execution, hire a VP of Engineering and let the CTO keep strategy. If it's strategy, hire a CTO or buy fractional cover. If you can't tell, buy cover first and decide with 60 days of evidence.
Before the announcement, get a lawyer to read the vesting service definition and your investor documents. That's a short task that can prevent a long dispute.
Then pick the bridge. If the search will take months and something is due before it ends, an interim or fractional leader makes sense while you hire. Read that page next if the answer to "who decides in the meantime?" is currently "nobody".
Covering the gap with a fractional CTO through HighCircl
HighCircl matches vetted senior engineers in 72 hours, with a shortlist of 3 to 5 candidates, which helps if the CTO's coding and review load needs covering. For leadership cover while the permanent search runs, see fractional CTOs through HighCircl. There's no minimum hour commitment, so you can start small and scale hours up or down once the VP or new CTO arrives. Roughly 1 in 10 applicants pass our vetting.
FAQ
Is a VP of Engineering higher than a CTO?
Not by default. Often the CTO is the more senior role, owning technology strategy and the board relationship, while the VP of Engineering runs delivery and the team. Some companies put a VP of Engineering under a CTO, and some reverse it. Check the reporting line in the offer, not the title.
Can a CTO step back to an individual contributor without leaving the company?
Yes, if both sides agree. Under UK guidance from ACAS, a change to the contract needs agreement unless the contract allows the employer to change it unilaterally. Equity depends on how the stock agreement defines continuous service, so have a lawyer read it first.
Does the CTO keep their equity if they change role?
It depends on the definition of continuous service in the stock agreement. Orrick ties vesting to continuous service as an employee or consultant, and WilmerHale describes repurchase of unvested shares when services stop. Neither addresses a role change, so read your own documents and don't assume.
When should a startup hire a VP of Engineering?
Search firms give team-size thresholds, and Riviera Partners says the first deliberate hire is typically a VP of Engineering once delivery and team structure need dedicated attention. Treat that as their view. Our test is simpler: hire one when nobody owns delivery and people management and the CTO is the person doing it unwillingly.
Sources
- Riviera Partners: CTO vs VP of Engineering, understanding the difference
- Built In: VP of Engineering or chief technical officer
- Orrick: What is vesting, should initial shares sold to founders be subject to vesting
- WilmerHale Launch: Equity incentives
- ACAS: Changing an employment contract, employer responsibilities