The three different jobs that share the title CTO

The title covers at least three jobs that have almost nothing in common, and most bad CTO hires are a mismatch between which one the company needed and which one it interviewed for.

Nobody says this out loud during a search, because everyone assumes the word means what it means at their last company. It did not.

If you are trying to work out which one you need — and whether you need it full time — that is the question fractional cto services exists to answer before a salary is committed rather than after.

Job one: the builder

Writes code. Makes the architectural calls. Is measurably the strongest engineer in the room, and the company’s technical output would drop noticeably if they stopped.

This is the right CTO for a company of three to fifteen people where the product is the business and the main risk is that the thing does not get built well.

The failure mode is growth. A builder who is still the best engineer at forty staff has become a bottleneck, because every non-trivial decision routes through one person who is also trying to write code. Companies rarely notice this transition until delivery has already slowed.

Job two: the scaler

Does not write much code. Designs how decisions get made — who owns what, how work is reviewed, what “done” means, how incidents are handled, when to hire.

The measurable output is that engineering keeps working as headcount doubles. That is not a coding skill, and being excellent at job one predicts very little about being good at this.

The failure mode here is the opposite: a scaler hired into a company of six builds process for an organisation that does not exist yet, and everyone spends their time in ceremonies instead of shipping.

Job three: the representative

Talks to investors, auditors, enterprise buyers, and regulators. Signs off on security questionnaires. Explains the technical strategy to people who will never read code but whose approval decides whether money moves.

This is a real job with real value, and it is the one most likely to be quietly required and never stated. If your funding round or your biggest deal depends on someone credible answering technical questions, that is the job you are hiring for, whatever the description says.

Why the mismatch is so common

Because the requirement changes faster than the title does. A company hires a builder at eight people, and by thirty it needs a scaler. The person has not got worse. The job changed underneath them, and nobody redefined it.

The honest version of that conversation is uncomfortable and cheaper than the alternative, which is eighteen months of both sides feeling that something is wrong without being able to name it.

The question I would ask before starting a search

Not “what should our CTO do.” Ask: what breaks in the next twelve months if nobody does this job?

If the answer is “the product does not get built properly,” you need a builder. If it is “we cannot absorb the ten people we are about to hire,” you need a scaler. If it is “we will not pass the security review that gates our biggest contract,” you need a representative — and that one you may only need for a few days a month, which is why the fractional model exists at all.

Two of those three answers rarely justify a full-time executive salary at the stage most companies first feel the need. That is worth knowing before you post the role.

Why the title inflates

One reason these three jobs get confused is that the title is used as compensation. A company that cannot pay market rate offers seniority instead, and the person accepts a title describing a job the company does not yet have.

This is not cynical on either side. It is usually generous and short-sighted. The cost lands later, when the company grows into genuinely needing the seat and discovers it is occupied by someone hired for a different reason.

The cheapest fix is to separate the title conversation from the job conversation. Agree what the job is for the next eighteen months, then decide what to call it.

What this framing does not settle

It does not tell you whether the person you already have is in the wrong job. That requires knowing what they are actually spending their week on, and the gap between what a senior technical person does and what their calendar suggests they do is usually large. I can describe the shape of the roles; I cannot assess a specific individual from a job title.

It also does not cover the case where the answer is “all three, at once, at twelve people.” That case exists and it is genuinely hard. Usually it means sequencing — deciding which of the three you accept doing badly for a year.

Related reading: fractional executive covers the part-time model across roles and where it stops working, and how to become a CTO covers the same three jobs from the other side, which is useful if you are trying to assess whether a candidate has done the one you need.