A product leader told me his CEO had mandated AI features by end of next quarter. Two weeks later, he opened senior product manager roles using JDs from years ago. Same comp, same criteria, same hiring panel. The candidates were elite. The version of the job they were being hired into no longer exists. AI absorbed the work the role was built around. The work that justifies the headcount is shrinking faster than JDs are getting rewritten. Full comp for steadily shrinking output, and a team that isn't structured to deliver on the board's mandate. The companies I see pulling away are freezing the legacy profile and hiring for shapes that didn't exist two years ago. The Product Operator profile is what's emerging.
Scoped before AI absorbed the work.
(Product Operator Profile)
Specialized in the work AI makes more valuable.
Same role title. Different shape. The companies that recognize this hire for the new shape. The rest hire for last year's job.
Four common patterns show up when the legacy profile keeps getting hired even as the work it describes gets absorbed. None are about bad faith. Most are about the org's clock running slower than the work's clock. Not every team shows all four, but most show some.
JD inertia. Last year's job description tends to get copy-pasted into next year's req. The question of whether the work the JD describes still exists doesn't always get asked. The recruiter posts. Candidates apply against a role that's often already partly absorbed.
Comp bands lag the work. Compensation surveys often trail the operating reality. The band that anchors the offer can be benchmarked against work AI is now doing. The hire walks in at full comp for a smaller job, and the next promotion conversation has less room to grow.
Hiring panels calibrated to legacy criteria. Interview panels were often trained to evaluate roadmap ownership, spec writing, and engineering partnership. None of those tend to be the binding constraint anymore. The panel can end up selecting for the shape the org used to need rather than the shape it actually needs.
Strategic surface tends to shrink faster than JDs get rewritten. The work the legacy profile was scoped to do tends to get absorbed quarter by quarter. The redefinition cadence inside HR is usually annual. The gap widens. By the time a JD is rewritten, the next layer of work is often already absorbed.
The work that hasn't been absorbed isn't a list of tasks. It's three dimensions of judgment. Each one demands a calibrated answer per product, per quarter, per shift in the AI surface.
The Product Operator owns the architecture of AI inside the product. Which workflows are AI-led, which are human-led, which are AI-assisted, where the handoffs sit. Designing this is the new strategic surface.
AI quality is bounded by the context it has. Curating what the AI knows about the business, the customer, the competitive position is a product responsibility now, not a data team responsibility. The judgment about what context to feed is the new specification.
The hardest call in the new profile is which work belongs to the AI and which belongs to humans. Wrong on either side compresses customer outcome. The Product Operator owns this call deliberately, with kill criteria for AI work that produces the wrong answer at scale.
A growth-stage SaaS company hired a senior product manager in Q1 against the standard JD. Strong candidate. 40 percent premium offer to win against a competing role at a peer company. The hiring panel scored her highly on roadmap ownership and spec quality.
DiscoveryBy Q3, the workflows she'd been scoped to design were being absorbed by an AI feature embedded in the product team's collaboration tool. Her sprint backlog was empty for the work she'd been hired to do. She was creative about finding new work, but the strategic surface she'd been hired against had collapsed. The CEO asked her what she was working on. She didn't have a clean answer.
OutcomeThe fix wasn't replacing her. It was redrawing the JD around the work that hadn't been absorbed: AI workflow design, context curation, human-vs-AI work allocation. The redrawn role was more strategically dense than the legacy JD. The PM moved into it. Comp held. The next hire on the team was scoped against the new shape from day one.
Yes or no for the JD on your desk. Take it as a CPO answering for the org, or as an operating partner pressure-testing a portfolio company before the next hire commits. The questions are blunt by design. If the honest answer is yes-but, it's a no.
Closing the profile-vs-reality gap isn't a documentation exercise. It's a hiring discipline. Three artifacts come out of running the redefinition cleanly.
The redrawn job description names AI workflow design, context curation, and human-vs-AI work allocation as core. The work AI has absorbed is no longer in the JD. Comp band reflects the actual strategic density of the role.
Interview panel is calibrated to evaluate AI workflow architecture, context curation judgment, and the call between human and AI work. Legacy interview rubrics get retired. The panel selects for the shape the org needs, not the shape it used to need.
Senior product managers see a path into the Product Operator role and beyond, with comp and influence that grow with the new strategic density. The career ladder reflects operating reality, not the org chart from two years ago.
The role looks the same on the org chart. The work isn't. The companies that close the gap pull away.
If you're staring at a stack of legacy JDs and a new operating reality, I'd be glad to talk.