You are writing a job description for a Chief Product Officer, and the working assumption behind the draft is that it will attract candidates. Let go of that assumption. The leaders you want are not reading job boards, and when they do see your posting, forwarded by a recruiter or a board member, they are not reading it the way an applicant does. They are reading it to decide whether you understand the job you are hiring for.
A CPO job description does two jobs, and attracting is neither. First, it culls: stated precisely, its requirements eliminate everyone operating below the level of the hire. Second, it unlocks understanding for the one right reader: why this role exists now, and what business objectives sit behind it. The attracting happens through direct outreach and the conversation that follows.
What a CPO Job Description Actually Does
Think about how the document gets used in a real executive search. Nobody applies. We approach leaders who are employed and performing, and somewhere after the first conversation they ask to see something in writing. What they need at that moment is not a responsibilities list. It is the case for the role: the state of the business, the problem the CEO cannot solve with the current team, and what changes if this hire works.
That is a search brief, and at CPO level the job description should be written as one. The posting version of the same document has a different function: it stands guard. A precise CPO job description makes the wrong applicants self-eliminate, which is the only useful thing a public posting can do at this level. Vague postings do the opposite. “Experience scaling” pulls in every director who once inherited a growing team.
Answer “Why Now” Before Anything Else
The first section a senior leader reads for is the why-now paragraph, because it tells them whether the role is real. Companies hire CPOs off the back of a specific business event: a second product that needs an owner, a PE thesis with a dated exit, an expansion decision the executive team keeps deferring. Name yours, with the numbers you can share.
One test separates this section from fluff. If your why-now paragraph could appear in another company’s posting, it is fluff, and “an exciting time to join a category-defining company” appears in thousands.
Before anyone drafts anything, run the diagnosis with your leadership team: is the gap in the product and its market, in how the company executes, or in the leadership layer itself? If most of your answers land in execution and leadership, you may need a VP of Product rather than a CPO, and our breakdown of that difference is worth reading before you write a word.
The business objectives follow from the diagnosis. Not “drive product excellence.” Objectives a board would recognize: take the platform into a second market by 2028, get the portfolio ready for exit, rebuild velocity in a product org that has been flat since 2023. A senior candidate reads objectives like these and can immediately map themselves onto the job or out of it. Both outcomes save you months.
State the Show-Stoppers, Not a Skills List
Every CPO posting we see carries the same skills list: strategic vision, hands-on execution, stakeholder management, “experience scaling.” None of it culls anyone, because everyone at director level and above can claim all of it.
A show-stopper requirement is different. It is the one or two experiences without which this hire fails, stated so precisely that no one can talk their way around it. If the company is PE-backed and the thesis requires a second exit by year five, the line is: “You have built a PE-backed business through to exit, and you know what year three of that arc feels like.” If the job is two products becoming a portfolio, the line is about having run a portfolio, not a product.
Writing show-stoppers forces the conversation your leadership team has been avoiding: which experience is actually mandatory. Most teams discover they have been carrying six “requirements” and only one show-stopper. The other five belong in the interview, not the document.
The strategy question belongs here too. Decide what the CPO owns versus influences before you write the document, and state it honestly. We see the same failure pattern across searches: CEOs rarely trust non-founders with strategic direction, then hire a CPO expecting them to own strategy while the CEO dictates it. A leader good enough to want will leave over that gap, and your next search inherits the story.
What Should a CPO Job Description Include?
Six sections, in this order:
- Why now. The business event behind the role, one paragraph, with numbers.
- Business objectives. Three or four board-level outcomes this hire exists to deliver.
- Scope and authority. What they own, what they influence, reporting lines, board exposure.
- Show-stopper requirements. The one or two precisely stated experiences that are mandatory. No skills list.
- Where we are. ARR, team size, funding reality, what is hard right now. If the product team is lean and staying lean, say it. The strong candidates have lived through downsized teams and AI mandates with no budget; naming your version tells them you know what job you are hiring for.
- Compensation and process. A real range ($260K to $450K base in 2026 depending on stage), the interview stages, the decision timeline.
Six sections, about a page. If one is hard to write, that is the section your leadership team has not agreed on yet, and the document is doing you a favor by exposing it.
Frequently Asked Questions
If the job description culls rather than attracts, what does the attracting?
Outreach does. At CPO level, the candidates worth hiring are approached directly, qualified in conversation, and then handed the document as confirmation of what they have already heard. This is the mechanic behind retained search, and it is why posting a CPO role and waiting is the slowest possible version of this hire.
Should the salary range be in a CPO job description?
Yes. Several jurisdictions require it, and at the executive level the range communicates scope: a $260K base and a $450K base describe two different jobs. The range is itself a culling tool.
How is a CPO job description different from a VP of Product one?
The VP document describes an organizational job: team, roadmap, delivery. The CPO document describes a business job: strategy ownership, portfolio decisions, board accountability. If your draft reads like team-and-roadmap, you are hiring a VP with the wrong title.
Should we require AI experience?
Only as a show-stopper, stated as evidence: “has restructured a product org’s workflow around AI tools” or “has shipped AI-driven product decisions.” A “familiarity with AI/ML” line culls no one. Every resume you receive in 2026 will claim it.
Writing a CPO job description and not sure the role underneath it is defined yet? Book a call with us. We build the search brief at the start of every retained search, and we will tell you if what you actually need is a VP.