CTO job description: a template by company stage

Do I need a CTO?

Before writing the job description, check you need the role. A full-time CTO makes sense when technology is central to your product, there’s a team to lead (or soon will be), and there are ongoing strategic technical decisions. You may not need one yet if:

• You have one or two engineers and the main need is building, not leading. A strong senior engineer may be the better first hire.
• Your product is mostly built by an agency and what you need is someone to judge the work. A part-time technical advisor fits better.
• You can’t describe what the CTO would do in their first six months. Hiring before you can is how companies end up with the wrong person.

If you need senior technical leadership now but the role isn’t clear yet, a fractional CTO can bridge the gap and help you write a sharper spec. I compare both options in fractional CTO vs full-time CTO.

How the CTO role changes by stage

• Pre-seed to seed (roughly 0–5 engineers): the CTO is the lead builder. Writes most of the code, chooses the stack, ships the first version, and hires the first engineers. Often a cofounder.
• Seed to Series A (roughly 5–20 engineers): still hands-on, but now hiring, running delivery, setting up processes like code review and on-call, and representing technology to investors.
• Series A to B (roughly 20–60 engineers): mostly leadership. Builds a management layer, owns architecture at a system level, sets the technical strategy, works on security and compliance. Often hires a VP of Engineering.
• Growth stage and beyond: strategic. Technology vision, major platform bets, M&A and due diligence, the board. Delivery is run by VPs and directors.

CTO vs VP of Engineering

In companies large enough to have both, the split is usually this: the CTO owns what and why technically, the VP of Engineering owns how and when.

The CTO focuses on technical strategy, architecture, platform bets, security posture, and external representation to customers, investors and acquirers. The VP of Engineering focuses on the engineering organization: hiring, people management, delivery process, team structure and execution against the roadmap.

A VP Engineering job description should therefore emphasize managing managers, delivery predictability, hiring at scale and engineering culture. A CTO description should emphasize technical direction and judgement. In a small company, one person does both; say so in the job description rather than pretending the split exists.

CTO job description template

Edit every line for your company. Delete the responsibilities that don’t apply at your stage; leaving them in signals you don’t know what you need.

1. About us: what the company does, for whom, stage, funding, team size, and one honest sentence about the current technical state (“our product works but was built fast and needs a stronger foundation”).
2. Why this role exists now: the specific reason you’re hiring. A founder stepping back from technology, a team that’s outgrown its structure, an upcoming scale challenge.
3. What you’ll own in the first 12 months: three to five concrete outcomes. For example: “Ship the enterprise tier with SSO and audit logging,” “Grow the team from 6 to 15 engineers,” “Reduce deploy time from days to hours.”
4. Responsibilities: technical strategy and roadmap; architecture and major technical decisions; building and leading the engineering team; delivery and quality; security, reliability and compliance; representing technology to the board, investors and customers.
5. Hands-on expectations: state the real split, for example “about 40% coding in the first year, decreasing as the team grows.”
6. Who you’ll work with: CEO, product lead, the current engineers, any agencies. Who reports to the CTO.
7. What we’re looking for: experience at a similar stage and scale; a track record of shipping and hiring; the technical depth your product needs; clear communication with non-technical people.
8. Nice to have: domain experience (payments, healthcare, data), experience through a fundraise or acquisition, relevant stack experience.
9. What we offer: salary range, equity range, location and remote policy, benefits. Including ranges saves everyone time.
10. Hiring process: the stages, who’s involved, and the expected timeline.

How to hire a CTO

1. Define the stage and outcomes first, using the template above. Get your cofounders and board to agree on them.
2. Get technical help for the assessment. A non-technical founder can judge leadership and fit but not technical depth. Bring in a trusted technical advisor, an investor’s technical partner, or a fractional CTO to run that part.
3. Source through your network first. Warm introductions from other founders and investors outperform job boards for executive roles. Use a recruiter if you have the budget and the network runs dry.
4. Interview on real problems. Walk candidates through your actual architecture, roadmap and team. Ask what they’d do in their first 90 days. Good candidates will ask hard questions back.
5. Check references properly, including people who reported to them. Ask about how they handled a failure.
6. Consider a paid trial project for the final candidate: a short, bounded piece of work like reviewing your architecture. It tests the working relationship on both sides.
7. Plan the onboarding, including handover from whoever is doing the job now.

Expect the whole process to take three to six months. During that time, technical decisions still need making. A temporary leader, such as an interim CTO, can cover the gap and help run the search.

Common mistakes in CTO hiring

• Hiring for pedigree, not stage. A CTO from a 2,000-person company may struggle without a team to delegate to.
• Wanting a unicorn. Senior architect, people manager, product visionary and full-time coder is four jobs. Pick the two that matter most right now.
• Skipping the equity conversation. Early-stage CTOs expect meaningful equity; be clear about it early.
• Not defining success. If you can’t say what a good first year looks like, neither of you will know if it’s working.
• Hiring a friend because they’re technical. Sometimes it works. Assess them with the same rigor you’d apply to a stranger.

For non-technical founders

Hiring your first technical leader without a technical background is one of the hardest things a founder does. You can’t easily tell a strong candidate from a confident one. Get an experienced technical person on your side for the process. My technical cofounder alternatives page covers how I help founders in exactly this position, including running technical interviews and handing over to the person you hire.

Related

• Fractional CTO vs full-time CTO: how to decide
• Interim CTO for the months between CTOs
• Fractional CTO services for growth-stage SaaS
• Building without a technical cofounder
• What does a fractional CTO cost? Pricing models explained