How to hire a product designer
By Sergio Gualda · 9 min read · Updated
Hiring a product designer well comes down to assessing decisions rather than screens: whether they reframe a badly posed brief, what they ask before designing, what they cut when resources disappear, how they respond when a constraint changes, and whether they can name the weakest part of their own proposal. Visual craft is necessary, but it's the easiest thing to verify and the least predictive of seniority.
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 consistently outperforms one who does the work well.
The effect is large. 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 most valuable habit 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 doesn't support the request.
2. What do they ask before designing?
Ask for the five questions they'd ask, and who they'd ask them of. It's 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's 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're sacrificing out loud, and protect one flow end to end so the result is still measurable.
Saying it out loud matters as much as the choice. A designer who cuts silently is going to surprise you later.
4. What happens when the plan breaks?
Portfolios structurally can't show this, 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's a second gear. Then put a stakeholder in front of them who has decided the answer and won't move, and ask them to write the reply.
They can fail by capitulating or by digging in. Doing it well means reframing towards the other person's actual goal and proposing a cheap way to settle it with evidence.
5. Can they find the weak point in their own work?
Ask what's weakest about what they just proposed and how they'd check it.
Strong designers name something concrete, usually an assumption they haven't tested. Weak ones give the textbook answer, 'we would need to validate with users', which is true of everything and so 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
Assess it separately and cheaply. Fifteen minutes on their real work tells you whether the craft floor is met. It's 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. Off spacing rarely sinks anyone.
Frequently asked
- Do you still need to look at a portfolio?
- Yes, for about fifteen minutes, to confirm the craft floor is met. It can't show you 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. Years on the CV tell you little. Rule out their most obvious solution and see whether there's a second gear. Seniority shows up as scope decisions made out loud, with what's being sacrificed and why, more 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's the normal situation for a first design hire. Craft is the one part you can't judge, so buy fifteen minutes of an external designer's time for it. Everything else is legible to anyone who has shipped a product: whether they question the brief, what they ask first, what they cut, whether they can name the weak point in their own proposal.
- 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 shows.