AAperture
Back/product trends

PM Role Bifurcation in the AI Era

Updated 2026-04-21
5 min read
1,068 words

PM Role Bifurcation in the AI Era

Product management is splitting into two distinct tracks. One track is thriving; the other is structurally endangered.

The Split

Nikhyl Singhal (former Meta VP of Product, Credit Karma CPO, Google Photos/Hangouts lead; now runs Skip, a 125-person closed community of tech product leaders) identifies two PM archetypes:

Builder PMs entered the field to make things. Many have engineering or founding backgrounds. Their core skill is translating ideas into testable products. In 2026, compensation is at historical peaks and offers are high-volume. The path from idea to validated product has compressed by an order of magnitude.

Information relay PMs entered the field because of high compensation and the fit with communication and organization skills. Core skills: information packaging, stakeholder alignment, upward management. Roughly half of the existing PM population. AI tools are direct substitutes for the packaging and relay functions. The structural argument for this role is weakening.

What Companies Are Doing

Singhal observes that product leaders in his network discuss concepts in 2026 that did not exist in their vocabulary 12 months prior: running enterprise workflows with agents, chief-of-staff apps, spending all time on judgment, replacing anything software can replace. This vocabulary shift happened inside 12 months.

Predicted pattern (12–24 months): Large companies will execute large layoffs followed by large rehires. The rehires are AI-first. The people cut are two overlapping groups: those hired during recent growth phases who did not produce commensurate value, and those whose skill sets do not match the new direction.

Google example: at 20,000–40,000 employees, the honest headcount needed to hit core revenue targets was approximately 500 (less than 9%). The rest existed for expansion and exploration. Companies are recalculating this number.

What the Surviving Role Looks Like

Judgment is the core. When the cost of testing a change approaches zero and change frequency rises 10–100×, someone must decide: which changes are good? Which harm the brand? Which affect system maintainability?

Judgment in practice:

  • Evaluating whether a change is net positive to the product system
  • Deciding trade-offs between customer needs and product sustainability
  • Deciding whether a feature is worth building and whether it meets release standards

This is systems thinking. It existed from the start of internet product development; it was buried under information relay work.

Building internal tools is the second dimension. PM building in 2026 is not about being the team's 51st engineer. It is about using software to scale your own operating capacity: automated product reviews, automated standups, automated status reports, custom agents for recurring workflows.

Career Implications

Big company tenure is depreciating. Interviews shifted from "what did you do at your last company?" to "here's a scenario, what would you build and how?" A PM who spent two years making an algorithm marginally faster at Meta has a credential that reads as thin against a builder-first interview process.

Role boundaries are dissolving. Singhal's community added 13 founding-CEO transitions in 12 months (from 1 to 14 out of 125). One senior member interviewed for a CHRO role because the hiring company wanted product thinking applied to HR. Companies with acute transformation needs are recruiting PM judgment into functions that traditionally had nothing to do with product.

PMs will diffuse into every industry. After internal product orgs complete AI transformation, the same pattern moves outward: marketing, sales, HVAC companies acquired by PE, schools. The question these organizations will ask is: "who can lead this transformation?" The answer is builders who are already living in the future.

Why Change Is Hard

Singhal describes a "shadow superpower" problem. People who won under the old system have a worldview that depends on the old system being valid. They are least likely to acknowledge a new system because doing so invalidates their accumulated wins. People who were mediocre under the old system are more willing to switch; the old methods did not work for them anyway.

The target is also moving. Learning new tools in a week is insufficient if those tools are obsolete in three months. The transition is not a one-time retraining event. There is no stable endpoint to aim for.

Singhal's estimate: approximately two years to reach a new stable state with standardized practices and training systems. During that period, the instability and pace are sustained.

Singhal's Six Recommendations

  1. Find your first joyful moment — one concrete experience of building something with AI that produces a real result. Observation: every PM who completed this transition has a specific story. The moment is the switch from fear to excitement; subsequent learning becomes self-sustaining.
  2. Apply an engineer's frame to your own work — anything you do repeatedly is a candidate for automation. Singhal automated member networking, job aggregation, and content Q&A for his 125-person community.
  3. Raise your pace — the next two years require sustained effort. Some existing commitments will get less of your time.
  4. Drop ego about titles — accepting a smaller role to move through the transition is worth it.
  5. Optimize the step after next (Skip) — don't optimize the next move; optimize the position you want to be in for the move after that.
  6. You do not need to write code — you need clear goals and the ability to evaluate quality. Those are sufficient for natural language programming.

Signals Worth Tracking

Diversity is contracting. The center of the AI wave is the Bay Area; companies are hiring fewer people and defaulting to similar-background candidates. Age, gender, and ethnic diversity are declining. Women who take career breaks for family during the transition window face compounding difficulty.

Design stagnation. Global design job openings (~5,700 as of early 2026) are flat since 2023, while PM and engineering roles grew. Industry conflated design with production; AI replaces production. Taste-driven designers are undervalued in this cycle.

Engineering is shifting too. The coding skill itself is being automated. Engineers who survive long-term will look more like PMs: focused on judgment, success criteria, and quality evaluation rather than implementation. The skill boundaries between PM, engineer, and designer are converging.

Sources

Linked from