UX designer interview questions — and the CV claims behind them
The portfolio, research and constraint questions UX designers actually get, what each is really probing, and which line on your CV or case study an interviewer will press hardest.
What this interview is actually testing
Whether you can defend a design decision against a constraint you didn't choose — and whether the shipped work in your portfolio shipped in the form you're showing.
The questions, and what each one is really asking
1.Walk me through this case study — what did you actually do?
What it probes: Individual contribution inside team work. Portfolios are collective artefacts and interviewers assume nothing until you say it.
2.What did the research change?
What it probes: Whether research informed the design or validated a decision already made. Both happen; only one is research.
3.Tell me about a design you had to compromise.
What it probes: Whether you can work inside engineering and business constraints without treating them as philistinism.
4.How did you know it worked after launch?
What it probes: Whether you saw the after. Many portfolio pieces end at the high-fidelity mock-up, and interviewers notice.
5.What would you change about it now?
What it probes: Whether you have revisited the work. A designer with no critique of their own case study either did not own it or has stopped growing.
6.How do you handle a stakeholder who redesigns your work in a review?
What it probes: Whether you can convert an opinion into a testable question. 'Make the logo bigger' is usually a real concern badly expressed.
7.Show me something that failed.
What it probes: Increasingly common and rarely prepared for. Portfolios are curated successes, and interviewers want one artefact that was not.
The CV claim they'll press hardest
A design outcome — "increased conversion 25%", "reduced support tickets by half".
Design outcome numbers usually come from a launch in which several things changed at once: a new flow, new copy, a new pricing page and a marketing push. The follow-up is whether the design change was isolated — was there an A/B test, what was the control, was the number measured a week later or a quarter. There is also a quieter risk unique to this discipline: the shipped version frequently differs from the version in the portfolio, because engineering constraints landed after the hand-off. Showing the mock-up and quoting the shipped result is a mismatch a careful interviewer will spot, and it is much better to say which is which yourself.
The UX interview is unusual in that the main artefact — the portfolio — is a collective document being used to assess an individual. Almost every failure in this interview traces back to that mismatch.
Your case study shows a shipped product. That product had a researcher, a product manager, engineers, a design system somebody else built, and probably a previous designer whose work you inherited. The interviewer knows all of this. They also cannot see any of it, which is why the first question is nearly always some version of what did you actually do?
Attribute early and precisely
Candidates worry that itemising their contribution shrinks it. The opposite happens.
“The research was run by our researcher — I sat in on six of eight sessions and did the synthesis. The flow and the interaction design are mine. The visual language is our design system; I contributed the two components that didn’t exist yet.”
That is a designer who knows exactly what they own, delivered without defensiveness. It makes everything else you say more credible, because the interviewer no longer has to discount for unknown attribution.
The alternative — a case study narrated in an unbroken first-person that quietly implies you did all of it — creates a slow problem. The interviewer probes one area, discovers a colleague did it, and then has to mentally re-audit everything you already said.
The shipped-versus-shown gap
There is a risk specific to design portfolios and worth naming: what shipped is often not what you are showing.
Engineering constraints land after hand-off. The elegant empty state got cut. The animation did not survive the performance budget. The flow lost a step because an API could not support it. This is completely normal and reflects badly on nobody.
It becomes a problem when the portfolio shows the intended design and the CV quotes the shipped result. “Increased conversion 25%” attached to a mock-up that was never in front of a user is a mismatch, and a careful interviewer will spot it — usually by asking what the live version looked like.
Get ahead of it in one sentence: “this is the design I handed over; the shipped version lost the inline validation for technical reasons, and the number I quoted is from the shipped version.”
The outcome number
As everywhere, design outcome figures are confounded. A redesign ships alongside new copy, a new pricing page and a campaign. The question is whether the design change was ever isolated: was there a test, what was the control, over what window.
If there was no test — usually there was not — say that. “We shipped the whole thing at once, so I can’t cleanly attribute the lift to the flow change; what I can say is that the support tickets about the third step went to nearly zero, and that step was the thing I changed.” A specific, narrower claim you can defend beats a broad one you cannot.
Preparing
Take your two strongest case studies and, for each, write: who did what, what shipped versus what you are showing, how the result was measured, and what you would change now. Prepare one piece that failed or never shipped.
Our free claim checker flags CV lines likeliest to draw a follow-up; the STAR guide covers the answer shape, though for portfolio walkthroughs the decision matters more than the situation.
Questions about the interview itself
- What questions are asked in a UX designer interview?
- A portfolio walkthrough dominates, usually 45 minutes on one or two case studies, and the questions inside it are about process, contribution and constraint. Expect a whiteboard or take-home exercise at many companies, and behavioural questions about working with engineering and product.
- How do I present a case study when I worked in a team?
- Say who did what, unprompted and early. 'The research was run by our researcher, I sat in on six of the eight sessions; the flow and the interaction design are mine; the visual system was our design system, which I contributed two components to.' Interviewers assume nothing about attribution, and precision here reads as confidence rather than as diminishing your role.
- What if my best work never shipped?
- Show it and say so at the start. Unshipped work is normal — projects get cancelled and priorities move. What damages you is the interviewer discovering it at question three, because from that point they are re-examining everything you said before it rather than looking at the design.