HeroApply
Auto Apply to hundreds of jobs in a few hours
English (US)EspañolItalianoPortuguêsFrançaisDeutsch日本語한국어
Sign up

UX Designer interview questions and how to answer them

A UX interview is really one long test of how you think out loud. The panel already liked your portfolio enough to call, so now they want to see whether the reasoning behind it is yours and whether you can hold it together when someone pushes back.

11 questions8 minute read

Part 1

1.Walk me through a project you're proud of.

Why they ask

It's the portfolio question in its purest form. They want to see whether you can tell a clear story about a problem, your decisions and the outcome, without drowning them in every artifact you made.

How to answer

  • Open with the business problem and who it hurt, in a sentence or two
  • Say exactly what your role was and who else was involved
  • Pick the few decisions that mattered most and explain the tradeoff behind each
  • Show what testing or data changed your mind along the way
  • End with the outcome and what you'd do differently now

2.How do you decide what to design when you don't have time for research?

Why they ask

Most teams ship faster than an ideal research plan allows. They want to know you won't stall, and that you won't guess blindly either.

How to answer

  • Start from what already exists: support tickets, analytics, session recordings, sales call notes
  • Run the smallest test that could change the decision, like a few quick hallway tests on a Figma prototype
  • Write down your assumptions so the team knows what's unproven
  • Plan a follow-up check after launch so the guess gets verified

3.Tell me about a time an engineer said your design couldn't be built.

Why they ask

UX designers who can't work through technical constraints create friction on every sprint. They're checking whether you treat engineers as partners or as obstacles.

How to answer

  • Describe the specific constraint, such as an API that couldn't return data fast enough
  • Explain how you found out what was actually hard, not just what was said
  • Show the compromise you designed together and what the user still got out of it
  • Mention what you changed about how you involve engineers early
4.How would you design a way for people to split a restaurant bill in an app?

Why they ask

This is the classic whiteboard prompt. The topic doesn't matter much. They're watching how you frame the problem before you draw.

How to answer

  • Ask clarifying questions first: who pays, how people split, whether it's inside an existing payments app
  • Pick a primary user and the main scenario and say out loud why you chose them
  • Sketch the core flow, then walk through edge cases like someone who leaves early or a declined card
  • Say how you'd test the flow and what you'd measure after launch
5.How do you run a usability test?

Why they ask

Plenty of candidates list usability testing on their résumé but have only watched one. They want to hear the mechanics.

How to answer

  • Set a clear goal and the tasks that test it, written without leading words
  • Recruit people who match the real users, not coworkers, when you can
  • Moderate without helping: ask what they expect to happen, stay quiet when they struggle
  • Synthesize patterns in a tool like Dovetail or a FigJam board and share clips with the team
  • Turn findings into prioritized changes, not a long report nobody reads

Part 2

6.How do you make sure a design is accessible?

Why they ask

Accessibility has moved from a nice extra to a real product and legal concern. They want to know whether you design for it from the start or bolt it on at the end.

How to answer

  • Name specifics: colour contrast, focus order, visible focus states, labels for screen readers, touch target size
  • Mention the WCAG guidelines and checking contrast with a plugin while you design
  • Talk about testing with a screen reader like VoiceOver or NVDA, even briefly
  • Explain how you annotate specs so engineers build it correctly
7.How do you work within a design system, and when do you break from it?

Why they ask

Most product teams have a component library. They want someone who reuses it by default but knows how to propose a change when a pattern doesn't fit.

How to answer

  • Start from existing components so the product stays consistent and engineers move faster
  • Break from it only when a real user need isn't met, and show the evidence
  • Bring the proposed component to the design system team rather than detaching it quietly in Figma
  • Give an example of a component you added or changed and why
8.How do you measure whether a design worked?

Why they ask

Hiring managers want designers who care about outcomes, not just handoff. This separates people who ship and walk away from people who follow up.

How to answer

  • Define success before launch with the product manager: task completion, drop-off at a step, support contacts
  • Mention the tools the team uses, like Amplitude, Mixpanel or Hotjar
  • Pair numbers with qualitative follow-up, like a round of interviews after release
  • Give an example where the data showed the design didn't work and what you changed
9.Tell me about feedback on your work that you disagreed with.

Why they ask

Design critique is constant. They want to see you take feedback without folding or getting defensive.

How to answer

  • Name the feedback and who gave it
  • Explain how you worked out the concern behind it
  • Show how you tested or reasoned it through instead of arguing taste
  • Share the outcome, including if the other person turned out to be right
10.How do you prioritize when several product managers want your time?

Why they ask

Many UX designers support more than one team. They want to see that you can say no or not yet without burning relationships.

How to answer

  • Make the work visible, on a Jira board or a shared list, so tradeoffs are clear to everyone
  • Tie priority to impact and deadlines, and let the managers or your design lead settle conflicts
  • Offer lighter help, like a quick review, when you can't take on a full project
  • Give a specific example of a request you pushed back

Part 3

11.Why do you want to work on this product?

Why they ask

They want proof you've looked at the product closely, not just the job ad.

How to answer

  • Mention something specific you noticed after using the product yourself
  • Connect it to the kind of problems you like solving
  • Offer a small, respectful observation about a flow you'd want to explore

Questions to ask them

Ask at least two. It shows you're picking them too.

  • How does design work with product and engineering here, and at what point do designers join a project?
  • Do you have dedicated researchers, or do designers run their own research?
  • What does a design critique look like on this team, and how often does it happen?
  • Can you tell me about a recent design decision that got changed after launch, and why?
  • What would you want this person to have done by the end of their first few months?

Related interview guides

UI DesignerProduct Designer