LinkedIn just validated a thesis I have been arguing for two years, and got the mechanism wrong while doing it. Tomer Cohen replaced LinkedIn's APM program with a Product Builder program, and most coverage read it as a story about generalists who can touch design, product, and engineering. That is the surface reading. It misses the actual shift.
The relay race was the whole problem
Product Builder was never about a PM learning to write React. It was about collapsing the distance between deciding and making. The traditional PM job was coordination: gather requirements, write a PRD, hand it to design, hand it to engineering, manage the relay race. That job dies not because AI teaches PMs to code, but because AI kills the reason the relay race existed in the first place. The relay race existed because translating an idea into a working artifact was expensive and slow, so you needed specialists to do each leg. When a single person can go from idea to a working prototype in an afternoon, the specialization that justified the handoffs stops paying for itself.
The real question is organizational, not individual
So when companies frame Product Builder as a skills question, upskill your PMs, teach them Figma and a bit of code, they are solving the wrong problem. The right question is: what do you still need a coordinator for once the person with the idea can produce the artifact? The answer, in most cases, is less than you think. This is why it is an org-design win, not a training-budget win. The companies that win this transition are not the ones retraining PMs to be full-stack. They are the ones who figure out that the PRD, the roadmap deck, and the handoff meeting were never the job. They were the tax you paid for not being able to build.
Two skills, not everything
Here is where I differ from the generalist framing. I do not think the future PM needs to be good at everything. I think the future PM needs to be good at prototyping and evaluation, specifically, and can outsource or automate almost everything else. That is a narrower and sharper skill set than being a generalist across product, design, and engineering. Prototyping is the instant-prototype loop any PM can now run. Evaluation is the eval discipline that keeps a cheap prototype honest. Generalism is the consolation prize for people who have not figured out which two skills actually matter.
Name the two skills that matter. Get good at those. Let the coordination tax expire.