LinkedIn's CPO killed the APM program, and that was the most under-discussed piece of product leadership news of the last year. Tomer Cohen said plainly on a December 2025 podcast with Lenny Rachitsky that the APM program at LinkedIn was designed for a role his company no longer hires for. He rebuilt the early-career pipeline around what he called full-stack builders. If your company runs an APM program, you are investing in talent that will graduate into a role that is being automated.
Why the 2018 APM program does not work now
Every major APM program I know, Google APM, Facebook RPM, LinkedIn APM now gone, Uber APM, Salesforce APM, Microsoft PM Rotational, is a pipeline to produce the PM role of 2018. The curriculum teaches PRD writing, stakeholder management, metrics definition, sprint planning, and presentation. Three things changed that the curriculum has not caught up with.
The median PM task is automated. Writing specs, producing analysis, drafting communications, running standups, scheduling research, all now done faster and often better by an agent. An APM who spends two years mastering these graduates as an expensive version of a workflow that runs for pennies per hour. The skills that matter are not in the curriculum: prototyping, evals, cost and latency thinking, agent design, and model selection. And the two-year rotational structure was built on the assumption that PM work takes years to master, when a Product Builder can ship a meaningful prototype in week two.
What replaces it
The 12-week Product Builder apprenticeship. The apprentice is embedded with a senior Product Builder, not rotating, not sampling, not observing. Pairing. They produce four prototypes, and one goes to production.
Weeks 1 to 2, they shadow and write a one-page memo on the three most important bets the product should make. The senior pushes back hard. Weeks 3 to 5, first prototype, small scope, real eval rubric, shown to three actual customers. Weeks 6 to 8, second prototype, harder, owning the unit economics decision. Weeks 9 to 10, third prototype as a negative bet meant to fail and prove a hypothesis against. Weeks 11 to 12, fourth prototype that ships to production with full ownership of prototype, rubric, README, and the first week of eval monitoring.
What is explicitly not in the program: no stakeholder management training, no presentation training, no frameworks-focused curriculum, and no rotational diversity. One product area, one senior mentor, 12 weeks of depth. Evaluation is objective: did the four prototypes ship, did the evals pass, did the production ship hold up. No 360 reviews, no nomination committees.
Where to start
If you cannot reshape the whole program, three moves. Hire for portfolio not resume, so the first question is "walk me through a prototype you shipped in the last six months." Pair every new hire with a senior Product Builder for their first 90 days, with the senior's goals including the apprentice's first production ship. And publish every apprentice's four prototypes and one ship on an internal page so the bar becomes visible.
This week, pair one new early-career hire with a senior Product Builder and make four shipped prototypes the graduation criterion, not a presentation.