Tell me about yourself.

Used to filter for narrative thinking, a core design skill. Strong answers run 90 seconds: current role and product context, one shipped project where research and design choices changed an outcome, why you are interviewing now. Weak answers list every tool (Figma, Sketch, Miro, Maze) without context. The kill-shot mistake is opening with educational background unless you graduated within the last two years. Tools and degrees are commodities; the impact of your work is what hires you. In my placements, UX designers who land senior roles always anchor on outcomes (lifted task completion by 27 percent, cut support tickets by 40 percent, validated the pivot away from feature X). Time it. Two minutes maximum.

Why UX, and why this team?

Motivation filter. Panels want to filter out designers who drifted in from graphic design, marketing or front-end without articulating why. Strong answers describe a deliberate path: the moment you realised research could change a product decision, the satisfaction of working at the intersection of users and business, what specifically draws you to this team. They reference the team's product, a published case study, or a designer they want to learn from. Weak answers say "I love solving problems" with no context. The kill-shot mistake is talking only about visual design when applying for a UX role. UK panels increasingly distinguish UX from UI; show you understand the difference.

Walk me through a project from your portfolio.

The most important round, scored on judgement as much as craft. Strong answers cover: the business and user problem, the research you did, the constraints you worked within, the design choices and the alternatives you rejected (and why), how you collaborated with engineering and product, the launch, and the measured outcome. Weak answers focus only on the visual artefacts. The kill-shot mistake is presenting the final designs as inevitable. Senior panels want to see the wrong turns, the cuts, the trade-offs. Pick a project where you can talk about a difficult decision. Polished case studies that hide the mess sound junior. Show the working.

How do you decide what to research and how?

Research depth round. Strong answers describe matching method to question: generative research (interviews, contextual inquiry, diary studies) for understanding problems, evaluative research (usability testing, A/B tests, surveys) for validating solutions. They mention sample sizes appropriate to the question, mixing qualitative and quantitative, and the reality of constraints (time, recruitment, budget). Weak answers list methods without judgement. The kill-shot mistake is suggesting heavy research for every project regardless of context. Senior designers in the UK know how to do meaningful research in a week as well as in a quarter. Show you understand the trade-offs and can defend a lighter-touch approach when appropriate.

How do you handle stakeholders who want a specific solution rather than a problem solved?

Stakeholder maturity round. Strong answers describe a method: ask why, reframe the conversation around the underlying user problem, bring data or research to broaden options, propose a small experiment to test the original idea fairly. They give a concrete example. Weak answers describe either capitulating or fighting. The kill-shot mistake is portraying stakeholders as obstacles. UK design teams that work well treat product managers and engineering leads as partners. Show that you can hold a research-led position without making it a battle. The designers who get promoted always have a story about reframing a brief and bringing the stakeholder along with them.

Tell me about a design decision you got wrong.

Self-awareness round, scored heavily. The panel wants a real story: a flow that confused users, a pattern that did not scale, an accessibility miss caught after launch. Strong answers own the decision, describe how you discovered the problem (analytics, support tickets, a user test post-launch), explain the fix and what changed in your process. Weak answers describe a near-miss caught in design review. The kill-shot mistake is claiming you have never made a design mistake. Every working designer has shipped flawed work; pretending otherwise reads as inexperience or denial. The recovery story is what hires you. Pick a real one and own it.

Tell me about a time you disagreed with a developer or product manager.

Collaboration round. Strong answers describe a specific disagreement (a flow being cut for engineering effort, a pattern being changed for technical reasons, a research finding being dismissed) and how you reached resolution: bringing data, prototyping the alternative, finding a middle ground, sometimes changing your mind. Weak answers cast the other side as wrong. The kill-shot mistake is escalating without trying to influence first. UK designers get hired on their ability to hold a position respectfully while staying flexible. Pick a story where the resolution improved the outcome and the relationship. That is the answer panels are scoring for.

How do you approach accessibility in your designs?

Increasingly central round. Strong answers describe accessibility as part of the craft, not a checklist at the end: designing with assistive technology in mind from the start, contrast and hierarchy choices, keyboard navigation, screen reader semantics, working with developers on implementation, testing with real assistive tech and ideally with disabled users. They reference WCAG levels and explain trade-offs. Weak answers say "I follow WCAG" without examples. The kill-shot mistake is treating accessibility as someone else's responsibility. UK government, financial services and increasingly all sectors take this seriously. Show you treat accessibility as a design discipline, not a compliance task.

Loyalty and research filter. Strong answers reference the company's product, its design culture or maturity, the specific user problems the team is solving, public design output (case studies, conference talks), or a designer you want to work with. They tie it to your career arc. Weak answers list the salary or the brand. The kill-shot mistake is showing you have not used the product. For consumer products especially, panels expect you to have signed up, used it, formed opinions and brought screenshots of moments that intrigued you. I lose offers every quarter for designers who interview at consumer brands without ever opening the app. Twenty minutes prevents it.

How do you measure the impact of your design work?

Commercial awareness round, scored more heavily than it used to be. Strong answers describe matching metrics to outcomes: task completion, time on task, error rates, support contact, conversion, retention, NPS or CSAT. They acknowledge that design impact is sometimes hard to isolate and describe how they design experiments to attribute it. Weak answers say "I do not measure my work, that is the PM's job". The kill-shot mistake is treating measurement as outside your craft. Senior UX designers in the UK get hired on the ability to talk about outcomes, not just artefacts. Have one project ready with measured impact. Specifics get hired.

Where do you see yourself in three years?

Trajectory round. Strong answers describe a direction (deeper craft in a specialism like research or systems design, broader scope, lead or principal path, optionally design management) without naming a specific title at a specific company. They acknowledge wanting to grow with the right team. Weak answers say "I want to be Head of Design" within two years (unrealistic in most teams) or "I have not thought about it". The kill-shot mistake is describing a trajectory the company cannot offer. If they have a flat design team, do not pitch climbing a ladder. Mirror the team's shape and stage. Hiring managers want designers who will grow with them for at least two years.

Do you have any questions for us?

Easiest round to score well on, most often wasted. Strong candidates ask two or three sharp questions: how is design embedded in product development, what is the team's research practice today, how is design success measured, who is the most senior designer on the team. They listen and follow up. Weak candidates stay silent or ask about hours and holiday. The kill-shot mistake is asking what the company does (you should know already) or repeating a question already answered. Prepare six questions in advance, pick the best two or three based on the conversation. Silence here loses offers regularly. It is the cheapest preparation in the entire interview.

Interview Q's · Tech · UK 2026

UX Designer Interview Questions UK

UX designer interviews in the UK have become more substantive since the design layoffs of 2023 settled. Panels in 2026 are sceptical of polished portfolios and want to see judgement, research depth and commercial awareness. I have placed UX designers into UK SaaS, e-commerce, financial services and government digital teams for over a decade, and the rounds you should expect are a portfolio walkthrough, a design exercise or critique, behavioural and culture-fit conversations. The questions below cover what comes up most often. I have written each answer from the panel's side so you understand what they are scoring, what a strong response sounds like and the mistakes that kill design offers most reliably.

By Alex · 12-year UK recruiter · 12 questions + recruiter answers

Question 1

Tell me about yourself.

Used to filter for narrative thinking, a core design skill. Strong answers run 90 seconds: current role and product context, one shipped project where research and design choices changed an outcome, why you are interviewing now. Weak answers list every tool (Figma, Sketch, Miro, Maze) without context. The kill-shot mistake is opening with educational background unless you graduated within the last two years. Tools and degrees are commodities; the impact of your work is what hires you. In my placements, UX designers who land senior roles always anchor on outcomes (lifted task completion by 27 percent, cut support tickets by 40 percent, validated the pivot away from feature X). Time it. Two minutes maximum.
Question 2

Why UX, and why this team?

Motivation filter. Panels want to filter out designers who drifted in from graphic design, marketing or front-end without articulating why. Strong answers describe a deliberate path: the moment you realised research could change a product decision, the satisfaction of working at the intersection of users and business, what specifically draws you to this team. They reference the team's product, a published case study, or a designer they want to learn from. Weak answers say "I love solving problems" with no context. The kill-shot mistake is talking only about visual design when applying for a UX role. UK panels increasingly distinguish UX from UI; show you understand the difference.
Question 3

Walk me through a project from your portfolio.

The most important round, scored on judgement as much as craft. Strong answers cover: the business and user problem, the research you did, the constraints you worked within, the design choices and the alternatives you rejected (and why), how you collaborated with engineering and product, the launch, and the measured outcome. Weak answers focus only on the visual artefacts. The kill-shot mistake is presenting the final designs as inevitable. Senior panels want to see the wrong turns, the cuts, the trade-offs. Pick a project where you can talk about a difficult decision. Polished case studies that hide the mess sound junior. Show the working.
Question 4

How do you decide what to research and how?

Research depth round. Strong answers describe matching method to question: generative research (interviews, contextual inquiry, diary studies) for understanding problems, evaluative research (usability testing, A/B tests, surveys) for validating solutions. They mention sample sizes appropriate to the question, mixing qualitative and quantitative, and the reality of constraints (time, recruitment, budget). Weak answers list methods without judgement. The kill-shot mistake is suggesting heavy research for every project regardless of context. Senior designers in the UK know how to do meaningful research in a week as well as in a quarter. Show you understand the trade-offs and can defend a lighter-touch approach when appropriate.
Question 5

How do you handle stakeholders who want a specific solution rather than a problem solved?

Stakeholder maturity round. Strong answers describe a method: ask why, reframe the conversation around the underlying user problem, bring data or research to broaden options, propose a small experiment to test the original idea fairly. They give a concrete example. Weak answers describe either capitulating or fighting. The kill-shot mistake is portraying stakeholders as obstacles. UK design teams that work well treat product managers and engineering leads as partners. Show that you can hold a research-led position without making it a battle. The designers who get promoted always have a story about reframing a brief and bringing the stakeholder along with them.
Question 6

Tell me about a design decision you got wrong.

Self-awareness round, scored heavily. The panel wants a real story: a flow that confused users, a pattern that did not scale, an accessibility miss caught after launch. Strong answers own the decision, describe how you discovered the problem (analytics, support tickets, a user test post-launch), explain the fix and what changed in your process. Weak answers describe a near-miss caught in design review. The kill-shot mistake is claiming you have never made a design mistake. Every working designer has shipped flawed work; pretending otherwise reads as inexperience or denial. The recovery story is what hires you. Pick a real one and own it.
Question 7

Tell me about a time you disagreed with a developer or product manager.

Collaboration round. Strong answers describe a specific disagreement (a flow being cut for engineering effort, a pattern being changed for technical reasons, a research finding being dismissed) and how you reached resolution: bringing data, prototyping the alternative, finding a middle ground, sometimes changing your mind. Weak answers cast the other side as wrong. The kill-shot mistake is escalating without trying to influence first. UK designers get hired on their ability to hold a position respectfully while staying flexible. Pick a story where the resolution improved the outcome and the relationship. That is the answer panels are scoring for.
Question 8

How do you approach accessibility in your designs?

Increasingly central round. Strong answers describe accessibility as part of the craft, not a checklist at the end: designing with assistive technology in mind from the start, contrast and hierarchy choices, keyboard navigation, screen reader semantics, working with developers on implementation, testing with real assistive tech and ideally with disabled users. They reference WCAG levels and explain trade-offs. Weak answers say "I follow WCAG" without examples. The kill-shot mistake is treating accessibility as someone else's responsibility. UK government, financial services and increasingly all sectors take this seriously. Show you treat accessibility as a design discipline, not a compliance task.
Question 9

Why our company?

Loyalty and research filter. Strong answers reference the company's product, its design culture or maturity, the specific user problems the team is solving, public design output (case studies, conference talks), or a designer you want to work with. They tie it to your career arc. Weak answers list the salary or the brand. The kill-shot mistake is showing you have not used the product. For consumer products especially, panels expect you to have signed up, used it, formed opinions and brought screenshots of moments that intrigued you. I lose offers every quarter for designers who interview at consumer brands without ever opening the app. Twenty minutes prevents it.
Question 10

How do you measure the impact of your design work?

Commercial awareness round, scored more heavily than it used to be. Strong answers describe matching metrics to outcomes: task completion, time on task, error rates, support contact, conversion, retention, NPS or CSAT. They acknowledge that design impact is sometimes hard to isolate and describe how they design experiments to attribute it. Weak answers say "I do not measure my work, that is the PM's job". The kill-shot mistake is treating measurement as outside your craft. Senior UX designers in the UK get hired on the ability to talk about outcomes, not just artefacts. Have one project ready with measured impact. Specifics get hired.
Question 11

Where do you see yourself in three years?

Trajectory round. Strong answers describe a direction (deeper craft in a specialism like research or systems design, broader scope, lead or principal path, optionally design management) without naming a specific title at a specific company. They acknowledge wanting to grow with the right team. Weak answers say "I want to be Head of Design" within two years (unrealistic in most teams) or "I have not thought about it". The kill-shot mistake is describing a trajectory the company cannot offer. If they have a flat design team, do not pitch climbing a ladder. Mirror the team's shape and stage. Hiring managers want designers who will grow with them for at least two years.
Question 12

Do you have any questions for us?

Easiest round to score well on, most often wasted. Strong candidates ask two or three sharp questions: how is design embedded in product development, what is the team's research practice today, how is design success measured, who is the most senior designer on the team. They listen and follow up. Weak candidates stay silent or ask about hours and holiday. The kill-shot mistake is asking what the company does (you should know already) or repeating a question already answered. Prepare six questions in advance, pick the best two or three based on the conversation. Silence here loses offers regularly. It is the cheapest preparation in the entire interview.

How to use these answers

Use these answers to understand the panel's perspective, then build your own examples using the STAR method (Situation, Task, Action, Result). For UX specifically, every project answer should include four things: the user problem, the research, the design choice and the measured outcome. If a story is missing any of those, it is not interview-ready. Write four or five projects in a notebook and walk through each one out loud before the round. The mistake I see kill the most UX designer offers is presenting work as a finished aesthetic without the messy decision-making behind it. Senior panels want to see the cuts, the alternatives you rejected and what you would do differently. Show the working, not just the artefact.