The questions in this guide are the ones I've asked, the ones my peers ask, and the ones my candidates have been asked in 2024 to 2026 at retail, fintech, B2B SaaS, public sector and agencies. Every question is followed by the underlying read: what the interviewer is actually testing for, and a practitioner-level answer pattern.
The shape of a UX interview in 2026
Most UX hiring pipelines look like this: a 30-minute intro call, a 60 to 90 minute portfolio walkthrough, a take-home or live design exercise, a cross-functional panel, and an offer conversation. The portfolio walkthrough is where most candidates are filtered. The design exercise is where senior candidates are stretched.
Two changes since 2023 worth knowing. First, design exercises are now standard rather than rare, because hiring managers want to see thinking that wasn't AI-assisted. Second, take-home tasks have shrunk in scope: three-day briefs have largely been replaced with two-hour exercises, because the long-format briefs were drawing candidate complaints and producing inconsistent signal.
Portfolio walkthrough questions
This is the most important section of the interview. Plan to spend 70 percent of your prep time here.
"Walk me through a project you're proud of."
What's being tested: can you tell a coherent story about your own work; do you foreground thinking over screens; do you know what you owned versus contributed to.
How to answer: open with the problem in one line. Outcome in one line. Then the two or three decisions that mattered, with the trade-offs you accepted. Be honest about scope and what you specifically owned. Aim for ten minutes. If asked to go deeper on a section, you should be able to.
"What was the hardest decision in that project?"
What's being tested: can you articulate trade-offs; did you actually make decisions or did you describe the work post-hoc.
How to answer: name a specific decision. Describe the option you didn't pick and why. Don't claim every decision was obvious or that you got everything right. The interviewer is looking for evidence you held both sides of a real trade-off.
"What would you do differently if you could rerun this project?"
What's being tested: self-awareness; whether you've reflected on the work since shipping.
How to answer: name one specific thing and why. Avoid generic answers ("more research time"). The strongest answers name a specific decision you'd reverse and explain what you've learned since that changed your view.
Behavioural questions
"Tell me about a time you disagreed with a stakeholder."
What's being tested: can you hold a position under pressure without being a problem; can you find resolution paths.
How to answer: name the disagreement, your position, the stakeholder's position, and the resolution. Avoid stories where you simply got your way. The strongest answers describe a compromise that respected both sides and a lesson you carried forward.
"Describe a project that didn't go well."
What's being tested: honesty; ability to reflect; resilience.
How to answer: pick a real failure. Don't soften it. Describe what went wrong, what you'd do differently, and what changed in your subsequent work because of it. Interviewers see through manufactured failures ("I worked too hard"); pick something real.
"How do you handle ambiguous briefs?"
What's being tested: can you operate when no one is going to hand you the answer; do you know how to scope your own work.
How to answer: describe how you'd convert ambiguity into a written, agreed scope. Walk through a real example. The strongest answers describe asking specific clarifying questions, writing a one-paragraph scope, and getting sign-off before working.
Design exercises
Two formats: live (60 to 90 minutes, in the interview) and take-home (two to four hours, over a few days). Both test the same things.
What the interviewer is watching for
- Problem framing. Did you spend the first ten minutes clarifying what to design, or did you start drawing immediately?
- Trade-offs named explicitly. Are you saying out loud what you're not doing and why?
- Recovery from a curveball. If they throw in a constraint mid-exercise, can you adapt?
- Communication under time pressure. Can you narrate your thinking without losing the design?
"Redesign this feature for [different audience]"
How to handle it: ask three clarifying questions before doing anything. What's the audience's current relationship with the product? What constraints am I working under? What does success look like? Then state your problem framing out loud. Then sketch. Then narrate.
Systems and craft questions
"How do you decide when to deviate from the design system?"
What's being tested: do you respect systems while having the judgement to know when they're wrong; do you understand the cost of deviation.
How to answer: deviation costs maintenance, consistency and trust. Justified when the system genuinely doesn't fit the case, the new pattern is reusable, and you can get sign-off from the system owner. Not justified to satisfy personal taste.
"How do you make accessible design decisions in 2026?"
What's being tested: do you actually know WCAG; do you treat accessibility as baseline or as an afterthought.
How to answer: WCAG 2.2 AA is the baseline. Reference the new 2.4.13 focus criterion and 2.5.8 target size. Mention the tools you use (a real contrast checker; the UX Companion one, axe, WAVE). Treat accessibility findings as non-negotiable.
"How do you use AI in your work?"
What's being tested: are you a thoughtful AI user; do you distinguish between execution and interpretation use cases.
How to answer: describe specific tools (Figma's AI features, Anthropic Claude or Gemini for synthesis, AI for microcopy drafts), which parts you delegate (drafting, exploring, critiquing), which parts you keep (interpretation, stakeholder work, final decisions). Be honest about your level of fluency.
Senior-only questions
"How do you measure your team's impact?"
What's being tested: can you connect design work to business outcomes; do you know what numbers to point at.
How to answer: combine product metrics (conversion, retention, NPS), team metrics (cycle time, design system adoption), and qualitative signals (stakeholder trust, hiring success). The strongest senior candidates name a specific number they've moved and the design intervention that moved it.
"What's your hiring philosophy?"
What's being tested: can you build a team; what kind of designers do you spot and develop.
How to answer: describe the bar (writing, decision-making, stakeholder management), the diversity you optimise for (background, seniority mix, specialisms), and the development pathway from junior to mid to senior. Most senior candidates underprepare for this question; the ones who answer crisply stand out.
The questions you should ask
Strong candidates spend prep time on the questions they'll ask. Ask things you genuinely want to know that you couldn't find on the website.
- What does the design team's week look like? Surfaces process and rhythm.
- What was the last hard decision the design team made, and how did you make it? Surfaces decision culture.
- Who would I be working most closely with day-to-day? Surfaces team dynamics without being adversarial.
- What would make someone fail in this role in the first six months? Surfaces what they actually care about.
- What does the next hire after this role look like? Surfaces team growth and confirms the role isn't a one-off.
- What's the relationship between design and product here? Surfaces power dynamics.
Negotiation
The salary conversation is part of the interview. Treat it as a calm, written exchange rather than a confrontation.
Five moves that work
- Anchor with a range. "I'm targeting £70-80k for senior product designer roles" is harder to anchor low than a single number.
- Get the offer in writing first. Verbal offers are anchors. The negotiation begins after the formal offer.
- Negotiate total package. Base, bonus, equity, pension, training budget, holiday, remote allowance.
- Cite the market. "Senior roles in this sector range £80 to £95k" is harder to dismiss than "I think I'm worth more". The UK salary guide covers ranges by level.
- Know your walk-away number. The candidate willing to walk negotiates from a stronger position.
Red flags both ways
Red flags from the candidate (interviewer's side)
- Walking through the portfolio without naming any decisions or trade-offs.
- Blaming previous teams or stakeholders for project failures.
- Asking only about benefits and compensation in the candidate's questions slot.
- Inability to explain a specific design choice when asked.
- Inflated outcomes that don't survive a follow-up question.
Red flags from the company (candidate's side)
- Multi-round interviews with no clear feedback between rounds.
- Take-home exercises longer than four hours.
- Vague answers to "what would make someone fail here".
- Salary range that can't be discussed openly.
- Last designer in the role left within six months and nobody will explain why.
Frequently asked questions
What are the most common UX interview questions?
Walk me through a project; tell me about a stakeholder disagreement; how would you redesign X; what's your process; what would you do in the first 90 days; what questions do you have for us. Senior interviews add measurement, trade-offs, and hiring philosophy.
How do I prepare for a portfolio walkthrough?
Pick one case study. Practise out loud, timed, ten minutes max. Open with problem and outcome. Walk through two or three decisions. Be honest about scope. Prepare for follow-ups on constraints and alternatives.
What is a UX design exercise?
A bounded problem given as live (60-90 min) or take-home (2-4 hours). Tests problem framing, decisions, and communication. Don't try to ship; show the thinking.
What questions should I ask in a UX interview?
Team structure, how decisions are made, the last hard decision, the next hire after you, what would make someone fail. Avoid questions answered on the website.
How do I negotiate a UX salary offer?
Anchor with a range. Get the offer in writing first. Negotiate total package. Cite market data. Know your walk-away number. Most offers move 8 to 15 percent on a calm counter.