What This Template Covers
The startup CTO job description template covers six areas that together define the role clearly enough to attract the right candidates and filter out the wrong ones. The role context section establishes what stage the company is at, what has been built so far, and what the CTO will be walking into. This section is often omitted but it is what candidates actually read to decide whether to apply. A detailed, honest description of the current technical state (even if that state is "we have a prototype and need to rebuild properly") signals transparency and helps candidates self-select. The responsibilities section covers the full scope of the startup CTO role, which is fundamentally different from a corporate VP Engineering role. At a startup, the CTO is usually still writing code while also making architecture decisions, building the engineering team, managing external development partners or agencies, and representing technical decisions to investors and the board. The technical skills section covers the baseline technical competencies for a CTO building AI-powered products in 2025. This includes LLM integration experience, cloud infrastructure, security fundamentals, and the specific stack the company uses or plans to use. The leadership expectations section describes what kind of leader the company needs at its current stage. A pre-product CTO needs different skills from a post-PMF CTO who is scaling the engineering team. The equity and compensation section covers typical market expectations for startup CTO packages in the UK market, including salary ranges, equity percentage, and vesting structures. The interview process section outlines a structured hiring process that gives you confidence in the hire before making an offer.
How to Use This Template Step by Step
Step one: write an honest role context section. Describe the company in two sentences. Then describe the current technical state: is there existing code, and if so, what stack and what quality? Is there an existing engineering team, or is this the first engineering hire? What is the immediate first-90-days priority: build the MVP, scale the existing product, rebuild a prototype, or build the engineering team? Candidates who read this section will either be excited by the challenge or self-select out, both of which are good outcomes. Step two: define the responsibilities precisely for your company's stage. For a pre-MVP company, the responsibilities are: design the technical architecture, make the build-versus-buy decisions, either build the MVP alongside an agency or lead the build directly, establish engineering standards, and hire the first two to three engineers. For a post-launch company, the responsibilities shift toward: scaling the architecture, building the engineering team, improving development processes, and managing the technology roadmap in partnership with the product function. Step three: list the technical requirements honestly. Do not list everything. List the things that are actually non-negotiable for your product. If you are building an AI SaaS product, LLM integration experience is non-negotiable. If you are building in Next.js and TypeScript, familiarity with that stack is important. If you need the CTO to manage AWS infrastructure, AWS experience is relevant. Listing 30 technical requirements signals that you do not know what you actually need. Step four: describe the leadership style you are looking for. The most common hiring mistake for startup CTOs is hiring someone who is excellent at corporate engineering leadership (process, governance, managing large teams) for a role that actually requires someone who is excellent at early-stage startup execution (moving fast, making decisions with incomplete information, writing code while building a team). Be explicit about which you need. Step five: set compensation expectations. Research the UK market. For a founding or early CTO at a seed-stage UK startup, a typical package is GBP 80,000 to 120,000 base salary plus 1 to 4 percent equity on a four-year vest with a one-year cliff. At Series A, base typically increases to GBP 120,000 to 160,000 with lower equity (0.5 to 1.5 percent). EMI options are the standard equity vehicle for UK startups. Be transparent about the equity percentage in the job description. Candidates who care about equity will ask anyway, and transparency signals confidence. Step six: design the interview process. The process should include: an initial screening call (30 minutes, culture and context fit), a technical conversation (60 minutes, discussing a previous technical decision the candidate made and its outcomes), a take-home exercise or live technical problem (testing specific skills relevant to your stack), a team fit conversation with any existing team members, and a reference check with a previous report or technical peer.
Section-by-Section Walkthrough
The role context section should start with the company mission and the current stage. Include: how long the company has been operating, what revenue or traction has been achieved, the funding status, the size of the team, and what the technical product looks like today. This is not a marketing pitch. It is an honest description of the situation. Experienced CTO candidates have seen many job descriptions. The ones that describe a specific, honest situation stand out from the generic descriptions that all sound the same. The responsibilities section should be structured around the first three months, three to twelve months, and twelve months-plus timeframes. This shows candidates that you have thought carefully about the role's evolution and prevents the common mismatch where a candidate expects to be building a large engineering team immediately while the founder expects them to be writing code for the first year. The technical skills section should distinguish between required skills (genuinely non-negotiable) and preferred skills (useful but can be learned). A candidate who has built AI products on a slightly different stack but has the underlying LLM engineering competency is a better hire than someone who matches your stack exactly but has no AI experience. Be explicit about which is which. The leadership expectations section should address two specific scenarios that are common at startups. First: the CTO will manage a relationship with an external development agency or contractors in the early phase. If SpeedMVPs or a similar agency is building the MVP, the CTO needs to be able to review the code, manage the handover, and take ownership of the codebase. Second: the CTO will need to represent technical decisions to non-technical founders, investors, and board members. Communication skills and the ability to translate technical concepts are important leadership competencies for a startup CTO. The equity section should address UK-specific considerations: the Enterprise Management Incentive (EMI) scheme is the standard equity vehicle for UK startups because it offers significant tax advantages for employees and is straightforward to administer. Non-EMI options or growth shares are alternatives but have different tax treatment. Any equity description in the job description should note that the actual option terms are subject to a formal option agreement.
Common Mistakes This Template Prevents
The most common startup CTO job description mistake is writing a description that could apply to any engineering leadership role at any company. Generic descriptions attract generic candidates. This template's role context section forces specificity about the company stage, the current technical state, and the immediate priorities. The second mistake is hiring for a role that is one or two stages ahead of the company's actual needs. A Series B engineering leader at a pre-seed company will be frustrated by the lack of resources and process, while the company will be frustrated by the focus on governance and team building when what it needs is fast execution. Match the hire to the stage. The third mistake is omitting compensation and equity expectations from the job description. The CTO talent market is competitive. Candidates are weighing multiple opportunities simultaneously. A job description without compensation information forces an extra step before candidates know whether the opportunity is financially viable for them. The fourth mistake is designing an interview process that tests the wrong things. Technical interviews that focus on algorithm puzzles test a different skill set from what a startup CTO actually does. The interview process should test: technical decision-making (how they chose between architectural options in the past), communication (can they explain a complex technical decision clearly), and culture fit (do they share the founder's operating style and priorities).
Customisation Tips for Different Project Types
For AI-first startups where the CTO will need to lead AI product development, add an AI-specific technical requirements section. Required: experience integrating LLMs into production products, understanding of RAG architecture, familiarity with prompt engineering, awareness of AI evaluation approaches. Preferred: experience fine-tuning models, experience with AI agent frameworks, knowledge of the EU AI Act and its implications for product design. For regulated sector startups (fintech, healthtech, legaltech), add a compliance awareness requirement. The CTO at a regulated startup needs to understand the regulatory environment well enough to design compliant systems from the start. For fintech, this means familiarity with FCA expectations for system design and data governance. For healthtech, it means understanding NHS Digital data standards and potentially MHRA requirements. For legaltech, it means understanding professional privilege and data handling obligations. For startups that have or plan to have a remote-first engineering team, add specific remote leadership requirements. Remote engineering leadership requires different skills from in-person leadership: asynchronous communication practices, documentation habits, deliberate team-building across timezones, and tooling for remote collaboration. For startups that are planning to raise institutional funding in the next 12 months, note that the CTO may be expected to present to investors and participate in due diligence processes. This includes preparing technical due diligence materials, answering questions about the architecture and the technical team, and potentially meeting with technical advisors engaged by lead investors.