How to Hire a CTO: Define the Role, Assess and Onboard Well
A practical guide for CEOs and founders on hiring a CTO: CTO vs VP Engineering, defining year one success, sourcing, assessment, references, compensation drivers and onboarding.

To hire a CTO, first decide whether you need a CTO or a VP of Engineering, then write down what success looks like after one year. Approach strong leaders directly, since most are not looking. Assess technical judgement and leadership with a real case discussion, take deep references, and agree a 90 day onboarding plan before the offer.
I have held the CTO role and hired engineering leaders. The mistakes I see most come from a role nobody defined, a process that tests confidence instead of judgement and a first month where the new leader guesses what the CEO expects.
CTO or VP of Engineering: decide which role you need
The titles overlap and companies use them differently, so start with the work rather than the title. In most technology companies the split looks like this.
| CTO | VP of Engineering | |
|---|---|---|
| Main focus | Technical direction and how technology serves the business | Running the engineering organisation and delivery |
| Typical questions they own | What should we build on, buy or avoid? Where are the technical risks? | Are we shipping predictably? Is the team healthy and growing? |
| Time spent | Architecture, strategy, key customers, board and investors | Hiring, managing managers, process, planning, delivery |
| Hands-on depth | Often deep, especially in early companies | Usually less coding, more people leadership |
| Works most closely with | CEO, product leadership, sometimes customers | CTO or CEO, engineering managers, product |
| Common failure mode | Strong vision, weak execution and team building | Smooth delivery of the wrong technical choices |
Many companies need both eventually, but rarely at the same moment. If your problem is that releases slip and the team is growing faster than its managers, you may need a VP of Engineering first. If your problem is that nobody owns the big technical decisions, or technology is central to what you sell, you need a CTO.
What your company stage needs from a CTO
The same title means different jobs at different stages. Be specific about yours.
- Early product stage: a hands-on technical leader who still writes code, makes fast architecture choices and hires the first engineers. Comfort with ambiguity matters more than experience running large teams.
- Scaling stage: someone who can turn a small team into an organisation, introduce managers, fix the parts of the system that will not survive growth and keep shipping while doing it.
- Mature or enterprise stage: a leader who sets multi-year technical strategy, manages a leadership team, handles security and compliance expectations and talks credibly with the board and large customers.
Hiring the mature-stage leader for an early company is a classic mismatch, and so is the reverse: a brilliant early builder who struggles once the job becomes managing managers.
Define success in year one
Write three to five outcomes the CTO should deliver in their first twelve months. Make them concrete enough that you and the candidate could agree, a year from now, whether they were met.
For example:
- A technical strategy for the next two to three years, agreed with the CEO and leadership team.
- A stable platform for the product's next phase, with the known reliability or scaling problems resolved.
- An engineering leadership layer in place, with managers or leads hired and owning their areas.
- A predictable delivery rhythm the business can plan around.
- A clear position on security, data and compliance for your customers and regulators.
These outcomes become the backbone of your scorecard, interview questions and onboarding plan. Strong leaders want to know what they are being hired to do.
Agree the brief and scorecard before searching
Turn the outcomes into a written brief: company context, the stage, the year one outcomes, the reporting line, the team today and the must-have capabilities. Then build a scorecard with each capability, what strong evidence looks like and who on the panel tests it.
Typical scorecard areas for a CTO are technical judgement, architecture and systems thinking, building and leading teams, delivery, business and product understanding, communication with non-technical stakeholders, and integrity under pressure. Agree in advance who makes the final decision. For a CTO it is usually the CEO, with the board or co-founders consulted.
Sourcing: most strong candidates are not looking
The leaders you want are usually busy succeeding in their current role. They will not see a job advert, and if they do, they will not apply. A CTO search is almost always a direct search.
That means mapping where suitable leaders work today, such as companies at a similar stage, with similar technical problems or in adjacent sectors, then approaching them personally and credibly. A first message should explain the company, the problem and why this person in particular, without overselling. Senior candidates respond to substance: what the role will own, who they will work with and what the company has already got right.
Expect a slower start: many good leaders say "not now" at first.
Assessing technical judgement and leadership
Interviews for senior technology leaders often reward confidence and fluent storytelling. You need to get beneath that to evidence.
Technical judgement
Ask about real decisions. "Tell me about an architecture choice you made that you later regretted. What did you learn and what did you change?" "Describe a time you decided not to build something." Go several layers down: the constraints, the options considered, who disagreed and what happened. Good leaders can explain trade-offs plainly and admit what they got wrong.
Bring in a senior engineer or architect to test depth where it matters, especially if your product depends on data, AI, payments or high-scale systems.
Leadership
Ask what teams they have built, from what starting point, and what those teams achieved. "Who is the best person you hired, and how did you find them?" "Tell me about someone you had to let go." "How did you handle a peer who disagreed with your technical direction?" Look for leaders who talk about developing people and raising standards, not only about their own decisions.
Run a case discussion, not a test
For a CTO, a case discussion works better than an exercise with a right answer. Pick a real situation from your company, such as a platform that will not scale to the next customer segment, a build or buy decision, or a delivery problem across teams. Share a short written brief in advance and discuss it for an hour or so with the CEO and one or two leaders.
Look at how the candidate frames the problem, what they ask before proposing anything, how they balance speed against risk and how they would explain the decision to the team and the board.
Take deep references
References carry more weight for a CTO than for almost any other hire, because the evidence that matters is spread across years and many people.
- Speak to at least one former CEO or manager, one peer and one person who reported to them.
- Ask about specific situations: a crisis, a difficult hire, a decision that went wrong.
- Ask what the candidate needed help with and what kind of company they would struggle in.
- Ask whether they would hire them again for this kind of role, and listen to how quickly they answer.
- Where you can do so discreetly and with care, speak to someone the candidate did not nominate.
Compensation drivers
CTO packages vary widely, and there is no single market rate. The main drivers are company stage and funding, the scope of the role (team size, budget, customer and board exposure), location and whether the role is remote, the candidate's current package and unvested equity, how scarce their specialism is, and the balance between cash and equity you can offer.
Senior candidates will ask detailed questions about equity and what they would give up to join. Agree the range internally before the search, so you do not lose a strong candidate at the final step.
Running a confidential search
Sometimes the search has to be discreet: you are replacing a current leader or are not ready to tell the team. Approach candidates directly rather than advertising, share the company name only when there is mutual interest and keep the panel small. Plan how you will tell the team, and treat any outgoing leader with respect. Everyone who stays will notice.
Onboarding a new CTO
Agree a first 90 days plan before the start date.
- First month: listen. Meet every engineer, key customers, product and commercial leaders. Review the architecture, incidents, costs and delivery history.
- Second month: share an honest assessment with the CEO and agree priorities against the year one outcomes.
- Third month: present the technical strategy and team plan, and make the first visible changes.
The CEO should meet the new CTO every week in this period. Most leadership hires that go wrong early do so because expectations were assumed rather than agreed.
Frequently asked questions
Should a startup hire a CTO or a VP of Engineering first?
It depends on the problem. If nobody owns the major technical decisions or technology is central to the product, hire a CTO. If the technical direction is clear but delivery and team growth are struggling, a VP of Engineering may be the better first hire.
How long does it take to hire a CTO?
A CTO search usually takes a few months from brief to accepted offer, and senior candidates often have long notice periods on top. A clear brief, an agreed compensation range and a fast, respectful process are the things that shorten it most.
What questions should I ask a CTO candidate?
Ask about real decisions and their consequences: an architecture choice they regret, a team they built, a hire that did not work and a time they said no to the business. Go several layers deep on each, and ask how they would approach a real problem from your company.
Should a CTO still write code?
At an early stage, usually yes, since the company needs a hands-on builder. As the company grows, the CTO's time shifts towards strategy, architecture and leadership, and coding becomes occasional. Agree the expectation upfront so neither side is surprised.
Can I hire a CTO confidentially?
Yes. A confidential search uses direct approaches instead of adverts, shares the company name only when there is mutual interest and keeps the panel small. It is common when replacing a current leader or making a strategic change.
How Sunday Labs can help
Sunday Labs runs leadership hiring for CTOs, VPs of Engineering and heads of data and AI, including confidential searches. We agree the role brief and scorecard with you upfront, and candidates are assessed by people who have built and led product and engineering teams, through structured interviews, case discussions and deep references. A founder reviews the search every week. You can read more about how we work, or start a conversation about the role.




