C-Suite / CTPO / Job Description
CTPO job description
A template you can adapt — and the mistakes unique to the merged seat
Most CTPO job descriptions make one of two errors: they demand a unicorn equally world-class at product and engineering, or they're a CTO JD with a few product bullets bolted on. This template is built around what actually makes the merged seat work — including the org structure that lets one person carry both mandates.
Direct answer
A strong CTPO job description names both mandates (product strategy and technology/engineering), states the reporting line (the CEO), and writes the two VPs — engineering and product — into the structure. The clause that makes it real is the honest one: one person cannot operate both functions at depth, so the JD names a home discipline and a strong deputy for the other half. A JD demanding equal world-class depth in both is unfillable.
Executive Tech Jobs
High-value tech leadership roles, in your inbox
Join 2,000+ CTOs, VPs of Engineering, and Heads of Engineering getting new executive tech openings and salary intel every Monday.
Browse the full executive jobs board →How to use this
Adapt it, don't paste it
This template is deliberately opinionated. Cut what doesn't apply, but keep two things: the explicit CEO reporting line and the named deputies underneath. Those are what a serious candidate reads to decide whether the role is a real merged seat or a CTO job wearing a longer title. A CTPO JD that pretends one human will personally run product discovery and platform architecture at equal depth attracts people who will spend a year discovering they were hired to do two full-time jobs at once.
The template
Chief Technology & Product Officer — job description
Role summary
The Chief Technology & Product Officer (CTPO) is accountable for both what the company builds and how it is built — product strategy and roadmap, and technology, architecture, and engineering delivery — in a single seat. The CTPO makes the trade-off between product ambition and technical reality directly, owns the combined product and engineering organization, and reports to the CEO.
Reporting structure
- Reports to: CEO
- Direct reports: VP/Head of Engineering, Head of Product, plus design and (increasingly) data/AI leadership
- Peer relationships: CRO, CMO, CAIO or CIO where they exist
Core responsibilities
- Product strategy & roadmap — own discovery, prioritization, and the roadmap the rest of the org plans against.
- Technology & architecture — own technical strategy, architecture, platform choices, and the reliability the product depends on.
- Unified delivery — be the single point of accountability for shipping; the roadmap and the engineering plan are one plan, not two reconciled in a meeting.
- Org & deputies — build and lead the combined org, with a strong VP of Engineering and a strong Head of Product so neither half goes shallow.
- The trade-off call — make the explicit, accountable decision when product ambition and technical reality conflict; this is the reason the seat exists.
Required background
- Came up through engineering or product, and has deliberately operated across the line into the other
- Has hired and led senior leaders in their weaker half (proof they can staff the gap, not just claim it doesn't exist)
- Track record of shipping product at the company's stage — startup velocity, not just large-org process
Preferred
- Experience in your product category (SaaS, AI platform, marketplace, etc.)
- Has scaled an org through the stage you're about to enter — and ideally seen a merged seat split into two
- Comfort working alongside or absorbing a CAIO as AI moves into the core product
Compensation
Base typically $350K–$650K with a 30–50% bonus and equity that swings hard on stage — a seed-stage CTPO may take $200–400K base plus a large grant, while late-stage total comp runs past $1M. Anchor the package to the CTO compensation range plus a premium for the added product mandate.
What goes wrong
Five hiring mistakes unique to the CTPO
- Hiring it to save a salaryMerging the titles doesn't merge the work. You'll still need both VPs underneath, so the "one chief instead of two" math rarely holds. Hire for speed and alignment, not cost.
- Demanding a two-sided unicornA JD that requires world-class depth in both product and engineering is unfillable. Name the home discipline and the deputy for the other half instead.
- A CTO JD with product bullets bolted onIf the draft is 80% engineering and a token nod to roadmap, you're hiring a CTO. Decide honestly which seat you actually want.
- Reporting it anywhere but the CEORoute the CTPO through a COO or CIO and you delete the alignment benefit that justified merging the seat. The role only works with direct line to the business.
- No plan for the splitThe merged seat is stage-bound. A JD that never acknowledges when and how the role splits into a CTO and CPO sets up an overloaded executive and a messy reorg later.
Related
More on the CTPO
Frequently Asked Questions
What should a CTPO job description include?
Who should a CTPO report to?
What background should a CTPO have?
How is a CTPO JD different from a separate CTO and CPO JD?
Scoping a CTPO hire?
The newsletter covers org design from inside the C-suite — how to scope a merged tech-and-product seat so it has the deputies and the reporting line it needs to actually work.