Chief Technology Officer
Owns what gets built, what it is built on, and whether the team can keep shipping in a year.
Who to hire
The shape of person who does this job well — and whether you should be hiring it at all yet.
If software is the product, this is a co-founder and not a hire — a fractional CTO cannot carry a product company's technical risk. The fractional version is right for a non-software business that nevertheless depends on software: choosing the stack, hiring the first two engineers, auditing an agency's work, or taking over a codebase a contractor left behind.
Education
A computer science or engineering degree is the common path and not a requirement; the strongest CTOs in small companies are frequently self-taught with ten years of production systems behind them. What matters is whether they have operated what they built — someone who has never been paged at 3am will build something that pages you at 3am.
Experience
8+ years writing software professionally and at least two years leading others. Crucially: has built the kind of system you need. Real-time, data-heavy, regulated and consumer-scale are four different skills, and nobody has all four.
Vertical / domain experience
Needed where the domain dictates the architecture — payments, health records, trading, telecom. Otherwise prefer a generalist who learns fast; domain knowledge transfers more easily into engineering than engineering transfers into domain.
What it pays, roughly
$138,674 median, Canada — for Managers in engineering, architecture, science and information systems, the closest occupation Statistics Canada actually measures, measured from $130,125 to $149,323 over 127,400 people. That occupation is broader than this role, so read it as an anchor, not a salary band — and note that a startup usually pays below it in cash and above it in equity.
Credentials and certifications
What exists, who issues it, and whether it means anything for this seat. A credential is evidence of a floor, never of judgment — and in a few of these roles it is a legal requirement rather than a nice-to-have.
| Credential | Issued by | When it matters |
|---|---|---|
| AWS, Google Cloud and Azure professional certifications | Amazon Web Services (and equivalents) | Evidence of breadth on a specific platform. Treat as a tiebreaker; a portfolio of running systems says more. |
| CISSP — Certified Information Systems Security Professional | ISC2 | Matters if the CTO also owns security and you sell to enterprises that send security questionnaires. |
| P.Eng. — Professional Engineer | Provincial engineering regulators (Canada) | Required only where the work is engineering in the legal sense — not for software. Do not use the title loosely; it is protected. |
What this role does at each stage
The same title means three different jobs depending on how much money is in the bank. Read the stage you are at, then read the next one — that is what you are hiring toward.
Builds it. One person, no process, decisions made for speed and reversibility. The right call is usually the boring stack they already know.
Still writes code roughly half the time; hires two to four engineers; puts in the three things you cannot retrofit cheaply — version control discipline, a deploy pipeline and backups you have actually restored from.
Mostly stops writing code. Owns hiring, architecture, the security posture you now have to prove to customers, and the first real on-call rotation. This is where many technical founders need to choose between the title and the keyboard.
Can one person hold this and something else?
The whole point of the many-hats problem: which of these jobs merge safely into one person, and which merges quietly cost you money or control.
Merges well with
- Chief Information Officer
- Software Engineer (Technology)
- Director of Data (Technology)
CTO + CIO is one person in nearly every company under 50 people: the same judgment chooses what you build and what you buy. CTO who still ships as the senior engineer is normal to about ten engineers.
Keep separate from
Not a governance problem, a capacity one — a CTO carrying a named feature team's delivery will do neither job in the quarter you most need the architecture decisions.
Reading a candidate
What good looks like in an hour, and what should stop the process.
Good signals
- Chooses a boring stack and can say why
- Asks what the business constraint is before proposing an architecture
- Has deleted a system they built
Red flags
- Wants to rewrite everything in the first month
- Cannot explain a technical trade-off to a non-technical founder
- No production experience, only prototypes
The jobs under this seat
What this hat is actually responsible for once there are people doing it. Every one is a page of its own — and at seed most of them are the same two people, which is what the merge notes above are about.
Builds and runs the product. At senior and staff level, also decides how it is built and raises everyone else's output.
Owns the part the customer touches — and, at architect level, the structure that keeps a large interface maintainable.
Owns the numbers the company trusts: the pipelines, the definitions, the warehouse and whether two dashboards can…
Decides what gets built next and says no to the rest. Accountable for the outcome of the thing shipped, not for…
Owns how the product looks, behaves and holds together — and, in the systems version of the job, the components…
The whole departments: Technology and Product & design · every job in one list
What this role runs on
The software categories this seat lives in, each linked to the screen of who sells it — the incumbent, the challengers and what the lock-in is.