Fractional CTO, adviser or engineer: which role do you need?

A delayed release can lead a founder to start looking for a CTO. But the immediate gap may be an engineer who can implement a decision the team has already made. Hiring becomes easier when those needs are separated.

List the work that is not getting done and the decisions that keep being postponed. Then identify who could own them internally. That is a better starting point for choosing a role than treating a funding round or headcount as a hiring rule.

Four possible roles

A title does not settle the responsibilities. A CTO may write code, and a senior engineer may contribute architecture judgment. Check how much time remains for each function and who will be accountable for it.

A delivery gap calls for delivery capacity

When the objective and architecture are clear, a defined implementation engagement may be enough. One example is connecting a model to an existing application and testing the agreed failure cases. Acceptance can focus on the behavior delivered.

Asking that person to direct the whole product while implementing it introduces another responsibility. Scope it explicitly and decide who will continue handling daily questions.

An LLM integration or a focused AI technical audit can address a specific need without creating an ongoing leadership role.

Advice needs an internal decision owner

An adviser fits when someone inside the business has authority but wants a second technical view before committing resources. The work might examine a vendor proposal, compare architectures or help define a hiring decision.

Ask for the reasoning behind the recommendation and a list of missing information. Agree whether the adviser will revisit it when new evidence appears. Someone must still own implementation and follow-up.

Fractional leadership needs an operating mandate

Part-time leadership becomes useful when decisions recur and nobody is coordinating them. It needs access to the team, agreed authority and a counterpart for commercial decisions.

Ask what happens between scheduled reviews. Who responds to an incident? Who unblocks a release? What can wait? If every decision depends on someone who is only available at specific times, the arrangement needs to change.

Daily management needs may justify a full-time role. Assess the coordination load and actual responsibilities rather than assuming a particular team size determines the answer.

Questions for a candidate

Use situations your business recognizes, while avoiding requests for a complete unpaid solution:

• A commercial deadline depends on technical work that has not been investigated. What information would they need, and who should revisit the date?
• The team wants to replace a vendor. How would they compare staying with switching, including future maintenance work?
• The next hire is expected to solve a problem the team cannot yet describe. How would they help define the role before interviews begin?

Listen for the responsibilities the person needs and the participation they expect from the team. If answering requires code review or investigation, agree that analysis as paid work before it starts.

Set the first commitment

Compare proposals covering the same responsibility. A one-off review and recurring leadership have different outputs and terms. Describing both as CTO hours hides that distinction.

You can start with one bounded decision and agree what would justify continuing. If fractional support is already the preferred route, the remote CTO engagement guide explains how to define the initial work and handover.

At Pharosyne I help with software and AI architecture and technical leadership. Describe the decisions that currently lack an owner, including who is covering them today. That context helps distinguish advice, implementation and recurring responsibility.