The PM's AI Transition Guide 01 | Which "AI Product Manager" Are You Actually Trying to Become?

Tencent opened its 2027 campus recruiting on August 11, aimed at students graduating between January 2026 and December 2027.

The announcement lists a batch of AI-native roles: AI full-stack engineer, agent development engineer, AI application engineer, AI algorithm engineer, AI product manager, AIGC art creation.

The same announcement changed something else. Tencent’s long-standing hiring creed used to be “ambitious, eager to learn, gets things done.” This time three more specific clauses follow it: proactively find and define problems, evaluate and verify AI output, turn ability into visible results.

Not one of the three is about large-model technology.

And they weren’t written for the AI product manager role alone. Tencent opened five job families this round — technology, product, design, marketing, and corporate functions — and the standard applies to everyone across all five.

That stopped me. Because every “transition guide” I’ve read over the past year or so is about something else entirely.

”AI product manager” names two different things at once

Search for how a PM should transition into AI and the results are remarkably uniform: a learning roadmap — prompt engineering → RAG → agents → LLMOps — a salary table, and a signup link at the bottom.

I started down that road too. It took me a few months to notice that what I needed wasn’t on the map.

The trouble is that one job title gets used for two different things:

Tencent’s three clauses describe the right-hand column. The courses being sold teach the left.

The left column isn’t fake. It’s real, and it’s growing.

Zhilian’s numbers only mean something when you read them together

Zhilian Recruitment published its 2026 AI Industry Talent Development Report on July 16, based on first-half platform data.

Look at role-level growth alone and AI PM looks excellent:

• Agent-related technical talent: +244% year over year
• AI product manager: +87.7% year over year
• Data annotation / AI trainer: +30.3%
• AI engineer: +19.3%

The number is still climbing. From the same organization, vice president Li Qiang put Q1 growth at +81%; the half-year figure is 87.7%. His data covered 404 million job seekers and 15.49 million companies on the platform.

But the same report carries another figure that belongs right next to it: the entire AI industry’s job postings grew only 10.6% year over year, while the number of job seekers grew 10.5%.

The AI product manager role is growing fast, but it’s growing inside a pool that expanded only 10.6%.

87.7% is a growth rate, not a volume. Doubling a small base can still leave you with a small absolute number. And the role growing far faster — agent development at +244% — is an engineering role that product managers can’t simply move into.

Postings up 10.6%, applicants up 10.5%. Those two numbers sit almost on top of each other: the door is getting wider, and the line outside it is lengthening at the same pace.

The fastest AI hiring growth isn’t at large-model companies

Two more figures from the same report, broken out by industry:

• AI engineer postings in new energy: +38.2% year over year
• AI engineer postings in aviation, aerospace, and shipbuilding: +23.5%

Both are well above the industry-wide 10.6%.

A meaningful share of the growth, in other words, isn’t at companies building large models. It’s at traditional industries putting AI into their own operations. The number of companies hiring rose 24.8% — faster than the 10.6% growth in postings — which means more companies each opened a few seats, rather than a handful of firms hiring at scale.

That has a fairly direct bearing on which way to move. If AI work is spreading into new energy, manufacturing, and aviation, the person those companies need may not be a product manager who understands large models. More likely it’s a product manager who understands that industry and can put AI to work in it.

That second person already has the domain knowledge. What’s missing is the way of working.

How narrow is the door? 54 job descriptions give you a read

Someone went through 54 AI PM job descriptions at leading companies. The recurring requirements cluster tightly: prompt engineering, RAG, function calling, data alignment, SFT / RLHF, automated evaluation systems, low-code platforms like Coze and Dify, plus paper-reading and the ability to prototype in code.

What employers weigh most heavily is whether you have real experience shipping AI into production. The reason isn’t hard to see: AI projects run into a pile of problems that have nothing to do with technology — you can’t get the data, a department won’t cooperate, users simply don’t trust what the model returns. Only people who’ve done it know where those holes are.

That same analysis turned up a counterintuitive finding: no agent project experience doesn’t mean no shot. Employers will credit hands-on work on low-code platforms, and they’ll credit a background as a heavy user.

So the road isn’t sealed off. It just asks you to produce something, rather than produce proof of attendance.

The catch is that “something” is exactly what a learning roadmap cannot hand you.

”Evaluate and verify AI output” has no job-title prerequisite

Back to Tencent’s three clauses. The middle one is the one I kept staring at: evaluate and verify AI output.

What makes it unusual is that it asks nothing of your job title, your employer, or your industry. Whatever work is in front of you right now, the moment you start doing it with AI, this begins the same day.

It’s also harder than it looks. AI will describe unfinished work as finished — not out of dishonesty, but because it doesn’t know which parts it left undone either. Either you can spot it yourself, or you wait for users to tell you after launch.

Last year I started trying to take things all the way to shippable on my own. Two of them have commit histories you can check: an ID-photo tool, 21 commits, June 13 through June 30, now in the App Store; and a PDF tool, 43 commits, the first on July 5 and the last on July 11, shipped for both iOS and macOS.

I’m not citing those numbers to suggest it was hard. The opposite — most of the hard parts were absorbed by AI. The time went somewhere else: judging whether what it produced was usable, and finding the places I had to take over by hand.

Tencent’s phrase for this is “turn ability into visible results.” Visible is the load-bearing word. “Familiar with large models” on a résumé can’t be verified by the person reading it. A link they can click answers the question in thirty seconds.

I can’t tell you which road to take

If your company happens to be building large-model products, or you want to work somewhere that does, the job route is real. The 87.7% is real. The job descriptions spell out what they want, and you can go fill those gaps.

If the work in front of you has no direct connection to large models — and per that report, a lot of the growth is flowing toward exactly this kind of work — then grinding through RAG and SFT may pay less than actually building one idea all the way through, once.

It’s also possible these two roads were never meant to be read separately. On the same day Tencent listed “AI product manager” in its job table, it wrote “evaluate and verify AI output” into the standard for all five job families. Same announcement, same day.

Here’s what I still haven’t worked out: if nobody at your company asks you to produce this kind of thing, and your performance review doesn’t look at it, what keeps you going? I’ve gotten this far by building my own products, but that clearly isn’t available to everyone — it eats your evenings and weekends, and for a long stretch nobody pays you a bonus for it.

I don’t have an answer to that one. If you do, I’d like to hear it.