What “Design” Actually Looks Like at AI-Native Companies in 2026
A field report from inside the companies rewriting the rules
There’s a moment Jenny Wen keeps coming back to. She’s the Head of Design for Claude Cowork at Anthropic — formerly Director of Design at Figma, where she built FigJam from scratch. She left a director title to go back to individual contributor work. That choice alone should tell you something is shifting.
On Lenny Rachitsky’s podcast in March, she said it plainly: “This design process that designers have been taught, we sort of treat it as gospel. That’s basically dead.”
Not evolving. Not disrupted. Dead.
And the thing that killed it wasn’t AI in the abstract. It was an engineer at Anthropic named Boris who started spinning up seven Claude instances simultaneously and shipping prototypes before Jenny had even opened Figma. The power dynamic between design and engineering flipped — and most designers haven’t felt it yet.
The Numbers Are Already Strange
The Designer Fund and Foundation Capital just released their AI in Design 2026 report, drawing on 900 designer responses and 25+ interviews with leaders at Anthropic, Stripe, Cursor, DoorDash, and others. A few numbers from it that I keep returning to:
50% of designers — including brand designers, not just the engineering-adjacent ones — have pushed AI-generated code to production. Only 20% of those identify as design engineers. The rest are people who, a year ago, had never touched a terminal.
65% of designers say they’re now doing more product management and engineering work. 40% say the reverse is also true — their PMs and engineers are doing more of what used to be design.
And the average designer’s toolstack went from 3 tools to 7. In one year. Nearly half say they’re still searching for their definitive setup.
That last detail captures something true about this moment. We’re all mid-molt.
What “Design” Actually Looks Like at AI-Native Companies
At Anthropic, the workflow has split into two distinct modes, according to Jenny. There’s the rapid-fire layer — engineers building prototypes at speed, designers embedded inside that loop to steer quality and intent rather than lead from the front. And then there’s the longer arc work: the kind of design that requires holding a broader vision across six months rather than five years.
The classic discovery → mock → iterate cycle is gone. Not because it was bad design thinking, but because by the time you’ve completed a diverge-converge loop, the engineer has already shipped three working versions and learned something real from users. You can’t block that with a process built for a slower world.
Jenny describes design at Anthropic as “supporting engineer-led execution” — which sounds like a demotion until you realize the designers doing this well are the ones shaping what gets built, why it gets built, and how it feels when someone actually uses it. The title on the org chart matters less than the accountability you hold.
At Notion, the framing is similar. Designers are working inside the product squad, not as a handoff layer. At OpenAI, the job posting for ChatGPT’s product designer explicitly asks for someone who gets “excited about being immersed in the AI research process and defining how AI-first products should look and behave.” Research immersion. Behavioral definition. Not wireframes.
What Vercel has done to formalize this is instructive. Their Design Engineer role operates in three modes: design collaboration (working alongside an engineer in Figma or code), product team integration (embedded inside a squad), and independent ownership (sketches, socializes, and ships alone). Their job description defines the role not as a hybrid but as “one fluid workflow.” The conjunction “and” in “design and engineering” is doing less work than it used to — it’s becoming an ampersand where both sides blur into each other.
The Tool Stack Is Rewriting Itself
Phil Vander Broek from Superhuman described what I think is the most significant shift in the report: “Figma has shifted from being the primary design tool to a canvas for quick exploration and polishing details as input for Claude Code.”
That’s a seismic repositioning of a tool that defined an entire era of product design. Figma didn’t disappear — the UX Tools State of Prototyping survey confirms it’s still the most-used design tool in 2026. But its role changed. It’s an input now, not the destination.
The pipeline designers at leading companies are actually running looks something like this: a rough sketch or prompt in Figma, fed through the Figma MCP server into Claude Code or Cursor, which generates working UI, which then gets pulled back into Figma as editable frames via the Anthropic-Figma bridge launched in February. Rapid cycles between code and canvas, with the designer as the quality filter and direction-setter at each pass.
Obsidian is showing up for design system documentation and decision logging. Linear for tracking what’s actually shipping and what’s rotting in the backlog. Claude Code and Cursor for prototype iteration. The designer as orchestrator of a pipeline, not author of a deliverable.
I’ve been building this way for a few months on my own projects, and the honest truth is: the first week feels like you’ve lost your superpower. The second week feels like you got a different, larger one.
Three Archetypes That Are Actually Getting Hired
Jenny mentioned she’s currently hiring for three specific archetypes at Anthropic. She didn’t name them in the podcast, but based on what’s emerging across job posts and team structures at leading AI companies, the pattern is readable:
The Systems Designer. Someone who thinks in constraints, tokens, and states — who can encode a design system as a machine-readable file that an AI can follow, rather than a Figma library that an engineer has to manually interpret. This person thinks in CLAUDE.md files as much as component specs.
The Prototype-first Designer. Someone who reaches for code before mocks, who can hold a working prototype as their primary thinking medium. At early-stage companies, the Foundation Capital report found 68% of designers are already shipping code. This archetype is table stakes, not differentiator, at most AI-native companies.
The Judgment Layer. The rarest and arguably most valuable — the designer who can sit at the intersection of product and engineering, make fast decisions about what actually matters, and take accountability for those decisions. Jenny put it cleanly in an earlier interview: “Taste without accountability is decoration. Taste with accountability is leadership.”
The third archetype is the one that AI cannot replace, and the one that most designers are least trained to inhabit. We were never taught to be accountable for the decision — only for the design.
What This Actually Means If You’re a Working Designer
The shift isn’t that designers should all become engineers. Half the designers shipping code to production in 2026 don’t call themselves design engineers. The shift is that the sequencing changed — and with it, where your value sits.
When engineers can generate functional UI faster than you can finish your first round of exploration, your value is no longer in producing the artifact. It’s in knowing what the artifact should do, why it should exist, and whether what got built is actually right.
That’s a PM question. It’s also a taste question. It’s also a systems-thinking question. Which is probably why 65% of designers say they’re doing more of all three.
A few things worth building into your practice right now:
Learn to think in working prototypes. Not wireframes that need translation — code that runs. Claude Code, Cursor, Framer’s AI layer — pick one and get fluent enough to use it as your thinking medium, not just a production shortcut.
Get close to engineers earlier. The designers who are thriving in this shift are the ones embedded in the build loop from day one, not brought in to review at the end. The double-diamond process was partly a compensation for the friction of late handoffs. Remove the friction, and you can remove the process.
Own the decision, not just the design. When you’re the person who decides what gets built next and why, you’re irreplaceable. When you’re the person who produces the mock of what someone else decided, you’re increasingly optional.
The Open Question
The thing I keep sitting with: Jenny’s own words on whether AI will eventually match human taste and judgment. She said: “We’ll get better at taste and judgment and design. We might be holding onto that a little bit too much.”
This is the head of design at the company building the most capable AI system in the world. She’s not speculating from the outside. She watches it happen daily.
So the question isn’t whether the design process is dead — that’s already settled. The question is what comes after the moat of taste, if the moat eventually floods. And the answer I keep coming back to is the same one that survives every wave of automation: the people who understand users, who feel the friction before it shows up in the data, who can hold a direction when everyone else is iterating without one.
That’s not a design skill. It’s a human one. And it might be the only thing worth sharpening right now.
References
Foundation Capital & Designer Fund. AI in Design 2026 Report. May 2026. foundationcapital.com/ideas/how-ai-is-reshaping-design-in-tech
ArtificialStudio. The year designers stopped being just designers. May 2026. artificialstudio.ai/blog/ai-design-report-2026
Designer Fund. AI in Design 2026: The inflection point is here. May 2026. designerfund.com/blog/ai-in-design-2026
Rachitsky, Lenny. The design process is dead. Here’s what’s replacing it. | Jenny Wen. Lenny’s Newsletter. March 1, 2026. lennysnewsletter.com/p/the-design-process-is-dead
Double Diamond NYC. Jenny Wen – Design Lead at Anthropic. March 17, 2026. doublediamondnyc.substack.com
Yang, Peter. Inside Anthropic: Claude Cowork Tutorial from Claude’s Head of Design. Creator Economy. March 29, 2026. creatoreconomy.so
Roth, Chris. Building An Elite AI Engineering Culture In 2026. February 2026. cjroth.com/blog
Medium / Design Bootcamp. Product Designers Are Not Being Replaced. They Are Being Sorted. March 2026. medium.com/design-bootcamp
OpenAI. Product Designer, ChatGPT — job listing. 2026. builtin.com