Salesforce's answer is short. Two skills, AI prototyping and AI evals, and five traits, with "can you say what good looks like?" at the top. That's from Aakash Gupta's conversation with Jayesh Govindarajan, who runs the roughly 700-person Agentforce org, published November 3, 2026.
What I take from it: the job description no longer describes a coordinator. Every trait measures whether you can see the gap between what an agent produced and what the customer needed. Figma is on the same path. Ezra Mechaber's PM OS is a shared repo of 31 skills every Figma PM uses, plus an agent that runs growth experiments with one human checkpoint. The PM is the checkpoint.
How I'd hire for it
Skip the case study about prioritizing a backlog. Give the candidate one real customer outcome and 45 minutes, and ask for ten outputs they'd ship and five they'd reject, one line of reasoning each. Then hand them an agent's actual output and ask which bucket it goes in. That tests skepticism and setting the bar in one sitting, and it's the work they'll do on day one.
The full argument, including why the Product Builder belongs in one loop with design, product marketing, and FDE under the CPO, is in part 1 of The PM Transition. Every part is collected on the series hub.