Skip to content
Resume Studioby M2Toolkit

9 role-specific questions

UI/UX Designer Interview Questions & Answers

Design interviews centre on your process and your portfolio: how you understand problems, research with users, test and iterate, design accessibly, collaborate with engineers, and measure whether a design worked.

Free, no sign-up. 54 questions in this role's practice pool, including behavioural, HR and situational questions.

UI/UX design interview questions

Design process, research, usability testing, accessibility, design systems and portfolio questions.

  1. 1.

    Walk me through your design process.

    BeginnerRole knowledge

    What the interviewer is evaluating

    Whether you follow a user-centred process and adapt it to constraints.

    Key points a strong answer covers

    • Understand the problem. Start by understanding the problem, goals and constraints.
    • Research. Research users and existing data.
    • Ideate & prototype. Explore options, wireframe and prototype.
    • Test. Test with users and iterate.
    • Deliver & measure. Hand off, ship and measure outcomes.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Describing a rigid textbook process you don't really follow.
    • No mention of measuring results.

    Likely follow-up questions

    • How does your process change with a tight deadline?
    • Tell me about a time research changed your design direction.
    Example strong answer

    It depends on the project's size, but the shape is consistent. First I make sure I understand the problem: the business goal, who the users are, the constraints, and how we'll measure success. Then research — existing analytics and support tickets, a few user interviews, and a look at how others solve it. I explore several directions with sketches and low-fidelity wireframes before committing, then build a prototype and test it with five or so users, iterating on what confuses them. I work closely with engineers during handoff — design tokens, states, edge cases — and after launch I check the metrics we agreed on. Under a tight deadline I compress research, but I never skip testing entirely.

    Practise this question and get feedback
  2. 2.

    How do you plan and run a usability test?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Practical research skills.

    Key points a strong answer covers

    • Goals & tasks. Define what you want to learn and realistic tasks.
    • Participants. Recruit representative participants (often ~5 per round).
    • Neutral moderation. Ask them to think aloud; avoid leading questions.
    • Measure. Record task success, errors, time, and observations.
    • Synthesis & action. Synthesise findings by severity and turn them into changes.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Asking users whether they 'like' the design.
    • Leading questions like 'Was that easy?'

    Likely follow-up questions

    • Moderated or unmoderated — when would you choose each?
    • How do you handle stakeholders who disagree with the findings?
    Example strong answer

    I start with the research questions — for a checkout redesign, 'can people apply a discount code and change delivery without help?' — and turn them into realistic tasks with a scenario, not instructions that give away the answer. I recruit five or six participants who match the target users with a short screener. In the session I ask them to think aloud, stay neutral, and avoid helping or asking leading questions like 'was that easy?'. I note task success, errors, time and where they hesitated. Afterwards I cluster observations, rate issues by severity and frequency, and share a short readout with clips, so the team sees the problems directly, along with recommended changes.

    Practise this question and get feedback
  3. 3.

    How do you design for accessibility?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Inclusive design as standard practice.

    Key points a strong answer covers

    • Contrast & colour. Sufficient contrast and never colour alone to convey meaning.
    • Keyboard & focus. Visible focus states and logical keyboard order.
    • Text & touch targets. Readable, resizable text and large touch targets.
    • Screen readers & content. Labels, alt text, heading structure — annotated for developers.
    • Standards & testing. Follow WCAG and test with assistive technology users.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Treating accessibility as a final check.
    • Relying on colour alone for errors.

    Likely follow-up questions

    • How would you design an accessible error state on a form?
    • How do you get accessibility prioritised on a busy team?
    Example strong answer

    I build it in from the start rather than checking at the end. Text and essential UI meet WCAG contrast — 4.5:1 for body text — and I never use colour alone: errors have an icon and a message too. I design visible focus states and a logical order, and annotate keyboard behaviour for complex components like menus. Text must work at 200% zoom, touch targets are at least around 44 pixels, and motion respects reduced-motion settings. In handoff I annotate headings, labels, alt text and what screen readers should announce. Our design system bakes most of this into components, and I test with screen readers and, when possible, with disabled users.

    Practise this question and get feedback
  4. 4.

    What is a design system, and how would you build or maintain one?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Systems thinking and collaboration with engineering.

    Key points a strong answer covers

    • What it is. Reusable components, tokens, patterns and guidelines — documented.
    • Tokens. Design tokens for colour, type and spacing shared with code.
    • Engineering partnership. Built with engineers so design and code stay in sync.
    • Governance & adoption. Contribution, versioning and adoption processes.
    • Value. Consistency, speed and built-in accessibility.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Describing it as just a UI kit in Figma.
    • No plan for keeping design and code aligned.

    Likely follow-up questions

    • How do you decide whether something becomes a new component?
    • How do you measure a design system's success?
    Example strong answer

    A design system is the shared language of a product: design tokens for colour, typography and spacing; reusable components with their states and variants; patterns for things like forms and empty states; and guidelines on when to use what — kept in sync between Figma and code. I'd start with an audit of what already exists and the inconsistencies, define tokens, then build the most-used components with engineers so the Figma library and the coded components — documented in something like Storybook — match. Governance matters as much as the components: a clear way to propose additions, versioning and deprecation. Success shows in adoption, faster delivery and fewer accessibility bugs.

    Practise this question and get feedback
  5. 5.

    How do you measure whether a design is successful?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Outcome orientation: whether you judge design by its effect, not by approval.

    Key points a strong answer covers

    • Define success upfront. Agree success criteria before designing.
    • Behavioural metrics. Behavioural metrics: conversion, completion, drop-off, errors.
    • Attitudinal metrics. Attitudinal metrics: SUS, CSAT, feedback.
    • Experiments. A/B tests where traffic allows.
    • Qualitative too. Combine numbers with qualitative insight.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Judging success by stakeholder approval alone.
    • Picking metrics after launch.

    Likely follow-up questions

    • What if the metric improved but users complain?
    • How do you measure a design with too little traffic for A/B testing?
    Example strong answer

    I agree what success means before designing, ideally as a hypothesis: 'if we simplify the sign-up form, completion will rise from 40% to 50% without hurting lead quality'. Then I use behavioural metrics — completion and conversion rates, where people drop off in the funnel, error rates, support tickets about the flow — and attitudinal ones like a System Usability Scale score or CSAT. Where there's enough traffic I A/B test; where there isn't, I compare before and after and run usability tests on the new version. I always pair numbers with qualitative insight from session recordings or interviews, because metrics tell you what changed, not why.

    Practise this question and get feedback
  6. 6.

    How do you handle critical feedback on your designs?

    BeginnerBehavioural

    What the interviewer is evaluating

    Collaboration and ego management.

    Key points a strong answer covers

    • Listen & understand. Listen and ask questions to understand the concern.
    • Separate taste from evidence. Bring it back to goals and evidence rather than taste.
    • Example. A real example.
    • Outcome. What changed as a result.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Getting defensive.
    • Accepting every opinion without questioning it.

    Likely follow-up questions

    • What do you do when a senior stakeholder insists on a design you believe is wrong?
    • How do you run a design critique?
    Example strong answer (a fictional story — use your own)

    I see feedback as part of the job, so I try to understand it before reacting — asking what problem they're seeing, because a request like 'make the button bigger' usually hides a real concern, such as people missing the main action. Then I bring the discussion back to the goals and evidence rather than taste. For example, on an onboarding redesign our head of sales felt the new flow hid pricing. Instead of debating, I ran a quick five-user test of both versions; people did look for pricing earlier than I'd assumed, so I added a pricing summary to step one. Completion stayed the same and sales calls about pricing dropped. I learned to test disagreements quickly rather than argue them.

    Practise this question and get feedback
  7. 7.

    Which research methods do you use, and how do you choose?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Choosing the right method for the question.

    Key points a strong answer covers

    • Generative vs evaluative. Generative research explores problems; evaluative tests solutions.
    • Qualitative methods. Interviews, contextual inquiry, diary studies.
    • Quantitative methods. Surveys, analytics, A/B tests, card sorting, tree testing.
    • Choose by question & constraints. Choose by the question, project stage and constraints.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Using surveys to answer 'why' questions.
    • Running research without a clear question.

    Likely follow-up questions

    • When would a card sort help?
    • How do you do research with almost no budget?
    Example strong answer

    I choose by the question and the project stage. Early, when we don't yet understand the problem, I use generative methods: user interviews, contextual inquiry where I watch people work, or diary studies for behaviour over time. When I need numbers — how common is a problem, which option do people prefer — surveys and product analytics. For information architecture, card sorting and tree testing. To evaluate a design, usability tests, and A/B tests once it's live. Interviews and observation tell me why; analytics and surveys tell me how many. With no budget I use guerrilla tests with five people, support tickets, sales call notes and existing analytics.

    Practise this question and get feedback
  8. 8.

    How do you work with developers to make sure designs are built correctly?

    BeginnerRole knowledge

    What the interviewer is evaluating

    Cross-functional collaboration.

    Key points a strong answer covers

    • Involve early. Involve developers early on feasibility.
    • Complete specs. Specify all states: empty, loading, error, responsive.
    • Shared components & tokens. Use shared components and tokens.
    • Review the build. Review builds in staging and pair on fixes.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Handing over only the happy path.
    • First seeing the build after release.

    Likely follow-up questions

    • What do you do when a developer says a design is too hard to build?
    • How do you document interactions and animations?
    Example strong answer

    I involve developers early — in kickoff and early sketches — so feasibility issues come up before details are polished. My handoff covers more than the happy path: empty, loading and error states, long text and edge cases, responsive behaviour, and focus and keyboard behaviour, annotated in the file. I use our design system's components and tokens, so most of the UI maps to existing code. During the build I stay available for questions, and I review the work in staging, logging issues by importance rather than nitpicking pixels. If something is too costly, I'd rather find a simpler design together than insist on the original.

    Practise this question and get feedback
  9. 9.

    Walk me through a project in your portfolio you're proud of.

    IntermediateBehavioural

    What the interviewer is evaluating

    Storytelling, your specific contribution and impact.

    Key points a strong answer covers

    • Context & problem. The context and the problem.
    • Your role. Your specific role.
    • Process & decisions. Key decisions and why.
    • Outcome. The measurable outcome.
    • Reflection. What you learned.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Showing only final screens without the reasoning.
    • Saying 'we' throughout, hiding your contribution.

    Likely follow-up questions

    • What would you do differently?
    • What was the hardest trade-off?
    Example strong answer (a fictional story — use your own)

    I redesigned the appointment booking flow for a physiotherapy clinic network, where 38% of people started booking online but gave up. I was the only designer, working with a PM and three engineers. Analytics and session recordings showed people dropping at the practitioner step — they didn't know whom to choose — so I interviewed six patients and found they cared about the soonest slot near them, not the person. I tested two prototypes; the one that led with 'first available near you' won clearly. The trade-off was that some clinics wanted to promote specific practitioners, so we kept that as a filter. After launch, completion rose from 62% to 79% in two months. Next time I'd involve clinic staff earlier.

    Practise this question and get feedback

Behavioural & HR questions you'll also get

These come up in almost every ui/ux designer interview. Story questions are best answered with STAR — Situation, Task, Action, Result.

  • Tell me about yourself.

    BeginnerHR

    What the interviewer is evaluating

    Whether you can give a concise, relevant pitch that frames your experience around this job.

    Key points a strong answer covers

    • Present. Start with your current role and what you do.
    • Relevant past. Pick the most relevant past experience.
    • Strength / achievement. Include one strength or achievement with evidence.
    • Why this role. Finish with why this role is the next step.

    Suggested answer structure

    1. Present — your current role in one or two sentences.
    2. Past — the experience most relevant to this job.
    3. Proof — one achievement or strength with evidence.
    4. Future — why this role is the logical next step.

    Common mistakes

    • Reciting your whole CV chronologically.
    • Personal life story unrelated to the job.
    • Going over two minutes.

    Likely follow-up questions

    • Why are you looking to leave your current role?
    • What would your manager say is your biggest strength?
    Example strong answer

    I'm a front-end developer with four years' experience, currently at a fintech start-up where I build the customer dashboard in React and TypeScript. Before that I spent two years at an agency building e-commerce sites, which taught me to work fast with lots of different clients. The thing I'm proudest of recently is leading our move to a shared component library, which cut the time to build new screens by about a third. I'm now looking for a role where I can work on a larger product with a strong design system, which is exactly what drew me to this position.

  • Why should we hire you?

    BeginnerHR

    What the interviewer is evaluating

    Whether you understand the role and can match your strengths to its needs with evidence.

    Key points a strong answer covers

    • Role's needs. Show you understand what the role needs.
    • Matching strengths. Match two or three strengths to those needs.
    • Evidence. Back each with evidence.
    • Enthusiasm. Close with genuine enthusiasm.

    Suggested answer structure

    1. Name the two or three things the role needs most.
    2. Match each with your experience and evidence.
    3. Add what makes you different.
    4. Finish with genuine interest.

    Common mistakes

    • Generic claims like 'I'm hardworking' with no evidence.
    • Comparing yourself to other candidates you don't know.

    Likely follow-up questions

    • What would you do in your first 90 days?
    • What's one area where you'd need support?
    Example strong answer

    From the job description and our conversation, you need someone who can take ownership of the customer onboarding process, work with sales and product, and improve the numbers. I've done exactly that for three years: at my current company I redesigned onboarding for new accounts and cut the time to first value from 14 days to 6. I'm comfortable working across teams — I run a weekly session with sales and product on customer feedback — and I'm very data-driven, so I'd measure everything from day one. I'm also genuinely excited about your product, because it solves a problem I've seen customers struggle with.

  • Tell me about a time you disagreed with a teammate. How did you handle it?

    BeginnerBehavioural

    What the interviewer is evaluating

    Handling conflict constructively and keeping relationships.

    Key points a strong answer covers

    • Listened to their view. Show you listened to understand their view.
    • Used facts / common goal. Bring it back to facts or a shared goal.
    • Resolution & relationship. Resolve it and keep the relationship.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Making the other person the villain.
    • A story where you were simply right and they gave in.

    Likely follow-up questions

    • What if you couldn't reach agreement?
    • Have you ever been wrong in a disagreement?
    Example strong answer (a fictional story — use your own)

    On a website rebuild, a senior designer wanted an animated, image-heavy homepage, and I was worried it would hurt mobile load times and SEO. As the developer responsible for performance, I needed us to agree before the sprint started. I asked her to walk me through what she was trying to achieve — she wanted the brand to feel premium. I built two quick prototypes, one with her full design and one with lighter animations, and we tested both on a mid-range phone together. Hers took nearly six seconds to load. We agreed on a version that kept the key animation but lazy-loaded the rest. The page launched loading in under two seconds, and she later asked me to review designs earlier. I learned that testing together beats debating.

  • Tell me about a mistake you made and what you learned.

    BeginnerBehavioural

    What the interviewer is evaluating

    Honesty, accountability and learning.

    Key points a strong answer covers

    • Real mistake owned. Own a real mistake.
    • Fixed it. Show how you fixed it and who you told.
    • Changed behaviour. Show what you changed afterwards.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Choosing a fake mistake like 'I work too hard'.
    • Blaming others.

    Likely follow-up questions

    • How did your manager react?
    • How do you know you haven't repeated it?
    Example strong answer (a fictional story — use your own)

    In my first year as a marketing coordinator, I sent a promotional email to our whole list with the wrong discount code — I'd tested the email but not clicked the code itself. Within an hour customers were complaining that it didn't work. I told my manager immediately, set the wrong code to apply the discount too, and sent a short correction email with an apology. We lost very little revenue, and some customers replied thanking us for the quick fix. Since then I use a pre-send checklist that includes testing every link and code as a customer would, and I asked for a second person to check any campaign to more than 10,000 people.

  • Describe a situation where you worked under pressure or to a tight deadline.

    BeginnerBehavioural

    What the interviewer is evaluating

    Prioritisation, composure and delivery.

    Key points a strong answer covers

    • The pressure. Make the pressure concrete.
    • Prioritised. Show how you prioritised.
    • Communicated. Show how you kept people informed.
    • Delivered. Show the outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Glorifying working all night as the solution.
    • No mention of prioritising.

    Likely follow-up questions

    • What would you do if it was clear you couldn't make the deadline?
    • How do you stop pressure affecting quality?
    Example strong answer (a fictional story — use your own)

    Two days before a client presentation, our analyst fell ill and I had to finish the market research report she'd been leading. I listed everything left and asked the account director which sections the client cared about most — pricing and competitor comparison. I focused on those, reused verified data from our previous report, and moved the appendix to a follow-up email. I sent a short update each evening so nobody was surprised. We delivered the core report on time, the client approved the next phase, and the appendix followed two days later. I learned to ask early what matters most rather than trying to do everything equally well.

  • What would you do if you realised you were going to miss a deadline?

    BeginnerSituational

    What the interviewer is evaluating

    Transparency and problem solving.

    Key points a strong answer covers

    • Tell people early. Flag it as soon as you know.
    • Assess the gap. Work out how far off you are.
    • Options. Offer options: reduced scope, help, a new date.
    • Prevent repeats. Learn why it happened.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Waiting until the deadline to say anything.
    • Promising you'll just work all night.

    Likely follow-up questions

    • What if your manager is unavailable?
    • Has this happened to you?
    Example strong answer

    I'd tell the person depending on it as soon as I realised, not at the deadline. Before that conversation I'd work out how far off I am and why, so I could offer options: delivering the most important part on time and the rest a few days later, getting help from a colleague, or agreeing a new date. Then I'd let them decide what works best for them, and keep them updated. Afterwards I'd look at why it slipped — usually underestimating something — so I plan better next time.

Ready to answer them out loud?

Run a timed ui/ux designer mock interview, type or speak your answers, and get a score breakdown with what to improve.

Interview questions for related roles