UX/UI designer interview questions — why "walk me through your process" is the whole interview
Portfolio reviews look like a presentation, but they're graded like an interview. Here's what's actually being scored while you're clicking through your own case study, and where most designers lose points without noticing.
Most design interviews center on a portfolio walkthrough, which makes them feel more like a presentation than an interrogation. That's exactly why they're easy to under-prepare for — the format feels comfortable, so candidates rehearse the story of the outcome and skip rehearsing the story of the reasoning, which is what's actually being scored.
"Walk me through this project."
What most candidates do: start at the final screens and explain what the design does.
What's actually being scored: whether the story starts at the problem, not the solution. A strong walkthrough opens with what was broken or missing for the user before any screens existed, and only then moves into what was tried. Starting at the finished UI signals that the process might have started there too — jumping to visuals before understanding the problem is one of the most common things interviewers are specifically screening for.
"Why this solution and not something simpler?"
What most candidates do: defend the final design as the obviously correct choice.
What's actually being scored: whether you can honestly describe an alternative you considered and rejected, and why. A designer who can only describe the path they took, with no visible awareness of the paths not taken, reads as someone who arrived at the design by instinct rather than by evaluating options — which is a harder skill to trust on a team where design decisions need to be explained to engineering and product.
"How did you know this design actually worked?"
What most candidates do: describe positive feedback from stakeholders or a general sense that users liked it.
What's actually being scored: whether there's a real signal behind "it worked" — a usability test that surfaced a specific friction point and how the design changed in response, a metric that moved, a support ticket category that dropped. "Stakeholders were happy" is not evidence the user problem was solved; interviewers listen specifically for the gap between those two things.
"Tell me about feedback you disagreed with."
What most candidates do: describe pushing back and ultimately being right.
What's actually being scored: whether the feedback-giver's reasoning gets described fairly, even in a story where you disagreed with the conclusion. A designer who frames every disagreement as "I was right and they were wrong" signals friction risk on a team where design has to collaborate with product and engineering constantly, not work in isolation.
"What would you do differently if you redid this project today?"
What most candidates do: name a small polish item — a color, a spacing choice.
What's actually being scored: whether you can identify a real process gap, not a cosmetic one. The strongest answers name something structural — a user segment that wasn't tested, an assumption that went unchallenged, a constraint that wasn't surfaced early enough — which shows the kind of self-awareness that improves the next project, not just the next screen.
The thread through all five
Every one of these questions is really asking the same thing from a different angle: can you narrate your own thinking honestly, including the parts that didn't work or that you're still unsure about. A portfolio shows the output. The interview exists specifically to check whether the reasoning behind it is real — and that's the part rehearsal usually skips.
Prepair asks design-role questions scoped to your level and scores whether your reasoning held up under a follow-up, the same way a real portfolio review does. Try a free interview — 3 a month, no signup required to start.