UX interview questions and how to answer them

Most UX interviews do not fail because candidates lack taste. They fail because answers stay vague: no users, no constraints, no trade-offs, no outcomes. This guide collects the questions UK and international hiring teams ask repeatedly, and shows how to answer them with clarity rather than performance theatre.

How to use this list

Do not memorise scripts. Practise a structure. For behavioural questions, use Situation → Decision → Action → Evidence → Learning. For portfolio questions, anchor every claim in a real artefact. For design challenges, narrate trade-offs out loud so the interviewer can see how you think. Then run a timed mock with structured feedback.

Portfolio and process questions

• Walk me through a project you are proud of.
• What was your exact role versus the wider team?
• Where did the brief come from, and how did it change?
• How did you decide what research to do first?
• What did you choose not to design, and why?
• Show me an insight that changed the direction of the work.
• How did you validate the solution before launch?
• What would you redo with another fortnight?
• How did success get measured?
• Which stakeholder was hardest to align, and how did you handle it?

Strong answers name constraints early: time, policy, legacy systems, accessibility, procurement, or organisational risk. In UK public-sector contexts especially, interviewers listen for awareness of GOV.UK patterns, service standards, and evidence trails — not just polished screens. See also our portfolio walkthrough guide.

Behavioural questions

• Tell me about a time research contradicted a stakeholder belief.
• Describe a disagreement with a product manager.
• How do you handle incomplete requirements?
• Give an example of prioritising ruthlessly under a deadline.
• When have you influenced without authority?
• Tell me about feedback that stung — and what you changed.
• How do you communicate uncertainty to leadership?
• Describe a time accessibility reshaped a design decision.
• How do you onboard to a messy codebase or design system?
• Tell me about mentoring a more junior designer.

Keep stories short and specific. Name the friction, the decision you took, and what improved. Avoid villain narratives about “difficult stakeholders”; demonstrate systems awareness and collaborative craft.

Technical and craft questions

• How do you approach information architecture for a complex domain?
• Talk me through a usability test plan in one minute.
• When do you use generative versus evaluative research?
• How do you write hypotheses for experiment design?
• What makes a prototype “good enough”?
• How do you balance brand expression with usability?
• Walk through how you hand work to engineering.
• How do you audit a journey for accessibility risks?
• When is a design system a help, and when is it a constraint?
• How do you decide whether to run a workshop?

Design challenge prompts you may meet

• Redesign onboarding for a busy first-time user.
• Improve form completion for a high-stakes application.
• Map a service journey with multiple organisations involved.
• Design an empty state that reduces support tickets.
• Prioritise a backlog when everything is marked “urgent”.
• Critique this screen live and propose two improvements.
• Facilitate alignment when legal, ops, and product disagree.
• Define metrics for a vague goal like “delight”.
• Propose research when you have three days and no budget.
• Explain your decision using risk and evidence, not preference.

In timed challenges, spend the first minutes framing the problem. State assumptions, users, and success criteria before jumping into Figma. Then present options at different fidelity: flow, key screens, open questions.

Culture and collaboration questions

• How do you prepare for a design critique?
• What does “good” documentation look like for you?
• How do you work with content designers and researchers?
• Describe your relationship with analytics.
• How do you keep quality high when shipping in increments?
• What rituals help a squad stay user-centred?
• How do you handle ethical concerns in a product decision?
• Tell me about collaboration across time zones or contractors.
• How do you stay current without chasing every trend?
• Why this company, and why this role now?

Answer quality checklist

Before interview day, practise until you can answer without filler. Check that each story includes a user, a constraint, a decision, evidence, and a consequence. If any of those five are missing, strengthen the answer. Then practise out loud — fluency under pressure matters as much as the content.

When you are ready, run a timed mock with structured feedback rather than polite encouragement. Honest revision beats rehearsed positivity every time.