Stop Creating New Roles. Start Developing New Capabilities.
The job boards are flooded with listings for "AI Product Managers." Companies are creating entirely new roles, sometimes entire teams, to manage AI product development. Having built and led product teams that shipped AI features at scale, we believe this is mostly wrong.
You do not need an AI Product Manager. You need product managers who have learned to work with probabilistic systems. The distinction is critical.
Why the "AI PM" Title Causes Problems
It creates a silo. When you hire an "AI PM," you implicitly tell the rest of your product team that AI is someone else's problem. The result: your core product managers do not develop AI literacy, and your AI PM becomes a bottleneck for every initiative that involves a model.
It attracts the wrong profile. The "AI PM" title draws candidates who are excited about the technology rather than the problem. The best AI product work we have seen comes from PMs who are obsessed with the user problem and view AI as one possible tool, not from PMs who are obsessed with AI and go looking for problems to apply it to.
It miscategorizes the challenge. The hard part of AI product management is not understanding how transformers work. It is redesigning user experiences for non-deterministic outputs, setting success metrics for systems that are sometimes wrong, and managing stakeholder expectations when your product behaves differently for every user.
The Skills That Actually Matter
Every product manager shipping AI features in 2025 needs these capabilities:
Designing for uncertainty. Traditional products give the same output for the same input. AI products do not. A PM needs to design experiences that handle variability gracefully: confidence indicators, fallback paths, easy correction mechanisms, and transparent limitations.
Defining success for probabilistic systems. "Accuracy" is rarely the right metric. A PM needs to understand precision vs. recall tradeoffs, know when a false positive is worse than a false negative (and vice versa), and translate these technical concepts into business terms.
Evaluation and testing intuition. How do you QA a system that gives different answers each time? PMs need to understand evaluation datasets, develop intuition for when model behavior is unacceptable, and build testing processes that catch failures before users do.
Ethical product judgment. AI amplifies bias in data. A PM needs to ask: Who is harmed if this system is wrong? Whose data are we using, and did they consent? Are we building something that should exist?
What to Do Instead
- Invest in AI literacy training for your existing product team rather than hiring a specialist who creates a dependency
- Pair your strongest PMs with your ML engineers on the first AI initiative. The PM will learn faster than any hire from outside
- Hire for product judgment and user empathy, then teach the AI-specific skills. The reverse almost never works
- Create shared evaluation frameworks that the entire product team uses, not just the "AI PM"
The companies building the best AI products are not the ones with the most AI PMs. They are the ones where every PM on the team can evaluate a model's output, design for uncertainty, and make sound judgment calls about when AI adds value and when it does not.