The CPO Job Description: What to Write, Section by Section

Because the CPO role varies more between companies than almost any executive seat: what it owns depends on the founder, the stage and the org. A template averages those away, so it describes no company's actual gap, and the candidates it attracts are optimized for interviews, not for your situation.

The failure is measurable in searches: a vague specification stretches the 4 to 6 month search timeline, because the market cannot match what the company cannot describe, and it lands worse, because the offer gets made on chemistry instead of evidence. The template saves an afternoon of writing and spends it back with interest in the shortlist.

Run the function first, even briefly, and write down what it actually decides: which conflicts landed on the desk, which metrics the roadmap was argued against, where the strategy strained. Those notes are the mandate and the outcomes sections, already written, and they describe your company rather than the category.

This is the quiet advantage of defining the role through a working engagement before searching: the scorecard writes itself from decisions that actually happened. Companies that hire a fractional operator during the search commonly hand the search firm a JD built this way, and the difference shows in who applies.

Publish the range. The market figure is $260K to $400K in base and cash with equity additional, and a JD that states its band inside that range filters honestly in both directions: candidates outside it self-select away, and nobody's time is spent discovering a mismatch at offer stage.

The same transparency logic that works in service pricing works in hiring: a stated number is a commitment device. If the band cannot be stated because it has not been decided, the JD is being written too early, and that is information too.

The silences. Whether decision rights are named, whether the outcomes have numbers, whether the mandate survives contact with the founder's actual involvement. Operators who have held the seat before read a JD the way a buyer reads a contract: for what is missing, not what is promised.

Two additions that consistently signal seriousness: the reporting line stated plainly, including who product reported to before, and one honest sentence about the hard part of the job. "The roadmap has been sales-driven for two years and changing that is the job" attracts exactly the operator who wants that fight, and repels the ones who do not.

Whoever has evidence about the function, at the moment the role is actually defined. If nobody inside has run product recently, that is the sequencing signal: define the role through a working engagement first, or accept that the first draft is a hypothesis the search will test expensively. The JD is downstream of the definition.

In practice the writing takes an afternoon once the evidence exists and weeks of committee drafting when it does not. The four-section table above is the whole structure; everything else in a typical JD, the company boilerplate, the values list, the benefits, matters less to the candidates you actually want than one honestly named decision right.