The AI PM became the highest-paid and fastest growing product specialisation

Here is a pattern I did not expect to see in the hiring data this year. The highest-paid product managers in the market, the ones commanding between $286K and $569K at senior levels, are disproportionately people without computer science degrees. An analysis of over 18,000 AI PM hires tells the story plainly: 60% of the people filling these roles did not come from traditional technical backgrounds. The most lucrative product specialisation in a generation is not being won by the people everyone assumed would win it.

That should make you curious about what is actually going on.

The technical credential myth

The default assumption in most hiring conversations is that AI PM roles require deep ML knowledge. Candidates assume they need to understand transformer architectures and training data pipelines to be taken seriously. Hiring managers put "technical background preferred" on job descriptions out of instinct more than evidence. The entire market has organised itself around a belief that turns out to be wrong more often than it is right.

I call this the technical credential myth. It is the assumption that proximity to the technology is what makes an AI PM effective. But the data contradicts it. And my experience contradicts it even more directly.

At Grab, I worked alongside product people building AI-driven features across ride-hailing and food delivery. The features were technically sophisticated: dynamic pricing, demand prediction, route optimisation, fraud detection. Every one of them required deep interaction between product teams and ML engineers. But the PMs who performed best in those rooms were not the ones who could discuss gradient descent or explain a loss function.

They were the ones who could look at the AI's output and say, "That is wrong."

Not because they understood the model's architecture. Because they understood the user's context. When a demand prediction model suggested surge pricing in a neighbourhood during what looked like a spike in ride requests, the PM who had spent three years understanding rider behaviour in Southeast Asian cities could look at the data and say, "That is a temple festival. Demand will drop in forty minutes, not rise. Do not surge." The ML engineer could not have known that. The PM with domain knowledge could.

The best AI PMs are not the ones who understand the model. They are the ones who understand the problem the model is trying to solve.

The domain advantage

This is where the career opportunity sits, and most product people are walking past it. But the domain advantage is not a vague soft skill. It is the accumulated expertise in a specific problem space that allows a PM to exercise judgment about AI outputs in ways that no amount of technical training can replicate.

A product designer I have been mentoring made this transition in a way that surprised everyone except me. She had spent ten years working in healthcare technology, designing clinical workflow tools for hospital systems. No computer science background. No ML coursework. When she told people she was interviewing for AI PM roles, the response was usually polite scepticism.

But she understood something most technically credentialed candidates did not. She knew how a nurse thinks at 3am during a shift change. She knew which clinical data points are reliable and which ones are routinely entered incorrectly because the system makes accurate entry too slow. She knew that a recommendation engine suggesting medication interactions needs to account for the fact that doctors will override it 40% of the time, and that the override rate is not a bug but a feature of how clinical judgment works.

She got the role. Within six months, she was outperforming PMs who had spent years studying machine learning. Not because she was smarter. Because her judgment about the problem space was deeper, and in AI product work, judgment about the problem space is the whole game.

Technical credentials got people into the room. Domain expertise is what keeps them there.

What AI PM actually requires

The confusion about AI PM skills comes from a misunderstanding about what the role actually involves. A traditional PM works with deterministic systems. You define requirements, engineers build them, the feature does what you specified. The feedback loop is tight and the outputs are predictable.

But AI PM work is fundamentally different. You are working with probabilistic systems. The outputs are not guaranteed. The same input can produce different results. The model will be wrong sometimes, and being wrong is not a failure state, it is an expected operating condition. The PM's job is not to make the model right. It is to decide how right the model needs to be, what happens when it is wrong, and how the user should experience both of those states.

But this is a judgment problem, not a technical one.

It requires the ability to sit with ambiguity. Most product people trained in deterministic environments find this deeply uncomfortable. They want clear requirements and binary outcomes. AI products do not work that way. The PM who thrives in AI product work is the one who can say, "This model is 87% accurate, and for this use case, that is good enough, but we need a fallback experience for the 13% where it fails." That sentence requires product judgment, user understanding, and risk tolerance. It does not require knowing how the model works under the hood.

But it also requires a specific kind of intellectual honesty. The temptation in AI product work is to defer to the model. The model says X, so we ship X. The PMs who fall into this trap are usually the ones with the strongest technical backgrounds, because they trust the model's reasoning more than their own judgment about the user. The PMs who resist this trap are usually the ones with domain expertise, because they have an independent basis for evaluating whether the model's output makes sense.

Why this matters for your career

The AI PM market is not slowing down. The compensation data is not a temporary spike. Organisations are building AI into every product category, and they need product people who can make judgment calls about systems that behave probabilistically. The supply of people with that specific combination of skills (product thinking, domain expertise, comfort with ambiguity) is much smaller than the demand.

But here is what most career advice gets wrong about this moment. The path into AI PM work is not a bootcamp on machine learning fundamentals. It is not a certificate in prompt engineering. Those things are not useless, but they are not the differentiator. The differentiator is the domain advantage: years of accumulated expertise in a problem space that gives you judgment no course can teach.

But if you have spent a decade in fintech, healthcare, logistics, education, or any other domain where AI is being applied, you already possess the most valuable asset in the AI PM market. You just do not recognise it as such, because the market has been telling you that technical credentials matter more. The data says otherwise.

The technical credential myth has cost good product people years of hesitation. They waited to learn things they did not need to learn before applying for roles they were already qualified to fill. The domain advantage was there all along, hiding in plain sight, disguised as mere experience.

The best career moves rarely look like credentials on paper. They look like the slow accumulation of judgment in a domain where that judgment turns out to be exactly what the market needs, right when it needs it most.