Fractional CTO vs full-time CTO vs VP of Engineering: how to choose
Three different jobs that get confused for each other. How to tell which one your company needs, from someone who has held all three.
I have been a VP of Engineering twice, a VP of Technology once, a VP of Software Engineering running a 100+ person org, and for the last couple of years a fractional CTO for several companies at once. The titles get used interchangeably in job posts and board decks, and they should not be. They are different jobs with different failure modes. Here is how I separate them, and how I would decide if I were the founder.
The short version
A CTO owns the technology direction of the company: what to build on, what bets to make, how technology makes the business faster or cheaper. A VP of Engineering owns the engineering organization: hiring, structure, process, delivery, and the health of the team. A fractional CTO is a CTO who does the job part time for more than one company, which changes the economics and the scope but not the responsibility.
Small companies collapse all three into one person. That is fine until it is not, and the point at which it stops being fine is usually earlier than people think.
What a CTO is for
The CTO is the technical member of the executive team. The work is outward and forward facing. Which architecture will still make sense in three years. Whether the data platform can support the product the CEO is pitching. What the AI strategy is and whether it is real. How the company looks to technical diligence during a raise or an acquisition. Vendor and platform choices that are expensive to reverse.
A good CTO spends a lot of time with the CEO, the board, customers and sometimes investors. In a small company they also write code. In a large one they usually do not, and the CTO role can drift into a staff position with no reports, which is its own kind of problem.
The failure mode of a strong CTO without a VP of Engineering is a brilliant technical direction and a team that cannot execute it. Hiring stalls, process is improvised, and the engineers are managed by whoever has time.
What a VP of Engineering is for
The VP of Engineering runs the machine. The work is inward facing. Hiring plans and interview loops. Team structure and who reports to whom. Delivery cadence, planning, estimation, and whether the roadmap is believable. On-call, incident response, and the SLOs that make reliability a number instead of a feeling. Career ladders, performance management, and the hard conversations.
At Talent Systems that was most of my week. Eight product lines, teams in North America, Europe, South America and APAC, and a transition from outsourced vendors to in-house teams. What made it work was mechanisms: shared release practices, feature flags, observability, structured intake tied to quarterly business outcomes. None of that is glamorous and all of it is what makes a 100-person org ship.
The failure mode of a strong VP of Engineering without a CTO is a well-run team marching efficiently in a direction nobody has questioned. Delivery is predictable and the architecture quietly becomes a ceiling.
What a fractional CTO is for
A fractional CTO covers the CTO seat for companies that need the decisions but cannot yet justify, or cannot yet attract, a full-time executive. The scope is the full CTO job compressed into one to three days a week, which forces a useful discipline: the fractional CTO has to build mechanisms the team runs without them, because they are not there every day.
In practice I end up doing a lot of VP of Engineering work too, because most companies that hire me have neither role filled. The first 90 days are usually a mix: architecture and platform decisions on one hand, hiring plans, operating cadence and release discipline on the other. Lately a third strand runs through both, which is installing AI and agentic engineering practices the team keeps after I leave. I described the week in detail in what a fractional CTO actually does.
The failure mode of a fractional CTO is a company that needs forty hours of executive attention a week and is getting sixteen. When that happens, the right move is to say so and help hire full time.
A decision framework
Ask four questions in order.
Do you have a product and engineers?
If you have neither, none of these roles is the answer yet. You need a technical co-founder or a build partner. If you have a product and no engineers, a fractional CTO can help you decide what to build, who to hire first, and how to avoid building a team around the wrong foundation.
Is the gap technical direction or execution?
Be honest about which one hurts. If the team ships reliably but you keep discovering that the architecture, the data, or the vendor choices will not support the next stage, the gap is direction. That is CTO work. If the direction is clear but delivery is slow, hiring is stuck, and the team is tired, the gap is execution. That is VP of Engineering work.
Most companies under about thirty engineers have both gaps and one budget line. That is the case for a fractional CTO who will cover both for now and tell you when to split them.
How many hours of executive attention does engineering need?
Count honestly. A team of five with a solid lead and a clear roadmap needs a day or two a week of executive attention. A team of forty mid-reorg with an outage every week needs someone there every day. If the answer is full time, a fractional engagement is a bridge, not a destination.
Can you attract the full-time hire you need?
Experienced CTOs and VPs of Engineering are expensive and selective. Early-stage companies often cannot get the person they need, and the person they can get is a first-time executive learning on your payroll. A fractional CTO gives you an experienced operator now, and part of the job can be helping you recruit and onboard the permanent leader.
Common patterns by stage
Pre-seed to seed, non-technical founder. Fractional CTO. You need decisions and a hiring plan, not a payroll line. The engagement often starts at one day a week and grows.
Seed to Series A, technical founder. The founder is the CTO and should stay that way for now. If the team is past about eight engineers and the founder is spending more time managing than building, hire a head of engineering or an engineering manager. A fractional CTO can work well here as a peer to the founder on architecture and org design.
Series A to B, team of fifteen to forty. This is where the roles split. The common choice is a full-time VP of Engineering, because execution is the bottleneck, with the technical founder or a fractional CTO holding direction. The reverse, a full-time CTO with no VP of Engineering, works only if the CTO is genuinely good at running an org.
Series B and beyond. Both roles, full time, and the question becomes who reports to whom. Either answer works if the two people respect each other. It fails when they compete.
Interim is a different thing again
An interim CTO or VP of Engineering is a full-time leader on a fixed term, usually covering a departure or a transition. The scope is the whole job, every day, with a planned end date and a handoff. I take interim engagements when the situation calls for it, and the practical difference from fractional is the hours and the exclusivity. If your previous leader just left and the org is large, interim is usually the right shape and fractional is not.
The title matters less than the agreement
Whichever you choose, write down the scope. What decisions does this person own. Who do they report to. What are the metrics they are accountable for in the first 90 days. How much time are they committing and how will you both know when that needs to change. Most of the painful engagements I have seen, full time or fractional, were painful because that agreement was never made.
If you are weighing this for your own company, the fractional CTO page explains how I work, the engineering leadership consulting page covers the org and delivery side, my resume has the history, and you can reach me through the contact page. I am happy to tell you that you need something other than what I do, if that is the honest answer.
Frequently asked questions
Is a fractional CTO cheaper than a full-time CTO?
Usually, because you pay for one to three days a week instead of a full salary, equity and benefits. The better comparison is value: you get an experienced executive now, at the scale you need, instead of a full-time hire you may not be able to attract yet.
Can a VP of Engineering do the CTO job?
Some can. The roles need different instincts: a CTO is judged on technical direction and bets, a VP of Engineering on the health and output of the org. In a small company one person often covers both. Past thirty or forty engineers it is worth splitting them.
Should a startup hire a CTO or a VP of Engineering first?
If the founder is technical, usually a VP of Engineering or head of engineering first, so the founder can keep owning direction while someone else runs the team. If the founder is not technical, a CTO or a fractional CTO first, so the technical decisions have an owner.
What is the difference between an interim CTO and a fractional CTO?
An interim CTO works full time for a fixed period, usually covering a departure. A fractional CTO works part time on an ongoing basis, often for more than one company. Interim fits a large org in transition; fractional fits a company that needs senior decisions but not forty hours a week.
Kris Chase
@krisrchase