The Best Interview Questions to Ask a Product Designer
A portfolio walkthrough tells you what a designer shipped. It doesn't tell you how they think, or how they handle being wrong. Here's what closes that gap.
The Candit Team, 2026-08-19
A product designer's portfolio is a highlight reel — polished, final, and stripped of every dead end that happened before the final screen. A portfolio review alone tells you what shipped. It's a weaker signal for how someone actually works: how they arrive at decisions, how they take feedback, and how they behave when the first idea doesn't pan out.
The questions below are built to get past the highlight reel.
What to actually screen for
| Competency | Question | What a strong answer sounds like |
|---|---|---|
| Process and rationale | "Pick one project and walk me through the decision you're least confident was right, in hindsight." | Names something specific and imperfect, not a safe "everything worked out." Shows they can evaluate their own work honestly. |
| Collaboration with eng and PM | "Tell me about a time engineering pushed back on a design for technical reasons. What happened?" | Describes an actual compromise or tradeoff reached together — not "I explained why my design was right and they agreed." |
| Handling critique | "Tell me about feedback on your work that stung, even if it was fair." | Can articulate what the critique actually was and what they did differently afterward — not just "I took it well." |
| Research vs. instinct | "When did you last go against what user research told you, and why?" | A specific, reasoned judgment call — not a blanket claim of always following data, and not a dismissal of research either. |
Why the portfolio walkthrough needs a harder follow-up
Ask "why" one layer deeper than the portfolio deck already answers. If a candidate explains a design decision, ask what the second-best option was and why it lost. If they mention user research, ask what the research actually said versus what they inferred from it. The gap between a design decision and the reasoning that produced it is exactly where portfolio prep runs out and real thinking has to take over.
Watch for how they talk about the team, not just the work
A design portfolio is inherently solo-framed — "I designed X." The interview is where you find out whether that's an accurate reflection of how they actually work with a team, or a narrative gap. Ask directly who else was in the room for a key decision, and what that person contributed. Designers who can name specific contributions from PM, engineering, and research are usually easier to integrate into a real team than ones whose story is entirely "I."
A note on portfolio-heavy interviews and time
Portfolio reviews tend to run long, and long-form conversational answers are the hardest thing to accurately summarize from memory afterward — the exact phrase a candidate used to describe a tradeoff is often the difference between "strong" and "vague" in your notes three days later. Capturing quotes live, not reconstructing them after the fact, matters more here than in almost any other interview type.
Hiring a product designer? Designers are part of the rest of your startup team, which we fill for clients we already work with. Every candidate we put forward has already been through a live interview, and you get an interview pack with what they said and where to push in your round. Book a call.