Offermic
Try it free

UX Designer Interview Questions and Answer Tips

UX Designer, Creative & Design. 21 questions.

Updated

Written by

The short answer

UX designer interviews test your process more than your visuals. Expect a portfolio walkthrough plus questions on user research, iteration, stakeholder feedback, accessibility, working with engineers and measuring design impact. Strong answers show the user problem behind each decision, the iterations you threw away, and a result such as task success or conversion.

Key takeaways

  • Walk through portfolio projects as stories: problem, research, options, decision, result.
  • Show at least one design that changed because of user evidence or feedback.
  • Accessibility should appear naturally in your process, not as an afterthought.
  • Interviewers listen for how you talk about engineers and product managers.
  • Bring a metric for design impact, even a small usability-test result.

What interviewers look for

  • Design decisions traced back to user research or usability evidence
  • Several iterations shown, with reasons for what was discarded
  • Handling conflicting stakeholder feedback by returning to user goals
  • Accessible design choices: contrast, focus order, readable text, touch targets
  • Collaborative handoff with engineers and use of a design system
  • Honesty about constraints and what they would do with more time

Red flags

  • Aesthetic-first explanations with no user problem behind them
  • Portfolio shows final screens only, with no process
  • Getting defensive when the interviewer critiques a design
  • Speaking dismissively about developers or product managers
  • No way to tell whether a design worked after launch
  • Treating accessibility as a checklist item at the end

Numbers worth bringing

  • Task success rate in usability tests before and after a redesign
  • Time on task for a key flow
  • Conversion or completion rate on a redesigned funnel
  • Accessibility issues resolved against WCAG criteria
  • Support tickets about a confusing flow before and after
  • Design system component adoption across product teams

The questions

Behavioral

  1. 1

    Walk me through a project in your portfolio from problem to result.

    Tip: Spend more time on research and decisions than on final visuals, and close with an outcome.

  2. 2

    Tell me about a design that changed significantly after user testing.

    Tip: Show the original idea, what users struggled with and the version that tested better.

  3. 3

    Describe a time you received harsh feedback on your work.

    Tip: Separate yourself from the design, explain what you took from it and what you changed.

  4. 4

    Tell me about a time a technical constraint forced you to change a design.

    Tip: Show you treated the constraint as input and found a solution that still served users.

  5. 5

    Describe a project with very little time. How did you adapt your process?

    Tip: Show which steps you compressed, what you kept, and the risk you accepted consciously.

  6. 6

    Tell me about a disagreement with a product manager about a design.

    Tip: Show how you found shared goals and what evidence settled it.

Technical

  1. 7

    How do you decide which research method to use for a new problem?

    Tip: Match method to question: interviews for why, usability tests for how, analytics for how many.

  2. 8

    How do you build accessibility into your design process?

    Tip: Mention contrast, focus states, labels, text size and testing with assistive technology.

  3. 9

    How do you work with engineers during handoff and build?

    Tip: Talk about early involvement, annotated specs, design system components and reviewing builds.

  4. 10

    How would you measure whether a redesign succeeded?

    Tip: Define the metric before launch, such as task success or completion rate, and a comparison.

  5. 11

    What makes a good design system, in your experience?

    Tip: Discuss clear components, documentation, tokens, contribution rules and real adoption.

  6. 12

    How do you run a usability test with five participants?

    Tip: Cover task-based scripts, not leading users, observing behavior and summarizing patterns.

  7. 13

    How do you present design decisions to executives with limited time?

    Tip: Lead with the user problem and the result, then show only the key trade-off.

Situational

  1. 14

    A stakeholder wants a bold visual change, but test data favors the current design. What do you do?

    Tip: Share the evidence, explore their underlying goal and propose a test rather than a debate.

  2. 15

    Eight stakeholders give you conflicting feedback on a prototype. How do you synthesize it?

    Tip: Group feedback by user goal, identify real conflicts, and bring the key trade-off to the decision-maker.

  3. 16

    Mid-sprint, product adds five new feature requests to your flow. How do you respond?

    Tip: Assess each against the user goal and timeline, and agree with product on what moves to later.

  4. 17

    You are asked to design a feature you believe users do not need. What do you do?

    Tip: Ask for the evidence behind it, propose a quick validation, and design the smallest test.

  5. 18

    Your portfolio piece looks great but the project was cancelled. How do you present it?

    Tip: Be honest about the outcome and focus on the process and what you learned.

Motivation

  1. 19

    Why do you want to design for our product and users?

    Tip: Show you have used or studied their product and name one user problem you want to solve.

  2. 20

    Which product has great UX, in your view, and why?

    Tip: Pick a specific flow and explain why it works for its users, not just that it looks good.

  3. 21

    What area of UX do you want to grow in next?

    Tip: Name a direction, such as research, interaction design or design systems, with a reason.

UX designer interview questions test your design process more than your visual style. Expect a portfolio walkthrough and questions on research, iteration, feedback, accessibility, collaboration and measuring impact, and answer them by linking every design decision to a user problem and a result.

What are UX designer interviews looking for?

The U.S. Bureau of Labor Statistics describes digital designers as people who “develop, create, and test website or interface layout, functions, and navigation for usability.” Interviewers focus on the “test” and “usability” parts of that sentence. They want to know:

  • Where your ideas come from. Research, data, support tickets or a hunch?
  • How you iterate. What did you try, what failed, and why did you change course?
  • How you handle feedback. From users, stakeholders and critique sessions.
  • How you work with others. Especially engineers and product managers.
  • Whether your work mattered. Some measure of impact.

Accessibility questions are now routine. The W3C’s WCAG 2.2 is the reference most teams use, and interviewers want to hear it inside your process, not bolted on. Our creative industry guide covers how design interviews differ from other roles, and the frontend developer questions show the engineering side of the same work.

How should you present a portfolio project?

Treat each project as a story with five beats:

  1. The problem: who struggled with what, and how you knew.
  2. Research: the method you chose and what surprised you.
  3. Options: two or three directions, including one you rejected.
  4. Decision and trade-offs: why this direction, and what you gave up.
  5. Result: a metric, test result or clear stakeholder outcome.

Interviewers often interrupt with “why?” Answer with evidence, not taste. “Users in testing missed the button” beats “it felt cleaner.”

Example STAR answer: design changed by testing

Example answer — mid-level UX designer, question: “Tell me about a design that changed significantly after user testing.”

  1. Situation

    Our mobile app's account setup had a high drop-off rate, and I was asked to redesign it. My first concept combined all steps on one long scrolling screen to reduce taps.

  2. Task

    I needed to validate the concept before engineering committed a sprint to building it.

  3. Action

    I ran moderated tests with six new users on a clickable prototype. Four of them missed a required field below the fold and got an error they did not understand. I switched to a three-step flow with a progress indicator, clearer inline validation and larger touch targets, and retested with five more users. I shared a short clip reel with the product manager and engineers so they could see the difference.

  4. Result

    Task success in testing rose from two out of six to five out of five. After launch, completion of account setup improved by about 18% over the following month, and the stepped pattern became a component in our design system.

Why it works: it shows a first idea that failed, evidence that changed it, collaboration, and measured impact.

Which general questions should you prepare?

Design loops include standard behavioral prompts too. Have stories for handling negative feedback, a creative approach and collaboration. The STAR method keeps them focused.

What questions should you ask the interviewer?

  • “How does design research get planned and funded here?”
  • “How early are designers involved before engineering starts?”
  • “Is there a design system, and who owns it?”
  • “How do you measure design quality or impact today?”
  • “What does critique look like on this team?”

More options: questions to ask the interviewer.

How should you practice?

Present one portfolio project out loud in ten minutes, then ask a friend to interrupt with “why?” at three random points. Practice answering with evidence. If the first round is a recorded video screen, the video interview tips help with framing and pacing.

Questions people also ask

How long should a UX portfolio walkthrough be in an interview?

Plan for about ten minutes per project unless told otherwise, with most of that time on the problem, research and decisions. Keep final screens brief.

What if I do not have metrics for my design work?

Use what you have: usability test results, qualitative quotes, fewer support tickets or stakeholder decisions. Explain how you would measure it next time.

Sources

  1. Web Developers and Digital Designers: Occupational Outlook Handbook, U.S. Bureau of Labor Statistics
  2. WCAG 2 Overview, W3C Web Accessibility Initiative

Written by, Founder

Can Garip is the founder and developer of this app. He builds the AI mock interview product and writes its interview preparation guides.

Drafted with AI assistance, then edited and fact-checked by the author.

How we write