Fractional CPO Job Description: Scope and Template
November 20, 20266 min read
A fractional CPO job description should name the product decisions the person owns (strategy, roadmap, prioritization, pricing and packaging input, the product team's operating rhythm), the weekly hours, the meetings they run, and the outcomes expected in the first 90 days. Leave out day-to-day ticket writing and anything that needs a full-time presence.
One note on the acronym: CPO here means chief product officer. If you need a part-time chief people officer, see the fractional CHRO guide instead.
What a fractional chief product officer is actually responsible for
The role exists to answer one question well: what should the product team build next, and why. Everything in the job description should trace back to that. In most engagements the responsibilities fall into five groups.
- Product strategy. A written point of view on who the product is for, which problems it solves better than alternatives, and which segments it will not serve this year. Usually a short strategy memo, revisited each quarter.
- Roadmap and prioritization. A now, next, later roadmap tied to company goals, plus the rule the team uses to rank work. That rule should handle the hard cases: the large customer's custom request, the sales-driven feature, the tech debt nobody wants to fund.
- Discovery. A steady cadence of customer interviews, usage review and prototype tests so bets are checked before engineering time is spent on them.
- Product operations. The weekly product review, the spec or PRD format, release notes, the launch checklist with marketing and support, and the intake path for requests from sales and customer success.
- Team and craft. Hiring, coaching and reviewing product managers and often designers. In a small company that can mean coaching one PM and a founder who still writes specs at night.
The metrics the role watches are product metrics: activation rate, time to first value, feature adoption, retention by cohort, and expansion where pricing allows it. A JD that lists revenue targets with no product metric is describing a different job.
Scope by hours: what fits in one, two or three days a week
Hours decide what the role can own. Write the JD to the hours you can pay for, and cut responsibilities until it fits.
| Weekly time | Realistic scope | What does not fit |
|---|---|---|
| About one day (6 to 8 hours) | Strategy memo, quarterly roadmap review, weekly product review, coaching one PM or the founder, input on key hires | Running discovery personally, writing specs, managing designers |
| About two days (12 to 16 hours) | Everything above plus owning the roadmap, running the prioritization process, leading a discovery cadence, pricing and packaging input, hiring the first or second PM | Being in every sprint ceremony, owning launches end to end |
| About three days (20 to 24 hours) | Acting head of product: manages PMs and design, owns the product section of the board deck, partners weekly with engineering and go-to-market leaders | After-hours escalations, serving as the only product person on the team |
If the company has no product manager at all, say so in the JD. A fractional CPO can set direction for a team of zero PMs, but someone still has to write tickets and sit in standup, and that someone is usually a founder or an engineering lead. The fractional head of product guide covers when the more hands-on version of the role is the better fit.
Copyable fractional CPO job description template
Replace the bracketed text. Keep it to one page.
Title: Fractional Chief Product Officer (part-time, [X] hours per week)
Reports to: CEO
About the company: [One or two sentences: what you sell, who buys it, team size, funding or revenue stage.]
Why we are hiring this role now: [The specific trigger. Example: "Our roadmap is set deal by deal, and engineering has shipped three features in the last two quarters that few customers adopted."]
What you will own:
- Product strategy, written and updated quarterly, agreed with the CEO
- The roadmap and the prioritization rules behind it
- A weekly product review with engineering and design leads
- A discovery cadence of at least [N] customer conversations per month across the product team
- Coaching and performance input for [N] product managers and [N] designers
- The product section of the quarterly board update
- Input on pricing and packaging changes, with the CEO as final decision maker
What you will not own: sprint management, writing individual tickets, customer support escalations, engineering delivery dates.
First 90 days:
- Days 1 to 30: interview [N] customers and every team lead, review usage data, and deliver a written assessment of the product, the team and the roadmap.
- Days 31 to 60: publish the strategy memo and a now, next, later roadmap. Start the weekly product review.
- Days 61 to 90: stand up the request intake process, define two or three product metrics with targets, and recommend a hiring plan.
Working pattern: [Fixed days, e.g. Tuesday and Thursday], available in the team chat on those days, one in-person or video leadership meeting per week.
What we are looking for: has led product at a [B2B SaaS / marketplace / consumer / hardware] company through [stage]; has managed PMs; comfortable telling a founder no with evidence.
Engagement: monthly retainer, [3 or 6] month initial term, [30] days notice either side.
What to leave out of the job description
- "Own the backlog." Backlog grooming is a product manager's job. Listing it tells experienced candidates you want a senior title on a junior workload.
- "Be available to the team as needed." A fractional leader has other clients. State the days and the response time you expect.
- Delivery dates. Engineering owns when things ship. The CPO owns what and why.
- A list of tools. Nobody is a better product leader because they know your ticketing system.
- Equity-only compensation. It narrows your candidates to people who can afford to work for free.
How each side should read the finished JD
If you are the company, test the draft with one question: could a candidate tell from this page what decision they will make in week two? If the answer is no, the "why now" section is too vague. The steps in how to hire a fractional executive will help you turn the JD into an interview plan.
If you are the executive, read for decision rights. Look for who has final say on the roadmap when the CEO and the largest customer disagree, and whether engineering leadership reports alongside you or above you. Ask about both on the first call. Then turn the JD into a written scope, using the approach in scoping a fractional engagement, so the 90-day outcomes in the posting are the same ones in the contract.
For experienced executives
Get found and hired for fractional work.
- A profile companies can find
- A calendar they can book
- Paid to your bank, you keep 90%
Frequently asked questions
What should a fractional CPO job description include?+
Include the product decisions the person owns (strategy, roadmap, prioritization rules, product review), the weekly hours and working days, who they coach or manage, the first 90-day outcomes, and what the role does not cover. Add a specific reason you are hiring now so candidates can judge fit quickly.
How many hours a week does a fractional CPO work?+
It depends on scope. About one day a week covers strategy, roadmap review and coaching. About two days lets the person own the roadmap and run discovery. About three days works as an acting head of product who manages PMs and design. Write the job description to the hours you can fund.
What is the difference between a fractional CPO and a product manager?+
A fractional CPO decides what the product team should build and why, sets the prioritization rules, and coaches the team. A product manager writes specs, grooms the backlog and works in the sprint daily. If your job description lists backlog ownership, you are describing a product manager.
Can a company hire a fractional CPO with no product managers?+
Yes, but be clear about who does the hands-on work. A fractional CPO can set strategy and the roadmap for a team with no PMs, yet someone still has to write tickets and attend standup. Usually that is a founder or engineering lead until the first PM is hired.