Where product design is going

Stop hiring for AI fluency

Half of design leaders now put more weight on AI fluency when they hire. The tools those candidates are fluent in more than doubled in number in a single year. We’re testing for the most perishable thing in the room.

AI fluency is a proxy with a shelf life. The durable skill is the ability to specify what good means and then say why the model’s answer missed it.

Fifty percent of design leaders now emphasize AI fluency when they hire, according to AI in Design 2026, a survey of more than 900 designers. Systems thinking and strategic skills come right behind it. I understand the instinct completely and I think the practice is close to useless.

Over the same year, the average designer’s toolstack went from three tools to seven. Ninety-one percent of designers now use AI weekly. A habit that 91% of the field already has, in tools that keep turning over, isn’t a filter. It’s a coin flip wearing a rubric.

What the screen actually selects for

When you screen for AI fluency, the candidate who wins is the one who most recently had time to play.

That correlates with some things you do want, like curiosity. It correlates with some things you should be careful about, like having been between jobs, or having worked somewhere with slack in the schedule, or simply being young enough that nobody at home needed them on a Saturday.

It doesn’t correlate with judgment, and judgment is the entire reason you’re hiring a designer rather than buying a seat.

There’s a version of the screen that works, and it isn’t “which tools do you use”. It is “show me something the model gave you that you threw away, and tell me why”. That question can’t be studied for. It has no right answer available on a podcast. And it goes directly at the thing you actually need to know.

The job got wider, not deeper

Sixty-five percent of designers report taking on more product or engineering responsibility. Forty percent say product managers and engineers now contribute more to design work. Seventy-three percent feel rising expectations for output, quality and speed, all at once.

Read those together and the shape is clear. The boundaries around the discipline dissolved in both directions. Designers are writing production code and specifying systems. Everybody else is making design decisions, because the tools let them and nobody stopped them.

The common read is that this is design losing ground. I think that’s exactly backwards, and it misses what actually got scarce.

When anyone can generate a competent screen, the constraint moves from production to specification. Somebody has to say which of the 40 plausible things is the right one, and say it precisely enough that it holds when they leave the room. That job didn’t exist as a distinct skill when producing the option was itself the hard part. It was bundled inside the craft, invisible, and a lot of people were doing it without a name for it.

It has a name now, because the bundle came apart.

What I screen for instead

Three things, in this order.

Can they write a standard down. I ask for something they have written that another person had to work from: a component spec, a critique doc, a definition of done. Then I read it for whether a stranger could apply it without asking a follow-up question. Most portfolios contain no such artifact, which is itself information.

Can they say why they rejected something. Not what they chose. What they killed, and on what grounds. Katie Dill at Stripe frames the check as asking whether you would be happy with this if it had taken you a week to make. A designer who can’t articulate the rejection is a designer who will approve the model’s first answer.

Can they be specific about what was theirs. Forty percent of designers say they feel full ownership of AI-assisted work and 9% say it’s genuinely difficult to separate their contribution from the model’s. That isn’t a moral failing, it’s a new and confusing condition. But a candidate who can walk me through which decisions were theirs is telling me they were paying attention to their own judgment while they worked. That’s the whole signal.

The thing I would not do

I wouldn’t test tool proficiency in an interview loop. Not because it’s unmeasurable, but because it’s the cheapest thing on the list to teach after someone starts.

Hire someone with judgment and no Cursor experience and they’re productive in two weeks. Hire someone fluent in every tool on the market who can’t tell you why one option is better than another, and you have bought a very fast way to produce work nobody can defend in a review.

Eighty percent of designers still trust their own quality judgment over the model’s, and their most common complaint about AI is unreliable output quality. Only 5% of leaders say they’re placing less emphasis on execution craft. That’s where designers think their value sits, and hiring should catch up to it.

Sources

  1. AI in Design 2026, Designer Fund and Foundation Capital. 900 designers, 60 countries. 91% weekly AI use, toolstack three to seven, 50% of leaders emphasize AI fluency in hiring, 65% taking on more product or engineering work, 73% feel rising expectations.
  2. Craft, the same report: 50% have shipped AI-generated code, 80% still rely on their own quality judgment, 40% feel full ownership of AI-assisted work.