How to hire a product designer

The thing most interviews accidentally measure

A typical design interview is a portfolio walkthrough plus a conversation. Both reward presentation — a designer who narrates their work well outperforms one who does the work well, consistently.

This is not a small effect. Presentation skill and design judgment are only loosely correlated, and the mismatch is worst at senior level, where the calmest presenter is often the one who has been shielded from hard decisions.

1. Do they separate the problem from the request?

Requests arrive as solutions. 'We need onboarding tooltips.' 'Add a dashboard.' 'Make it more modern.' The single highest-value behaviour in a product designer is asking what outcome the request is meant to produce, before doing any of it.

To observe it, give them a brief that already contains its answer, with data attached that points somewhere else. A junior designs the tooltips. A senior asks what number is supposed to move, and notices the data does not support the request.

2. What do they ask before designing?

Ask for the five questions they would ask, and who they would ask them of. This is the fastest read on seniority available in any format, and it takes ten minutes.

Weak answers are generic and interchangeable — who are the users, what are the business goals, what is the timeline. Strong answers are specific to the situation, directed at named people, and at least one of them is uncomfortable to ask.

3. What do they cut when resources vanish?

Halve the time available, mid-conversation, and watch what goes.

Junior designers cut polish: animations, empty states, visual refinement. Senior designers cut scope — they remove whole use cases, name what they are sacrificing out loud, and protect one flow end-to-end so the result is still measurable.

The verbal part matters as much as the choice. A designer who cuts silently is going to surprise you later.

4. What happens when the plan breaks?

This is what portfolios structurally cannot show, because case studies are written after the outcome is known and every abandoned path has been tidied away.

Rule out their most obvious solution and see whether there is a second gear. Then put a stakeholder in front of them who has decided the answer and will not move, and ask them to write the reply. There are two ways to fail — capitulate, or dig in — and one way to do it well: reframe towards the other person's actual goal and propose a cheap way to settle it with evidence.

5. Can they find the weak point in their own work?

Ask what is weakest about what they just proposed and how they would check it.

Strong designers name something real and specific, usually an assumption they have not tested. Weak ones produce the textbook answer — 'we would need to validate with users' — which is true of everything and therefore says nothing.

Follow it with: which single number would you move, and by how much? A designer who names one metric with a magnitude is thinking about outcomes. One who lists six is describing a dashboard.

What to do with visual craft

Do not ignore it — but assess it separately and cheaply. Fifteen minutes on their real work tells you whether the craft floor is met. It is the easiest attribute to verify and the one least likely to be the reason a hire fails.

Hires fail because someone builds the wrong thing well, not because the spacing was off.

Frequently asked

Do you still need to look at a portfolio?

Yes, for about fifteen minutes, to confirm the craft floor is met. What it cannot show you is the reasoning: a case study is written after the outcome is known, with every abandoned path tidied away. Use it to rule people out on craft, never to rule them in on judgment.

How do you tell a senior product designer from a mid-level one?

By what happens when the plan breaks, not by years on the CV. Rule out their most obvious solution and see whether there is a second gear. Seniority shows up as scope decisions made out loud — what is being sacrificed and why — rather than as a longer résumé or a better-narrated portfolio.

Can you evaluate a product designer if nobody on the panel is a designer?

Yes, and it is the normal situation for a first design hire. Craft is the one part you cannot judge, so buy fifteen minutes of an external designer's time for it. Everything else — whether they question the brief, what they ask first, what they cut, whether they can name the weak point in their own proposal — is legible to anyone who has shipped a product.

How much of your team's time should this take?

Under three hours per candidate, interview included. Most processes spend it in the wrong place: hours on portfolio walkthroughs, which reward presentation, and minutes on decisions under changed constraints, which is where seniority actually shows.