Nurkhon's piece on the three designer archetypes Jenny Wen hires at Claude is one of the sharpest career reads I've seen this quarter. The three archetypes (strong generalist, deep specialist, prototype-coder) are real. The traditional senior product designer who hands off Figma mockups to engineers is not on the list, and the piece is right to call that out.
I want to extend the argument. The same split is hitting PMs. Same three archetypes. Different title. The piece reads like a design career piece. It is actually an operating-model piece.
The short version
Jenny Wen, head of design at Claude, hires three designer archetypes: generalist (designs and ships across disciplines), specialist (extraordinary craft in one area), and prototype-coder (works directly in code). The traditional senior product designer is missing. Nurkhon's piece nails the diagnosis. The same archetype split is happening in PM, with builder PM mapping to archetypes one and three, translator PM disappearing in the middle, and deep specialist PM surviving only in regulated domains and outcome-specialist roles. The shift is not design-specific. It is the AI-era operating model showing up in the discipline that already had the prototype-in-code pattern.
For the PM version of the same split, see The PM Interview Question I'd Refuse to Answer in 2026 and The Old PM vs The Product Builder.
What Nurkhon gets right
Three points that apply across roles, not just design.
Job postings shifted from years-of-experience to shape-of-capability. "Senior" used to be a number. Now it's a shape. The hiring text Nurkhon quotes ("comfort operating without a defined brief," "prototype in code and present to stakeholders in the same afternoon," "ability to ship without waiting for research") is shape language. None of those qualifications care how long you've been in the industry. They care what you can produce in an afternoon.
This is also true for PM hiring. The 2026 PM job post that means it asks "what's the last thing you shipped without engineering" not "how many years have you been a senior PM." Same shift.
The polished portfolio is not the asset it used to be. A portfolio is a curated past. A prototype is a present-tense artifact. Polished portfolios get filtered out fast in 2026 hiring loops because they signal someone who optimizes for the artifact reviewers used to ask for, not the artifact the work now requires.
The PM equivalent is the slide deck of "products I've shipped." Same fate. The artifact that wins now is the live prototype.
The traditional senior is a structural casualty. This is the part that will hurt for the people in the role. The traditional senior product designer (and the traditional senior PM) was the middle-of-the-stack role that depended on the coordination, filtering, and translation work that AI now does. The job description hasn't changed enough to keep up with the operating model. The shape that survives is the one closest to the customer outcome.
The PM version of the same split
Map archetype to PM role:
Archetype one (strong generalist) → builder PM. Ships across disciplines. Writes evals. Prototypes in code with Claude Code or Cursor. Sits in customer calls, designs the next feature, ships the prototype, and writes the LinkedIn announcement. Most of the senior PMs I respect in 2026 fit this shape. It is the dominant builder PM archetype.
Archetype two (deep specialist) → outcome specialist or domain specialist. This is the smaller but real PM track. A growth PM who owns activation depth-first for three years. A pricing PM who has seen six migrations. A healthcare PM who knows the FDA pathway end-to-end. Domain or outcome mastery that nobody else on the team has. Survives because the depth is not commoditized. Smaller pool, harder to fake.
Archetype three (prototype-coder) → AI-native PM who ships agents. The PM whose primary artifact is a working agent in production. Ships the prototype, builds the eval suite, owns the agent's behavior end-to-end. This archetype barely existed in 2024 and is now the fastest-growing PM shape in 2026 hiring loops.
The middle role (the senior PM who runs sprints, manages stakeholders, defends roadmaps, and "owns the backlog") is the same structural casualty as the traditional senior designer. It's not that the role can't be done well. It's that the role is the one AI is hollowing out fastest, because the coordination work that justified its existence is what AI does most cheaply.
Where I'd push back on Nurkhon
One small place.
The piece frames the shift as design-specific because Jenny Wen is the source. The implication a reader takes away is that designers are the canary, and other disciplines have more time.
I don't think that's right. The PM hiring data I've seen across the last two quarters shows the same three-archetype split, just three to six months behind design. Engineering is going through it too (the "AI isn't replacing developers but eroding craft" debate is the same thing in different vocabulary). Product marketing is next, and it's coming fast.
The Wen archetypes are not a design phenomenon. They are the AI-era operating model surfacing in the discipline that already had the prototype-in-code pattern. Designers have been prototype-coding longer than PMs have, so the pattern arrived in design hiring first. That doesn't mean PM hiring loops have another year. It means the loops that haven't shifted are going to shift suddenly.
What to do this week
If you are a senior PM or senior designer:
Build a ten-hour artifact that demonstrates which archetype you fit.
If you're a generalist, ship something across three disciplines in a week. A prototype with a landing page and a Loom demo. A new product surface with the eval suite and the announcement copy. The artifact should signal that you can move across the stack without handoffs.
If you're a deep specialist, ship a teardown or a primary-source analysis that nobody else on your team could produce. Five days into a specific domain or outcome. The artifact should signal depth nobody can fake.
If you're a prototype-coder, ship something in production. An internal tool the team adopts. An agent that lives in the workflow. A scrappy feature that customers use. The artifact should signal that production-readiness is the bar, not Figma fidelity.
The thing you do not ship is a portfolio. Portfolios are the wrong artifact for the archetypes that are getting hired.
The career version of the kill list
The Wen archetypes are the design discipline naming what every discipline is going through: the middle-of-the-stack senior role is shrinking, and the only survival paths are end-to-end ownership or extreme depth.
Nurkhon nailed it for design. The same diagnosis applies to PMs, engineers, and PMM. The action is the same. Pick an archetype that maps to your shape, build the artifact the archetype produces, and update what you call yourself.
The titles haven't caught up yet. The hiring loops already have.
The 12-question PM interview diagnostic and the builder PM artifact templates are on the toolkit. For the role-shape this post diagnoses, see Hiring the Builder PM and Your AI Agent Fleet.
Sources: Nurkhon, "Companies want three types of designers in 2026", Jenny Wen on Lenny's Podcast: The design process is dead, Jenny Wen on X, Marty Cagan on the product trio, Anthropic / Claude design team.
Further reading
Frequently asked
What are the three designer archetypes Jenny Wen is hiring at Claude?+
Per Nurkhon's piece citing Wen: (1) the strong generalist who can design, prototype, and ship across disciplines; (2) the deep specialist with extraordinary craft in one area; (3) the prototyper-builder who works directly in code. The traditional senior product designer who hands off Figma mockups to engineers is conspicuously not on the list.
Why does the PM role look like the same split?+
Because the underlying force is the same. The middle-of-the-stack role (the senior generalist who is a chooser, not a builder) was the one that depended on filtering and coordination work that AI now does. What survives is end-to-end builder, deep specialist, and prototype-coder. Same three archetypes. Different title.
Which archetype is the builder PM?+
Closest to archetype three (prototype-coder) with overlap into archetype one (generalist who ships). The builder PM ships prototypes in code, not specs. They sit closest to the engineering work. The translator PM was archetype two-and-a-half, the middle role that's getting cut.
Is the deep specialist still a viable PM track?+
Yes, in two narrow places. Regulated domains (healthcare, fintech, defense) where domain mastery is load-bearing. And growth/pricing specialists who own one outcome dimension end-to-end. Outside those two, the deep specialist PM is shrinking.
What does Nurkhon's piece get right?+
Three things. (1) Job postings have shifted from years-of-experience to shape-of-capability. (2) 'Comfort operating without a defined brief' is the actual hiring signal. (3) Polished portfolios are not the asset they used to be. All three apply directly to PM hiring loops too.
Where does the piece miss?+
The framing implies the shift is design-specific because of Jenny Wen's perspective. The same shift is happening across PM, engineering, and even product marketing. Wen's archetypes are not a design phenomenon. They are the AI-era operating model showing up first in the discipline that already had the prototype-in-code pattern.
What should a senior PM or senior designer do this week?+
Build a ten-hour artifact that demonstrates which archetype you fit. If you're a generalist, ship a working prototype across three disciplines (design + code + marketing). If you're a specialist, ship a teardown that demonstrates depth nobody else has. If you're a prototype-coder, ship something in production. Don't ship a portfolio. Ship the artifact the archetype produces.
Comments (0)
Sign in with LinkedIn to leave a comment.
Sign in with LinkedIn