DEV Community

Javier Castro
Javier Castro

Posted on

The Middle PM Is Not a Generalist. It's a Warning Sign.

#thesplitproductmanager

The PM role is splitting into two distinct archetypes — and the one stuck between them isn't versatile. They're just overdue for a reckoning.

Picture a product manager at a mid-sized enterprise SaaS company — somewhere in the analytics or fintech corridor. They run the sprint ceremonies, write the PRDs, manage the roadmap presentation for the quarterly business review, and pride themselves on being "technical enough" while also being "strong with stakeholders." They are, in the parlance of every PM resume written between 2017 and 2023, "a bridge between business and engineering."

That bridge is now a bottleneck.

Not because this person is bad at their job. They may be quite good at it, in the way that a skilled fax machine operator was quite good at their job in 1997. The problem is structural. The PM role is no longer one job. It's becoming two — and the territory in the middle, where most working product managers actually live, is quietly collapsing.

The Fork in the Road Has Already Happened

The generalist PM role has been splitting in two, and by most accounts it's been obvious since at least mid-2025. The divergence isn't subtle anymore.

The first archetype is the builder-PM: AI-native, ships prototypes independently, works on teams that deliberately blur the PM/engineer line. This is the PM who shows up to a design review with a working Figma prototype, or drops a functional feature scaffold in Cursor before the engineering spec is even written. Old PM-to-engineer ratio assumptions are collapsing because the job now includes shipping code, not just speccing it.

The second is the integrator-PM: high-EQ, cross-functional, owns the roadmap in messy B2B environments where internal alignment is still fundamentally a human problem. This PM survives at large enterprise orgs not by prototyping but by knowing exactly which VP to get in a room before a roadmap review, and precisely which talking points will neutralize the objections from legal before they surface. Their superpower is political intelligence, not technical fluency.

The most significant data point validating this shift came out of LinkedIn in December 2025. The company dismantled its traditional associate product manager program and replaced it with an associate builder track that trains hires to code, design, and product manage — while also adopting small "pods" of full-stack builders. LinkedIn's chief product officer Tomer Cohen confirmed the transition on Lenny's Podcast, announcing that the new program would begin in January and teach participants "how to code, design, and PM at LinkedIn."

Applicants don't submit a resume. They submit a 60-second demo of a product they built, and answer questions about how they used AI in building it.

That is not a hiring preference. That is a public statement about what the word "product" now means.

The Middle Is Not a Strategy. It's a Position.

Here is the claim worth arguing over: the PM stuck in the middle isn't a generalist. They're a specialist in tasks that are being automated out of relevance.

That's a sharp thing to say, and it deserves a fair hearing as a counterargument. Many practitioners — reasonable ones — will push back. Product management has always required both builder instincts and political fluency. Marty Cagan at SVPG has spent years arguing that the best PMs are deeply involved in product creation and act as the connective tissue of a cross-functional team. The integrator skills and the builder skills aren't mutually exclusive; they're complementary. The "full-stack PM" is arguably the ideal, not the outdated archetype.

That counterargument is correct in theory. It also describes a very small number of people. In practice, the group under the most pressure is the one doing neither archetype role distinctively — operating in the middle at a mediocre level on both dimensions and calling it range.

Product management is becoming an 80/20 profession — not because 80 percent of PMs are about to lose their jobs, but because the distribution of value is getting much more extreme. A smaller group will create a disproportionate amount of impact, and the gap between strong and average will become much easier to see.

The labor market is already registering this. Senior PM hiring at staff, principal, and director levels grew 34% in 2025, while junior and mid-level PM hiring shrank 12%. The role isn't disappearing — it's concentrating at the top. And when you look at where the cuts came, they followed a predictable pattern. According to data analyzed by Mind the Product, management layers were most affected, with VP-level PMs down 38%, directors down 35%, and managers down 31% from their peak — managers representing the largest reduction in absolute terms.

It was the middle of the org chart that got hollowed out. The people whose jobs consisted mostly of translating information between engineers and executives, running ceremonies, maintaining roadmaps, and drafting quarterly reviews. That is precisely the work that tooling now handles faster and with less friction. The middle layers of product management — focused solely on stakeholder management or process orchestration — are being automated out of relevance. Microsoft reportedly discussed reducing the number of middle managers and non-coders specifically in a bid to increase the ratio of programmers to product managers.

This was not a surprise, for anyone paying attention.

Why the Middle Felt Safe for So Long

The middle position had a reasonable structural rationale for a long time. Enterprise organizations are genuinely complex. Aligning engineering, design, marketing, sales, and finance around a shared roadmap requires sustained human effort that doesn't compress cleanly into a sprint tool or a shared Notion doc. Large B2B customers want a PM who knows how to handle their procurement process, not one who ships wireframes. The integrator skills were real, valued, and often underpaid.

But that same complexity became a hiding place. A PM who fills their week with alignment meetings, status updates, and stakeholder briefings can look extremely busy while contributing very little to the actual direction of a product. The comfortable middle is the PM whose primary value is being organized, articulate, and good at running process — and who is having a harder and harder time explaining why that's a differentiated skill.

Meanwhile, the barrier to entry for creating functional software has collapsed. With tools like Lovable, Cursor, and Replit, a PM who cannot prototype their own ideas faces a hard career ceiling. The distance between a thought and a usable first version has become too short to justify handing every idea over the wall. A PM who can walk into a technical conversation with something tangible is operating from a very different position than one who arrives with a document describing what someone else should build.

The integrator path has its own structural risk, too. Builder-PMs are more exposed to commoditization as software creation gets easier; integrator-PMs are more exposed to top-down directive pressure when capital is tight. Neither track is inherently secure. But at least each has a clear value proposition. The middle has a resume.

What Concrete Moves Actually Get You Out of It

There is no single escape hatch. But there are two honest choices, and a third that pretends to be a choice while actually being inaction.

The first honest choice is to commit to the builder track. That means shipping something publicly, right now — not planning to learn a prototyping tool next quarter, not watching tutorials, but actually publishing a Lovable app or a Cursor-built prototype that solves a real user problem. LinkedIn's new model aims to build people who can take an idea from concept to launch with far fewer handoffs. That is the bar. Not theoretical capability. Demonstrated shipping.

The second honest choice is to go deep on the integrator track — but with ruthless specificity. Not "I'm good at stakeholder management," which is what every middle PM says. A demonstrable track record in a specific vertical (fintech compliance, healthcare procurement, enterprise security) where the human alignment problem is genuinely hard and the domain knowledge takes years to acquire. Generalist PMs who rely primarily on coordination skills face reduced demand in highly technical environments, while those who combine strategic thinking with domain mastery are increasingly viewed as high-impact contributors.

The third option — continuing to describe yourself as "balanced" or "full-stack" without evidence for either — is the one that leads to the awkward performance review conversation in eighteen months.

The most useful question to ask yourself before your next Monday standup: if you removed all the coordination and meeting facilitation from your week, what would you actually have built? If the answer is "not much," that's not a reflection on your work ethic. It's a signal about which archetype you're drifting toward — and whether you've made that choice consciously or by default.

The generous read on all this is that the PM role is maturing into two genuinely different professions, and that's fine — specialization is how every discipline grows up. The less generous read is that the generalist middle was always, to some degree, a job description that survived because it was hard to measure and easy to hire for at scale.

Both reads are probably true. The market is just finally resolving the ambiguity.

Sources

Top comments (0)