Do we need to hire a CTO?

1. Find the responsibility behind the frustration

“We need a CTO” often follows a difficult conversation: a roadmap slips, a supplier’s proposal is hard to evaluate, or the founder becomes the final decision-maker in every technical disagreement. The concern is real. The right appointment depends on the responsibility underneath it.

Take several recent decisions that were delayed, escalated repeatedly or made without enough confidence. Who was expected to decide? What information or authority was missing? Did the decision concern business priorities, technical direction, people management or the amount of work the team could take on?

If capable people already own those responsibilities, start by examining how they work together. An additional title can complicate an unclear arrangement. If no one is accountable for connecting technology investment, risk and capability to the business’s direction, the executive gap deserves attention.

2. Separate four kinds of need

A small business may combine these responsibilities in one person. A larger or more complex business may distribute them. Make the split explicit before choosing the job title; otherwise candidates will be solving different versions of the problem.

Technology direction and investment

Who explains the technology options, sets direction and takes responsibility for the trade-offs with the rest of the leadership team? This can support a CTO mandate.

Engineering management and execution

Who develops engineers, organises work, deals with dependencies and improves delivery? A Head of Engineering or engineering manager may be the more precise appointment.

Product and commercial priorities

Who decides which customer problems matter and which commitments the business will make? A CTO needs a workable relationship with that owner; technical leadership alone cannot settle conflicting business priorities.

Specialist capability or capacity

Who can perform a defined piece of architecture, security, migration or implementation work? A specialist or delivery partner may meet the need without creating a broad executive role.

3. Write a mandate before a job description

Describe what the appointee should own, what remains with other leaders and what they can change. “Own technology” is too broad to guide hiring. A mandate should explain the business context, the decisions that recur and the authority available to make them.

Include the difficult parts of the environment: an established technical founder, a trusted long-standing supplier, a partially completed rewrite, or commitments already made to customers. Candidates need to understand those constraints, and you need to hear how they would work within them.

Agree the reporting line and the division of responsibilities with existing leaders before interviews. If the founder intends to retain final control over architecture, hiring and investment, explain that clearly and assess whether the role has the authority needed to deliver its expected outcomes.

4. Match the appointment to the workload

A permanent executive can be appropriate when the responsibilities are enduring and require sustained attention. A fractional CTO can fit recurring senior leadership work with a manageable part-time remit and effective day-to-day ownership elsewhere. An interim leader can cover a vacancy or transition while the longer-term structure is decided.

Availability matters as much as the role description. Ask what happens when a decision is needed between scheduled days, who manages the team in the meantime and which issues must wait. If the appointment depends on constant informal availability, revise the capacity or the remit.

For one consequential decision with an operating team already in place, a defined independent review may be enough. It can also help clarify the mandate before a search. Your reason for commissioning it should be the uncertainty it resolves; a hiring process does not automatically require a preliminary review.

5. Ask for evidence of judgement

Use the mandate to design the assessment. Familiar company names and confidence in an interview give an incomplete view of how someone will operate in your setting. Ask for concrete examples, the alternatives considered and what happened after the decision.

Give candidates the same concise, anonymised business scenario, explain its limits and ask which questions they would investigate first. Discuss their reasoning live. Keep the exercise proportionate; you are assessing judgement and communication, rather than obtaining a free strategy for a live project.

A consequential trade-off

Ask about a decision where delivery, reliability, team capability and commercial pressure pointed in different directions. What did they choose, who disagreed and what changed their view?

Work through other leaders

Ask how they developed a technical lead, resolved conflicting ownership or made a decision with product and commercial colleagues. Explore their own contribution and the team’s.

An intervention that fell short

Ask what they initially misunderstood, how they recognised it and what they changed. Look for an explanation grounded in evidence and responsibility.

A relevant reference conversation

With the candidate’s agreement, explore the responsibilities they actually held, how they handled difficult decisions and the conditions in which they were most effective.

6. Make it possible for the hire to succeed

Before the person starts, communicate why the role exists and how it changes decision-making. Give them access to the relevant people, customer context, commitments, budgets and operating information. Make space for them to understand the business before asking for a definitive transformation plan.

Agree early evidence of progress suited to the mandate. That could include a shared view of risks and commitments, clear ownership across technology and product, or a prioritised investment proposal that the executive team can discuss. Avoid promising a release-rate improvement by a fixed date before the cause of the current constraint is understood.

For a business with an existing CTO or technical co-founder, resolve the relationship openly. If the issue is performance, capacity or a change in responsibilities, the appropriate business leaders must handle that directly. A second leader hired into an ambiguous remit can leave both people unable to act.

7. Decide whether to hire now

Proceed with the search when you can explain the enduring ownership gap, the mandate, the authority, the workload and how the business will support the appointment. Use that explanation to align the interview panel and compare candidates consistently.

Refine the role when the examples point mainly to engineering management, product ownership or a specific capability. Arrange temporary cover when operating decisions cannot wait for a permanent search. Investigate further when leaders disagree about what is missing and have not yet examined concrete examples.

The practical output is a one-page role mandate: business outcomes, recurring responsibilities, decision rights, relationships, availability and evidence of success. Once those are clear, the job description and selection process have something solid to follow.