2026-06-18 · 11 min read
Natalia Veretenyk— UX Academy instructor
UX Design Interview Questions: What to Expect and How to Prepare
A UX design interview is not like most job interviews. There is no standard question sheet, no correct answer for "where do you see yourself in five years", and very little time spent on your CV once you are past the screening stage. Most of the evaluation happens in two places: your portfolio and your ability to walk through design decisions out loud.
If you have never been through a UX hiring process before, the format can catch you off guard. Interviewers are not just checking that you know what a user journey is. They are watching how you think, how you respond to challenge, and whether you can separate your aesthetic preferences from evidence-led decisions. This guide walks through every stage of the process, the questions you are likely to face, and how to answer each one well.
The typical UX interview process in the UK
Most mid-to-large UK employers run a 3-4 stage process. Knowing what to expect at each stage lets you prepare accordingly rather than being reactive.
Stage 1 — Screening call (20-30 minutes)
Usually with a recruiter or a hiring manager. This is a basic fit check: are you available, are your salary expectations in range, can you articulate what you do clearly? Have a two-minute summary of your background ready. Know your notice period and target salary.
Stage 2 — Portfolio review (45-60 minutes)
This is the most important stage of the process. A design manager or lead designer will ask you to walk through one or two projects in detail. The expectation is not a polished presentation — it is a conversation about how you think. We cover the specific questions you will face in this stage below.
Stage 3 — Design challenge or task
Either take-home (typically 2-7 days) or live (30-45 minutes in the room or on a video call). You are given a design prompt and asked to work through it. Interviewers are assessing your structure as much as your output.
Stage 4 — Panel or stakeholder interview
Usually involves more people: a product manager, an engineer, possibly a senior leader. The focus shifts to culture fit, how you collaborate across disciplines, and whether you can hold your own in a room with non-designers.
End-to-end, expect 2-6 weeks for the full process.
Portfolio review questions
The portfolio review is where most interviews are won or lost. Being able to walk through your work clearly and respond well to follow-up questions requires specific preparation. Here are the questions you are most likely to face and what a strong answer looks like.
"Walk me through one of your projects."
What they want: a structured narrative — problem, research, decisions, outcome — not a tour of screens. Start with the problem you were solving and for whom. Then explain what informed your approach. Then walk through a few key decisions. Then tell them what happened.
What to avoid: starting with "So I opened Figma and..." or narrating the visual design without explaining why.
"Why did you make that design decision?"
What they want: evidence or reasoning. A good answer references something — a user research finding, a usability test result, a constraint, a trade-off you consciously made.
What to avoid: "It felt more intuitive" or "it looked better." These answers signal that your design process is aesthetic rather than evidence-led.
"What would you do differently if you did this project again?"
What they want: self-awareness and genuine reflection. This is not a trap — interviewers want to see that you learn from experience and can evaluate your own work critically.
What to avoid: "I wouldn't change anything" (overconfident) or a vague "I'd do more research" (too generic). Be specific about what you learned and what a different approach would have produced.
"How did you validate this design?"
What they want: evidence that you tested or evaluated the design in some form. This could be usability testing, A/B testing, analytics review, expert review, or even guerrilla testing with five users. Any of these is a valid answer.
What to avoid: "Stakeholders liked it" or "the client signed it off." Stakeholder approval is not validation. Interviewers — especially at more mature product organisations — will push back on this.
"What was the biggest challenge on this project?"
What they want: specifics. A real constraint, a genuine conflict, a technical limitation that required a creative solution. This question is a window into how you problem-solve under pressure.
What to avoid: "The timeline was tight" (too generic) or blaming the client without demonstrating how you navigated it. Frame the challenge as something you actively worked through, not something that happened to you.
"What feedback did you get and how did you incorporate it?"
What they want: evidence of iteration. Experienced designers expect design to change in response to feedback. A good answer gives a specific example: what feedback came in, from whom, what you decided to act on and why, and what the design looked like as a result.
Process and knowledge questions
These questions sit alongside the portfolio review and are designed to understand how you work day-to-day, not just on a specific project.
"How do you approach a new design project?"
Describe your process in practical terms: discovery, define, ideate, prototype, test. The key is demonstrating that you start with understanding the problem and the users before moving to solutions. You can reference the UX design process here, but make it personal — describe how you actually work.
"What research methods have you used?"
Be specific. Name the methods: user interviews, surveys, contextual enquiry, card sorting, tree testing, usability testing, diary studies, competitor analysis. If you are earlier in your career, be honest about which methods you have used directly versus observed or studied. See our guide to UX research methods for a full breakdown. Vague answers like "I do research at the start of projects" will not land well.
"How do you work with engineers?"
A question that reveals your maturity as a designer. Strong answers reference: sharing Figma specs and annotating edge cases, joining sprint planning to understand technical constraints early, having direct conversations with engineers during implementation rather than just handing over files and hoping for the best. If you have worked in an agile environment, describe that process specifically.
"How do you handle stakeholder pushback on a design decision?"
What they want: the ability to present rationale with data, not just defend your taste. A good answer describes leading with evidence ("here is what users told us"), offering to test the alternative if there is genuine uncertainty, and being willing to iterate rather than dig in. They are also checking that you are not a pushover who changes designs the moment someone raises an eyebrow.
"Tell me about a time your design did not work as expected."
Use the STAR method: Situation (what was the context?), Task (what were you trying to achieve?), Action (what did you do when things went wrong?), Result (what happened and what did you learn?). Every designer has examples of this. The best answers are honest and demonstrate what changed as a result.
Design challenge questions
Design challenges — whether take-home or live — are used to see how you structure a problem you have never seen before. The prompt varies, but the common formats are:
- "Design an app for X" (e.g. helping elderly people manage medication)
- "How would you improve [specific product]?" (e.g. the TfL Oyster app)
- "How would you approach a redesign of this page?" (usually shown a real screen)
What they are testing:
Can you structure a design problem? Do you start with understanding users and constraints, or do you jump straight to sketching screens? Can you articulate trade-offs out loud? Can you work under time pressure without losing your process?
How to approach it:
- Restate the brief in your own words to confirm you have understood it correctly.
- Ask clarifying questions before you start: Who are the users? What platform is this for? What does success look like? What constraints should I assume?
- Define the core problem before proposing solutions.
- Start with users — who they are, what they need, what their pain points might be — before moving to ideas.
- Show your thinking out loud. Do not go quiet and sketch for ten minutes.
Common mistakes:
- Jumping to UI solutions before defining the problem
- Not asking any questions (makes you look like you take briefs at face value)
- Ignoring constraints (platform, time, technical feasibility)
- Over-polishing the output at the expense of demonstrating your thinking process
Behavioural and culture questions
Later-stage interviews shift toward collaboration, culture fit, and professional maturity. These questions are harder to prepare for without genuine examples.
"What is your proudest design achievement?"
Be specific. Name the project, the problem, the outcome. "Improved checkout conversion by 18% by redesigning the payment flow based on usability testing findings" is a strong answer. "Helped improve the user experience of a complex app" is not.
"Describe a time you disagreed with a product manager."
They want to see professional conflict resolution — not that you always capitulate to keep the peace, and not that you go to war over every decision. A good answer shows that you raised your concern with evidence, you listened to the PM's reasoning, and you reached a decision together (or agreed to test it). Ideally you can describe what happened after the disagreement.
"What excites you about UX design right now?"
They want genuine interest in the field and awareness of where it is heading. Current areas worth mentioning: AI-assisted design and what it changes about the designer's role, the UK Accessibility Regulations and the commercial pressure they create, the convergence of UX and product strategy in smaller teams. Avoid generic answers like "I love solving problems for people" — every candidate says this.
"Why do you want to work here specifically?"
Do your research before the interview. Know their products, their recent launches, their competitors, something about their design team if you can find it. Reference something real and specific. "I use your product daily and noticed that..." or "I read your design team's case study on..." signals that you mean it.
Questions to ask the interviewer
Asking good questions at the end of an interview signals seriousness and design maturity. They also give you genuinely useful information about whether the role is right for you.
- "How does the design team work with product and engineering here? Is design involved from discovery or brought in later?"
- "What does a typical sprint look like for a UX designer on this team?"
- "How is design quality measured in this role — what does a strong first 6 months look like?"
- "What has made other designers successful here? And what has made some not work out?"
Avoid questions that could easily be answered by reading the job description or the company website. And avoid making the first question about salary or benefits if the topic has not come up yet.
A 30-day prep plan
If you have a UX job search starting in the next month, here is a structured approach to interview preparation:
Week 1 — Audit your case studies
Go through every project in your portfolio. For each one, write down: what problem were you solving, what research did you do, what were the two or three most important design decisions and why, what was the outcome. If you cannot answer those in two sentences each, the case study is not ready for a portfolio review.
Week 2 — Practise out loud
Walk through your projects verbally, not just in your head. Record yourself on your phone. Watch it back. You will notice where your explanations trail off, where you say "um" and reach for words, where you are narrating screens instead of explaining decisions. Do this until the narrative feels natural and structured.
Week 3 — Run mock interviews
Pair with a peer, a mentor, or someone from a course or community. Ask them to play the interviewer and use the questions in this guide. The objective is to get comfortable being challenged on your decisions — "why did you do it that way?" — without becoming defensive or flustered.
Week 4 — Research target companies and polish your files
For each company you are actively interviewing with: know their main products, know what they have shipped recently, and have a specific question ready about their design team. Check your Figma files and portfolio for anything that looks unfinished — interviewers sometimes ask to see the actual files, not just the presentation layer.
What comes next
Being prepared for UX interviews is one part of the picture. The other is having the portfolio and the practical experience to back up your answers. If you are building towards your first UX role or making a career change into UX design, the UX Career Track at UX Academy includes mock interview practice, portfolio critique, and interview preparation with instructors who have hired UX designers at companies including Adobe, Google, and Canva.
Next cohort starts 5 September 2026.
For more on the job search side, see our guides to UX design jobs in the UK and UX designer salaries in the UK. If your portfolio needs work before you start applying, start with the UX portfolio guide and the portfolio review checklist.