Having held the Chief Product Officer job four times, I can report that the role has always been unstable — a different shape at every company, renegotiated with every CEO. But what is happening now is not the usual instability. The market is repricing the job itself. Parts of the role that justified the title for a decade are losing value fast, and four jobs are absorbing the value they lose.

The parts losing value first: roadmap stewardship and delivery choreography. When AI-assisted teams can ship in days what used to take quarters, being the executive who sequences the backlog and reports the dates is not leadership — it is administration, and administration is exactly what this technology automates. The CPOs who defined their value by owning the process of shipping are discovering that shipping is no longer the constraint.

Here is where the constraint moved.

Job 1: Portfolio allocator

AI turns product investment from deterministic scheduling into probabilistic allocation. Some fraction of your AI bets will not clear their quality bar regardless of effort, and the capability curve underneath you moves quarterly. Someone has to decide how much of the company's capacity rides on hardening the core, how much on adjacent automation, how much on frontier bets — and, harder, someone has to hold the kill discipline when a charismatic bet misses its criteria.

This is capital-allocator thinking applied to product capacity, and it cannot be delegated downward, because every team is structurally in love with its own bet. The AI-era CPO runs the portfolio review the way a good fund runs one: pre-committed criteria, explicit re-pricing, no sentimental positions. The scorecard question: can you name the last AI bet you killed on its criteria, on its date? If the answer is none, you are not allocating. You are accumulating.

Job 2: Quality owner

In deterministic software, quality was delegable — QA owned the test suite, engineering owned the bugs. Probabilistic products dissolve that arrangement. The central quality question of an AI feature — how good is good enough for this workflow, and which failures are disqualifying? — is not a testing question. It is a judgment about customers, brand, and risk appetite. It belongs to product, and at the level where it sets precedent, it belongs to the CPO.

Concretely, this means the CPO owns the eval culture: every AI behavior ships against a graded eval; the eval encodes product judgment about tolerable versus embarrassing versus disqualifying failures; and eval scores are reviewed in the same forum as revenue, not buried in an engineering dashboard. The companies that treat evals as an ML-team artifact ship quality by accident. The scorecard question: for your most visible AI feature, do you know its eval score today — and did you set the bar it has to clear?

The feature-factory CPO managed the process of shipping. The AI-era CPO manages the judgment of what's good, what's economic, and what's trustworthy. Process was delegable. Judgment is not.

Job 3: Margin steward

For twenty years, product leaders could ship value and let finance find the price, because marginal cost was approximately zero. AI ends the free ride: every feature now has a cost of goods that scales with usage, and product decisions — model choice, retry logic, context size, agent autonomy — are margin decisions. The CFO can see the AI bill. Only product can see why it is shaped the way it is and which product choices would bend it.

The AI-era CPO therefore carries unit economics as a first-class product metric: cost per completed task per feature, gross margin by packaging rung, cost trajectory as usage mix shifts toward heavier tasks. This job also makes the CPO the CFO's structural partner on pricing — not consulted after, but designing the packaging ladder as part of the product architecture. The scorecard question: can you state the fully loaded cost per completed task of your top three AI features, at the 90th-percentile account?

Job 4: Trust architect

Every AI feature spends customer trust before it earns any back. Customers are extending a provisional line of credit — with their data, their workflows, their tolerance for confident errors — and that credit line is finite, shared across your whole product, and refilled slowly. A single trust incident in one feature raises the adoption tax on every other.

Someone has to govern that shared resource: what data the models see and remember, how the product behaves at the edge of its competence, whether failure modes are designed with the same care as success paths, how correction and recourse work when the system is wrong. These decisions cross feature teams, which is exactly why they rise to the CPO. Trust is the retention moat of AI-era SaaS — capability gaps close in months, but a reputation for being safe to rely on compounds for years. The scorecard question: does your product have designed behavior at the edge of its competence, or does it improvise?

What this means for the people in the job

The uncomfortable summary: the CPO job is shifting from managing the production of software to holding four judgments — where to bet, what good means, what it may cost, and what trust requires. Each was always latent in the role. AI makes them the role.

For sitting CPOs, the audit is simple and bracing: look at last week's calendar and count the hours spent on the four jobs versus the hours spent choreographing delivery. For CEOs hiring product leaders, the interview changes the same way: ask candidates to walk a real bet they killed, a quality bar they set and defended, a margin problem they engineered away, and a trust decision that cost them a feature. The candidates with crisp answers to those four are the ones built for what the job is becoming — the rest are applying for a role that is being automated out from under them.