I once reviewed a CTO job description that included "must have 15+ years of experience in microservices architecture." The startup was two years old with four engineers. They'd been searching for eight months.
The problem wasn't the market—it was the job description. They'd written a list of everything they wished for, not a role a great candidate would actually want.
After helping over 35 startups write CTO job descriptions that successfully closed candidates, I've learned that most job postings fail before the sourcing even begins. Here's how to write descriptions that attract instead of repel[^1].
Why Most CTO Descriptions Fail
Before we look at what works, let's understand what doesn't.
Laundry list requirements signal an unrealistic employer. When you list 25 required skills, you communicate that you don't know what you actually need. The best candidates—who know their worth—see this as a red flag.
Generic descriptions attract generic candidates. "Lead technology strategy" could describe a CTO at any of 10,000 companies. Specificity attracts people who fit your specific situation.
All responsibility, no opportunity makes the role sound like a burden. Yes, you're hiring someone to own hard problems. But they also want growth, impact, and interesting work. Describe both.
Founder-centric framing reads like "we need someone to execute our vision." The best CTOs want partnership, not prescription. If you've already decided every technical direction, you need a senior engineer, not a CTO.
Unrealistic experience requirements eliminate great candidates. Someone with exactly the experience you've listed is probably overqualified or non-existent. Someone with adjacent experience who learns fast might be perfect.
Understanding What You're Actually Hiring
The CTO role varies dramatically by company stage. Define yours clearly before writing the description.
| Stage | Primary CTO Function | Time Coding | Team Size |
|---|---|---|---|
| Pre-seed/Seed | Builder (writes code) | 60-80% | 0-3 |
| Series A | Player-coach | 30-50% | 3-10 |
| Series B | Engineering leader | 10-20% | 10-30 |
| Series C+ | Executive | 0-10% | 30+ |
At seed stage, you need a CTO who can build the product themselves. At Series C, you need someone who can scale a 100-person org. These are different people with different skills.
Also clarify the CTO vs. VP Engineering distinction:
| Dimension | CTO (External Focus) | VP Engineering (Internal Focus) |
|---|---|---|
| Primary focus | Technical strategy, architecture | Execution, delivery, team |
| Key stakeholders | CEO, customers, investors | CEO, product, engineers |
| Time horizon | 1-3 years | Quarters to 1 year |
| Hands-on coding | Depends on stage | Usually minimal |
Some startups need both roles. Some need only one. Be clear about which you're hiring.
The Job Description Framework
A strong CTO job description has five sections, each serving a specific purpose.
Section 1: The Hook (2-3 sentences)
This is what candidates read first. Make it count.
Bad hook: "We're looking for a CTO to lead our technology organization and drive technical strategy."
Good hook: "We're building the infrastructure that powers next-generation logistics companies—and we need a technical leader who can scale our platform from 100 to 10,000 customers while keeping our engineering team as sharp as they are today."
The good hook communicates: what you do, what the opportunity is, and what makes the role interesting.
Section 2: About the Company (3-4 sentences)
Don't bury the company description at the bottom—candidates need context to evaluate the role.
Include: what you do in plain language, stage and traction (funding, revenue, customers), why you'll win (not marketing speak, but actual differentiation), and team size.
Example: "Warehouse Dynamics automates inventory management for mid-market retailers. We've grown to $4M ARR with 80 customers, raised a $15M Series A from [notable investors], and compete by being 10x faster to implement than legacy solutions. We're 28 people total, with a 9-person engineering team."
Section 3: The Role (5-8 bullets)
Describe what they'll actually do, not what they'll be responsible for. Active verbs beat passive descriptions.
Good bullets:
- "Own the technical architecture that supports 10x customer growth"
- "Hire and develop the next 10 engineers while maintaining our high bar"
- "Partner with our CEO and VP Product on product strategy"
- "Make build vs. buy decisions on infrastructure investments"
Bad bullets:
- "Responsible for technology strategy"
- "Manage the engineering team"
- "Ensure system reliability"
The good bullets are specific and action-oriented. The bad bullets could describe any CTO anywhere.
Section 4: What We're Looking For (5-7 bullets)
Frame requirements as qualities, not checkboxes.
Instead of: "10+ years of software engineering experience" Write: "You've built and shipped products that real customers use—we care more about what you've accomplished than years on a resume"
Instead of: "Experience with microservices architecture" Write: "You've scaled systems from startup to significant load and know when complexity is worth it"
Instead of: "Management experience required" Write: "You've helped engineers grow their careers, whether through formal management or technical mentorship"
Requirements should describe the person, not a set of credentials.
Section 5: What We Offer (4-6 bullets)
Be specific. Every startup says "competitive compensation." Say what's actually true.
Instead of: "Competitive salary and equity" Write: "Base salary of $220K-280K depending on experience, plus 1-2% equity with four-year vesting"
Instead of: "Great team" Write: "You'll work alongside [specific notable people] who previously [specific accomplishments]"
Instead of: "Opportunity for growth" Write: "This role reports directly to the CEO and will evolve into a C-suite position as we scale"
Templates by Stage
Seed Stage CTO Template
CTO (Technical Cofounder Track)
We're building [one sentence about what you do]. We need a technical leader who
can architect the initial product, write substantial code, and eventually build
a team.
About [Company]:
[2-3 sentences: problem, traction, differentiation]
The Role:
- Build the core product architecture from the ground up
- Write production code daily—this is a hands-on role
- Make early technology choices that will scale
- Hire our first 2-3 engineers when the time is right
- Partner with founders on product decisions
You Might Be Great For This If:
- You've built a product from scratch before—ideally one that shipped to customers
- You're comfortable wearing every technical hat: frontend, backend, infrastructure
- You want to build something meaningful, not just manage people
- You're energized by ambiguity and ownership
The Offer:
- Base: $[X]-$[Y]
- Equity: [X-Y]% (co-founder level)
- Reports to: CEO (co-founder dynamic)
Series A CTO Template
Chief Technology Officer
[Company] is [one sentence description]. We've reached [traction metric] and
raised our Series A to [goal]. We need a CTO who can scale our technology and
team for the next stage of growth.
About [Company]:
[3-4 sentences: what you do, traction, team size, notable investors/customers]
The Role:
- Own technical architecture as we scale from [X] to [Y]
- Grow the engineering team from [X] to [Y] engineers
- Establish engineering practices that maintain quality at scale
- Represent technology in executive discussions and board meetings
- Code when needed—we expect hands-on contribution, not just oversight
You Might Be Great For This If:
- You've scaled an engineering team through rapid growth (ideally 5 → 25+)
- You're still technical enough to earn engineers' respect and review architecture
- You've built systems that handle meaningful load
- You can translate between business needs and technical solutions
- You're excited by building, not just managing
The Offer:
- Base: $[X]-$[Y]
- Equity: [X-Y]%
- Bonus: [structure if applicable]
- Reports to: CEO
Series B+ CTO Template
Chief Technology Officer
[Company] is [one sentence]. We've grown to [traction metrics] and are entering
our next phase of scale. We need a CTO who can build a world-class engineering
organization while driving technical strategy.
About [Company]:
[4-5 sentences: what you do, traction, funding, team size, differentiation]
The Role:
- Drive technical strategy aligned with company goals
- Scale the engineering organization from [X] to [Y]
- Develop engineering leadership: VPs, Directors, Staff engineers
- Own technology decisions in executive team and board discussions
- Represent [Company] externally: recruiting, conferences, customers
- Partner closely with [other C-suite roles] on company direction
You Might Be Great For This If:
- You've built and led engineering organizations of [X]+ people
- You've successfully hired and developed VP and Director-level leaders
- You can engage credibly with technical architecture while delegating implementation
- You've navigated the challenges of rapid scaling firsthand
- You communicate effectively with boards, customers, and engineers alike
The Offer:
- Base: $[X]-$[Y]
- Equity: [X-Y]%
- Bonus: [structure]
- Reports to: CEO
- Direct reports: [roles]
Common Mistakes and Fixes
| Mistake | Why It Hurts | Fix |
|---|---|---|
| "Rockstar" or "ninja" language | Signals immature culture | Use professional language |
| Listing 20+ requirements | Nobody qualifies, best candidates skip | Max 7-8 qualities |
| "Fast-paced environment" | Everyone says this | Describe your actual pace |
| Vague equity ("competitive") | Creates distrust | Give ranges |
| No salary range | Wastes everyone's time | Post the range |
| "Culture fit" without definition | Signals bias concerns | Describe actual values |
| Buzzword soup | "AI-powered disruptive synergies" | Plain language |
Final Check
Before posting your CTO job description, ask:
Would you apply to this role? If you were a candidate reading this, would it excite you?
Is it specific enough to screen? Does it help candidates self-select in or out?
Does it describe the real job? Not the ideal job, the actual one.
Could this describe 100 other companies? If yes, add specificity.
Would your best engineer recognize the company? Have current team members review it.
The startup that couldn't find a CTO for eight months rewrote their job description with me. We cut the requirements by half, added specific context about their challenge, and included real compensation numbers. They had three strong candidates within six weeks and closed their CTO the following month.
The words matter more than you think.
References
[^1]: SmithSpektrum CTO hiring data, 35+ successful placements, 2019-2026. [^2]: Textio, "Job Description Language and Candidate Response," 2024. [^3]: LinkedIn Talent Solutions, "What Candidates Want in Job Postings," 2025. [^4]: First Round Review, "Writing Job Descriptions That Win," 2023.
Writing a CTO job description? Contact SmithSpektrum for review and optimization.
Author: Irvan Smith, Founder & Managing Director at SmithSpektrum