The Product Designer job description is shifting. Here’s what we’re seeing from the hiring side.

Over the past few months, something changed in the Product Designer roles our clients in the U.S. ask us to fill. The titles look the same. The seniority levels look the same. But read the job descriptions carefully and a different shape starts to emerge. It’s not about new tools. It’s about a different kind of designer.

The driver behind the shift has a name people are throwing around a lot: GenUI, or Generative UI. And the conversation around it has been mostly wrong.

What GenUI actually means

GenUI is the idea that parts of a product’s interface get generated in real time by an AI agent, based on what the user is trying to do, instead of being pre-designed screen by screen.

Think of it this way. A traditional Product Designer designs the restaurant menu. A Product Designer working with GenUI designs the kitchen rules so an AI chef can put together the right dish on demand. Same ingredients, same brand, but assembled fresh for each customer.

That’s it. That’s the concept. The interesting part is what it does to the role.

The narrative most people are repeating

The loudest take on LinkedIn goes something like this: “AI is going to replace Product Designers.” It’s the wrong conversation. We’ve placed enough Product Designers in the last year to say with confidence: demand is not dropping. What’s dropping is demand for a specific kind of Product Designer. And what’s rising is demand for another kind. That’s the story worth telling.

What’s actually changing in the hiring side

Four shifts we keep seeing in the briefs we get from U.S. clients:

From designing screens to designing systems. Job descriptions that used to lead with “deliver high-fidelity mockups” now lead with “evolve and govern our design system.” The deliverable changed. Designers are increasingly asked to define the rules, tokens, and components that other people, and increasingly AI agents, will assemble.

Design systems went from nice-to-have to non-negotiable. Two years ago, a strong portfolio of polished screens could land most senior roles. Today, when we ask hiring managers what they care about most, design system experience comes up first or second almost every time. If GenUI assembles interfaces from approved components, the quality of those components becomes the quality of the product.

Systems thinking is now weighted more than pixel craft. Pixel craft still matters. But the candidates moving fastest through interview loops are the ones who can talk about constraints, edge cases, and how a design behaves across thousands of generated variations, not just three Figma frames.

Knowing how AI agents work is no longer optional. This one is newer. Not every job description spells it out, but in interviews, hiring managers consistently ask designers if they’ve worked alongside AI tooling, how they think about guardrails for AI-generated outputs, or whether they’ve used tools like v0 or similar. A year ago, this was a “nice extra.” Now it’s a signal.

What hasn’t changed

It’s worth saying this clearly, because it gets lost in the AI panic: the fundamentals still matter. User research, accessibility, communication with engineering and product, judgment about what’s worth building. None of that is going anywhere. If anything, it matters more, because a designer who can’t reason about user needs has even less to offer when the screen itself becomes generative.

This is not a “throw everything out and learn AI” moment. It’s an “add new layers on top of solid fundamentals” moment.

If you’re a Product Designer reading this

A few practical moves we’d suggest based on what’s getting candidates hired right now:

• Get fluent in design systems. Not just using them, building and governing them.
• Learn the vocabulary of the new specs even at a conceptual level. A2UI, MCP Apps, component catalogs. You don’t need to ship code, but you should be able to talk about them.
• Practice thinking in guardrails instead of layouts. What are the rules an AI should follow when assembling an experience? What should it never do?
• Spend time with tools like v0 or similar. Not to replace your craft, but to develop intuition for how AI generates UI from prompts.

You don’t need to become an engineer. You need to expand the shape of what you call “design work.”

If you’re hiring Product Designers

A few things worth weighing more heavily than you probably are today:

• Ask candidates how they’d design a system, not just a screen. Watch how they handle ambiguity and scale.
• Look for design system depth, even if the role isn’t framed as a systems role.
• Notice how candidates talk about AI. Defensiveness is a flag. Curiosity is a green light.
• Be careful with portfolios that are all polished final screens. Ask to see the messy middle. That’s where the systems thinkers reveal themselves.

The best Product Designer hires we’ve made in the last year would have been considered “too systems-focused” or “not visual enough” by hiring rubrics from 2023. Those rubrics need an update.

Where this leaves us

Product Designers are not in danger. But the job is changing, and faster than most job descriptions admit. The designers who lean into systems and rules, instead of pantries and flows, will have a lot more to offer in the next two years. And the companies that adjust their hiring lens early will get the better people, before everyone else catches up.

We see this from the hiring side every week. The shift is not coming. It’s already happening, quietly, one job description at a time.