Back to Blog

Chief Product Officer Job Description Template 2026

HiringIT HiringLeadership

Last updated: November 9, 2026

By Mike Carter, Managing Director, KORE1

A chief product officer job description should list the products the seat owns and what each earns, the teams reporting in, who sets price, what can be shut down, and a base range with the equity described. A true chief earns $260,000 to $450,000 base in 2026. Most CPO postings we see read like a VP of product ad with a longer title, and the people you want to reach notice that on the first pass.

The question that ended one search we worked this year was ten words long. “Am I allowed to shut down the app you bought?”

Some background, with the usual caveat that this is two searches folded into one story and the details are changed. A software company in South Burlington, Vermont, about 260 people and a Series C behind it, sold practice-management software to veterinary clinics. It had three products. The core scheduling and billing app brought in about 82% of revenue. A payments add-on was growing fast. And a client-reminder app, acquired in 2023 for its customer list, lost money every quarter and ate a fifth of the engineering team’s time.

The posting said none of that. It said “own the product vision and roadmap,” “partner with engineering and go-to-market,” and “build a world-class product organization,” followed by nine more bullets in the same key. No pay range. The finalist we liked, a VP of product at a Boston health-tech company, read it twice and then asked her question on our first call. Nobody at the company knew the answer. The CEO thought the new chief would decide. The CFO thought the board had already decided to keep it. Pricing turned out to be set every January by the CEO and the CRO, and product marketing reported to the CMO, so the person being hired to own product as a business would have controlled neither the price nor the message.

She withdrew politely, and I don’t blame her.

Before going further, where I sit. I spent twenty years in sales and marketing before staffing, I’m the managing director here, and KORE1 gets paid when a company hires a chief we found through our chief product officer staffing practice. A posting good enough to fill itself costs us a fee. I’d still rather you had one. If you haven’t settled whether the seat is really a chief, a VP, or a head of product, read our guide to hiring a chief product officer first, and the bands by stage and metro are in our chief product officer salary guide. Hiring one rung down? The director of product job description template is built for that seat. This page is only about the CPO posting.

Product leader pointing at sketched product flows pinned to a studio wall while two team members look on

What a Chief Product Officer Is Hired to Own

A chief product officer is the executive who reports to the CEO and owns product as a business: which products the company builds, keeps, prices, and retires, and the product, design, and research teams that do the work. At larger companies the seat also carries a profit-and-loss line.

That last part has moved faster than most job descriptions have. Products That Count and Mighty Capital surveyed more than 1,500 product leaders for their 2026 CPO Insights Report and found that over half of chief product officers now hold P&L responsibility and one in three owns the budget for buying AI companies, per the report’s May 2026 release. Those are survey numbers from a community of product leaders, so they lean toward people who already have the bigger version of the job. Still. If your posting describes a roadmap owner, a candidate who runs a P&L today reads it as a step down, and you won’t hear from them at all.

So the posting has a narrower job than most people give it. It doesn’t need to sell the company. It needs to describe the business the chief would be running, in numbers, plainly enough that the right person can tell it apart from the eleven other CPO postings in their inbox that month.

List the Products, and What Each One Earns

Start with the portfolio. Every candidate at this level will ask what they’re inheriting, and the strong ones ask in a particular order: what makes money, what’s growing, what’s dying, and what’s been promised to a customer already.

What you haveWhat to put in the postingExample line
The core productShare of revenue, customer count or segment, growth rate“Practice management for 4,100 veterinary clinics, about 82% of revenue, growing 19% a year.”
Add-ons and second productsAttach rate, or revenue share“Payments add-on, attached to 38% of accounts, launched 2024.”
Anything acquiredWhen, why, and whether it’s integrated“Client-reminder app acquired in 2023, still on its own codebase and login.”
AI features in production or promisedWhat ships today, and what sales has already shown customers“AI visit summaries in beta with 60 clinics, on the sales deck since March.”
Commitments already madeContracted features or dates the chief inherits“Two enterprise contracts include a multi-location reporting module due Q3.”

Exact numbers are optional. Bands work fine, and a private company can say “most of revenue” instead of 82% if the board is nervous. What isn’t optional is being honest about which line pays the bills, because that tells a candidate where the job really is.

Then answer the reminder-app question before anyone asks it. Can the new chief retire a product? All of them, some of them, or only with board approval? There’s no wrong answer. Plenty of good CPOs will take a seat where the board keeps the last word on shutting down an acquisition, since somebody paid real money for it. They won’t take a seat where nobody has thought about it, because that’s the argument they’ll spend their first year having.

Which Teams Report to the CPO

Product management reports to the chief at nearly every company we’ve worked with. Past that, it varies a lot more than people expect, and the variation is where candidates slow down and reread.

TeamReports to the CPO ifLives somewhere else if
Design and UX researchThe product is the main thing customers touchDesign is a shared brand and marketing team
Product operationsThere are four or more product teams to coordinateA COO runs a central operations or PMO group
Product analyticsUsage data drives the roadmap and pricingA chief data officer owns all analysts
Product marketingLaunches and positioning are treated as part of the productThe CMO owns all messaging. This is the most common split.
Technical writing and docsDevelopers are the customerSupport owns the help center
EngineeringThe title is chief product and technology officerThere’s a CTO, which is the normal case

Product marketing is the row that starts fights. In my old life I ran marketing teams, and I’ll admit I would have fought to keep it. But a chief who answers for whether a product sells, without any say over how it’s positioned, has been given the outcome and none of the levers. If the CMO keeps it, fine, say so and say how launches get decided. “Product marketing reports to the CMO, with launch positioning approved jointly.” That’s a sentence a candidate can work with.

Add the headcount too, by team. “Fourteen product managers, six designers, two researchers” tells a candidate more than “a growing team of talented product professionals” ever could.

Who Sets the Price

This is the line I’d add first if you only add one. At most of the companies we work with, pricing has been decided by the founder, or by the CEO and the head of sales in a room each January, for years. Hiring a chief product officer is often the moment that changes. Often, not always. The posting should say which.

Pricing has more parts than people think, and they don’t all have to move together. List price. Packaging, meaning which features sit in which tier. Discount authority, which nearly always stays with the CRO and should. And now usage pricing on AI features, where every customer action costs the company inference money and somebody has to decide whether that cost gets passed through, bundled, or capped. That last one has turned into a real fight at a lot of software companies over the past eighteen months, mostly between product and finance, and a candidate who has been through it will ask who wins.

Write the split down. In South Burlington it came out as packaging and list price to the CPO, yearly changes signed off by the CEO, discounts left with the CRO.

Two executives moving blank cards between three stacks on a table, the way packaging tiers get argued over in a pricing review

Equity Is Most of the Pay, and Vermont Only Asks About Salary

The bands are in our salary guide, so briefly. A true chief product officer earns $260,000 to $450,000 base in 2026, and total compensation runs from $500,000 to past $1.2 million once equity and bonus are counted at growth-stage and public companies. For comparison, the Bureau of Labor Statistics put the median wage for chief executives across all industries at $213,990 in May 2025. A real CPO’s base clears the median chief executive’s whole wage, and the equity comes on top.

Which creates a strange problem in the posting. The part of the package candidates care most about is the part the pay-range laws mostly don’t ask for.

Vermont is a clean example, and it’s newer than most. Act 155, which took effect July 1, 2025, requires employers with five or more employees to include “the compensation or range of compensation” in any advertisement of a Vermont job opening. The statute defines that range as the minimum and maximum annual salary or hourly wage the employer expects in good faith to pay when it writes the ad. Salary. Not equity, not bonus. A few details matter more for a chief seat than they would for most jobs:

  • It covers remote positions that will predominantly work for an office or location in Vermont, so a fully remote CPO reporting into a Burlington headquarters is in.
  • Positions open only to internal candidates count, and so do promotions. Moving your VP of product up still means a range on the internal posting.
  • An “advertisement” is any written notice of a specific opening made available to potential applicants. Verbal outreach is excluded. The confidential position specification a search firm emails to candidates is written, though, and I’d treat it as covered. Your counsel may read it differently; ours tells clients to put the range on it.
  • The Attorney General or a state’s attorney enforces it, and refusing to interview or hire someone for asserting their rights under it is a separate violation.

So print the base range, which you have to do in Vermont and a growing list of other places anyway. Then describe the equity even though the law doesn’t make you. Not the exact grant, which belongs in the offer. The shape of it. Stock options or restricted stock units. Roughly what percentage band, or say “competitive equity at a Series C valuation” if the board won’t let you print a number. Standard four-year vesting or something else. Whether there’s acceleration on a change of control, since a chief joining a company that might sell in two years will ask about that before anything else. A candidate weighing your posting against a public-company offer with $300,000 a year in stock needs that shape to decide whether to reply at all.

Bonus goes in as a percentage of base with what it’s measured on. Our salary benchmark assistant gives a first read on a base figure for your city in a couple of minutes.

Chief Product Officer Job Description Template

Replace everything in brackets. Notes in parentheses are for whoever drafts it and come out before it posts. Cut sections that don’t apply instead of padding them.

Title

[Chief Product Officer] (Use chief product and technology officer only if engineering reports to this seat. If the scope is one product line and a team of PMs, it’s a VP of product posting, and the pay should match.)

The Company and the Product Today

  • [What you sell] to [which customers], [N] customers, about $[band] in annual revenue
  • [Funding stage, investor, or public listing], [N] employees
  • [What changes over the next two years, for example a move upmarket, an acquisition to integrate, or a new pricing model]

Products You’ll Own

  • [Core product], about [N]% of revenue, growing [N]% a year
  • [Second product or add-on], [attach rate or revenue share]
  • [Acquired product], acquired [year], [integrated / separate]
  • [AI features in production or in beta, and what has been shown to customers]
  • [Contracted commitments with dates, if any]

Who Reports to You

  • Product management, [N] people across [N] teams
  • [Design and UX research, N people]
  • [Product operations / product analytics / technical writing] (Only what’s true on day one.)
  • You report to [the CEO] and attend board meetings [quarterly / as invited].

What Sits Elsewhere

[Engineering reports to the CTO. Product marketing reports to the CMO, with launch positioning approved jointly. Discounting stays with the CRO.] (Write this even if it feels awkward. Every finalist asks.)

Calls That Are Yours

  • The roadmap across all products, with [the top N bets reviewed by the CEO / no carve-outs]
  • [Packaging and list price, with annual changes approved by the CEO]
  • Retiring or merging products, [on your own / with board approval for anything acquired]
  • Hiring and removing product and design leaders
  • [Build-or-buy recommendations on AI capabilities, with acquisitions approved by the board]

The First Twelve Months

  • [A business result, such as payments attach rising from 38% to 50%]
  • [A portfolio result, such as a decision on the acquired product, made and carried out]
  • [A pricing result, such as a new packaging structure live for new customers]
  • A product leadership team in place that you hired or chose to keep

Background We’re Looking For

  • Led product at a business doing $[low] to $[high] a year, with more than one product line
  • Made pricing or packaging decisions and lived with the results
  • Retired or consolidated at least one product
  • Presented product strategy to a board or an investment committee
  • [Domain experience, only where it truly shortens ramp time, such as payments, healthcare data, or developer tools]

Helpful, Not Required

  • Shipped AI features that customers pay for, not just announced
  • Integrated an acquired product
  • [Public company / private equity hold] experience, if that’s your ownership

Pay, Equity, and Location

Base salary $[low] to $[high]. Annual bonus target [N]% of base, measured on [the results above]. [Stock options / RSUs], [percentage band or “competitive grant at our current valuation”], vesting over [four years with a one-year cliff], [with / without] acceleration on a change of control. Based in [city], [remote / hybrid N days a week], with travel about [N]% of the time.

Executive reading a printed chief product officer job posting by a window overlooking a small New England city and a lake in autumn

Questions We Get on CPO Drafts

Chief product officer, or chief product and technology officer?

Chief product officer, unless engineering will actually report to this person. The combined title tells every engineering leader reading it that there’s no CTO coming.

The CPTO setup works at companies under a few hundred people where one leader can still hold both, and it shows up a lot after a CTO departure. If that’s why you’re considering it, say so in the posting, and expect fewer applicants from the product side and more from engineering.

We’re promoting our VP of product. Do we still need a posting?

Usually yes, and in Vermont an internal posting needs a pay range too, because positions people can be promoted into count as job openings under the statute.

Even where no law requires it, writing the full description is worth the afternoon. It forces the same decisions about pricing and the portfolio that an outside hire would ask about, and it gives your VP a written answer to “what changes when I get the title,” which is a fair question.

How much equity detail belongs in a public posting?

The type, a rough band, the vesting schedule, and whether there’s acceleration. Save the share count and strike price for the offer.

Does Vermont’s law cover a remote CPO?

It covers a remote CPO who will mostly work for an office in Vermont, and a chief physically working from Vermont. A role based outside Vermont and working for offices outside it is excluded.

Where it gets murky is a company with offices in several states and no clear home base for the role. We tell clients to print the range on every version of the posting and stop worrying about which office the seat technically belongs to.

Is P&L ownership a fair requirement for a first CPO?

Only if your seat carries a P&L. Requiring one for a role that doesn’t own one screens out good product leaders and attracts general managers who’ll be bored by month six.

A better line for most first-time CPO seats is “has made pricing or portfolio decisions and been measured on revenue.” That’s the experience that transfers. A formal P&L at a company four times your size might not.

Should the requirements ask for AI product experience?

Put it under helpful, with a specific test. “Shipped AI features customers pay for” separates real experience from a résumé line about exploring generative AI.

Most product leaders have added an AI feature by now. Far fewer have priced one, watched the inference bill, and decided whether to keep it. If that’s your situation, the posting should say so, and it’ll draw the people who have done it.

One Read Before It Posts

Give the draft to your best product director and ask whether they’d know, from the posting alone, what the new chief could decide on day one. They’ll find the missing pricing line or the acquired product nobody mentioned faster than anyone in the C-suite will. If you’re writing the neighboring seats too, our CTO job description template covers the engineering side of that border and the chief revenue officer job description template covers the seat that usually keeps discounting. If the role needs filling before a permanent search can finish, a fractional CPO can hold it two or three days a week. When applications start coming in, the loop that follows is in our chief product officer interview questions.

KORE1 has run technology and product searches since 2005 across 30+ U.S. metros, our recruiters average 15+ years in the work, and 92% of our placements are still in the seat a year later. Our technology roles average 17 days to fill. A chief product officer search takes much longer than that, usually two to four months, and it’s almost always a direct-hire search. If you’d like a second read on your draft, send it to our executive search team. We’ll tell you which line a finalist would ask about first.