Skip to content

20 interview questions

UX designer interview questions and answers

UX designer interviews centre on your portfolio and how you explain your decisions. Expect a portfolio walkthrough, questions about research and process, often a design exercise or whiteboard challenge, and behavioral questions about feedback and collaboration.

Updated

Portfolio and process

01Walk me through a project in your portfolio.

What they want to hear: Your thinking and your specific contribution, not just the final screens.

Answer outline (STAR)

  1. The problem, the users and the business goal, in a few sentences.
  2. Your role and the team around you.
  3. Key research findings and the decisions they led to, including options you rejected.
  4. The outcome, measured if possible, and what you would change now.

02Describe your design process.

What they want to hear: A process that adapts to the project, not a rigid diagram recited from memory.

Answer outline

  1. Understand: goals, users, constraints.
  2. Explore: research, sketches, multiple directions.
  3. Test: prototypes with real users, then iterate.
  4. Deliver and learn: hand-off, launch, measure, improve.
  5. Say how you shorten or adjust it when time is tight.

03Which project are you least proud of, and why?

What they want to hear: Honesty and the ability to learn from work that did not go well.

Answer outline (STAR)

  1. The project and what went wrong.
  2. Your part, stated plainly.
  3. What you learned and how it changed your later work.

04How do you decide when a design is ready to ship?

What they want to hear: Balancing quality with progress, and knowing that shipping is part of learning.

Answer outline

  1. It meets the agreed goal and has been tested with users at the right level.
  2. Known issues are understood and not blocking the main tasks.
  3. Accessibility and edge cases have been checked.
  4. There is a plan to measure and iterate after launch.

User research

05How do you decide which research method to use?

What they want to hear: Matching methods to questions, time and risk.

Answer outline

  1. Start from what you need to learn and what decision it will inform.
  2. Exploratory questions: interviews, contextual inquiry, diary studies.
  3. Evaluative questions: usability tests, A/B tests, analytics.
  4. Consider time, budget and access to users, and combine qualitative and quantitative evidence when you can.

06How would you run a usability test?

What they want to hear: Practical research skills and avoiding common biases.

Answer outline

  1. Define what you want to learn and write realistic tasks.
  2. Recruit participants who match the target users; around five per round often surfaces the main issues for a qualitative test.
  3. Use a neutral script, ask participants to think aloud and avoid leading questions.
  4. Synthesise findings by severity and share them with the team quickly.

07How do you design when you have no time or budget for research?

What they want to hear: Pragmatism and resourcefulness.

Answer outline

  1. Use what exists: analytics, support tickets, sales notes, previous research.
  2. Run quick guerrilla tests or short calls with a few users.
  3. Rely on established patterns and heuristics.
  4. Make assumptions explicit and plan to validate after launch.

08How do you turn research findings into design decisions?

What they want to hear: Synthesis, the step where weaker designers stall.

Answer outline

  1. Cluster observations to find patterns (affinity mapping).
  2. Turn patterns into insights and prioritised problems.
  3. Frame them as design questions or 'how might we' statements.
  4. Trace each major design choice back to the evidence.

Design skills and principles

09How do you make your designs accessible?

What they want to hear: Accessibility as part of the work from the start, with concrete practices.

Answer outline

  1. Follow WCAG guidance: colour contrast, text alternatives, keyboard access, visible focus, clear labels.
  2. Do not rely on colour alone to carry meaning, and support text resizing.
  3. Design states and error messages that screen reader users can follow.
  4. Test with tools and, where possible, with people who use assistive technology.

10What makes a design system useful?

What they want to hear: Systems thinking and an understanding of consistency at scale.

Answer outline

  1. Reusable components with clear usage guidance, not just a component library.
  2. Shared tokens for colour, spacing and type that design and code both use.
  3. A process for contributions and changes so it stays current.
  4. Adoption by teams, which depends on it saving them time.

11How do you design for mobile and desktop differently?

What they want to hear: Understanding context of use, not just screen size.

Answer outline

  1. Consider context: on the move, short sessions and touch on mobile; longer, focused work on desktop.
  2. Prioritise content and actions for small screens; use touch-friendly target sizes.
  3. Adapt navigation and layout rather than shrinking the desktop version.
  4. Test on real devices.

12Tell me about a design you simplified.

What they want to hear: Whether you remove complexity instead of adding features.

Answer outline (STAR)

  1. The original design and why it was confusing.
  2. How you found what users actually needed.
  3. What you removed or combined.
  4. The effect on task success or support load.

13Name a product with great UX and explain why.

What they want to hear: Design taste and the ability to explain it in terms of users and goals.

Answer outline

  1. Pick a product you use often.
  2. Explain one or two specific design choices and the user problem each solves.
  3. Mention one thing you would still improve.

Collaboration

14How do you work with engineers?

What they want to hear: Collaboration that leads to built designs that match the intent.

Answer outline

  1. Involve engineers early to understand constraints.
  2. Hand off with clear specs, states, edge cases and interaction notes.
  3. Be available during build and review implementations.
  4. Accept trade-offs when there is a good reason, and keep track of what was deferred.

15How do you handle a product manager who wants a feature that harms the user experience?

What they want to hear: Advocating for users with evidence, while respecting business goals.

Answer outline

  1. Understand the business goal behind the request.
  2. Show the user impact with research, data or a quick test.
  3. Propose alternatives that meet the goal with less harm.
  4. Agree a decision and a way to measure it.

16How do you present and defend your design decisions?

What they want to hear: Clear communication tied to goals and evidence.

Answer outline

  1. Start with the problem and the goal.
  2. Explain the options considered and why you chose this one.
  3. Back it with research, data or principles.
  4. Invite questions and be clear about what is still open.

Feedback and growth

17Tell me about a time you received harsh feedback on your design.

What they want to hear: Openness to critique and separating yourself from your work.

Answer outline (STAR)

  1. The feedback and who gave it.
  2. How you responded in the moment.
  3. What you took from it and changed.
  4. The result.

18Describe a time user testing proved you wrong.

What they want to hear: Humility and a habit of testing assumptions.

Answer outline (STAR)

  1. Your assumption and why you believed it.
  2. What testing showed.
  3. How you changed the design.
  4. What you now test earlier.

19How do you measure the success of a design?

What they want to hear: Connecting design to outcomes.

Answer outline

  1. Agree goals and metrics before launch.
  2. Track task success, time on task, conversion, retention or errors as relevant.
  3. Add qualitative signals: feedback, support tickets, follow-up tests.
  4. Use the results to plan the next iteration.

20How do you keep your skills current?

What they want to hear: Curiosity and a habit of learning from practice.

Answer outline

  1. Name specific sources or communities you follow.
  2. Describe a technique you recently tried in real work.
  3. Mention how you learn from colleagues, such as critiques or pairing.

How to prepare

  • Prepare two or three portfolio case studies you can present in ten to fifteen minutes each, focusing on problem, process, decisions and outcome.
  • Show messy work: sketches, rejected options and research notes tell the interviewer more than polished final screens.
  • Practise a whiteboard challenge out loud: clarify, define users, map the flow, sketch, then explain trade-offs.
  • Be clear about what you did versus what the team did in every project.
  • Learn the company's product and come with one or two thoughtful observations, not a redesign.

Practice these questions out loud with NORDON

Reading answers is not the same as saying them. NORDON's interview practice asks you questions written for the role, listens to your spoken answer and shows you how to make it stronger.

  1. Upload your CV in the Knowledge base, so questions and feedback use your real background.
  2. Open Practice, enter the role (for example UX designer), paste the job ad if you have it, and choose 3, 5, 8 or 10 questions and the answer language.
  3. Listen to each question and answer out loud, as you would in the room. You can also type an answer.
  4. Get a score from 1 to 10, what worked, what to improve and a stronger answer to rehearse. It uses only what you said and your documents, and leaves a [placeholder] where a fact about you is missing.
  5. Try the question again, or move on. For a dress rehearsal, run a mock call where an interviewer voice asks the questions out loud.

The free plan includes 10 scored practice answers a month and mock calls of up to 10 minutes, no card needed. Paid plans include more practice and mock calls of up to 30 minutes. How practice works

Practice is for preparing. Use live help in a real interview only where the interviewer allows AI assistance, never in an interview, test or assessment whose rules forbid it.

NORDON for job interviews

Preparing for your UX designer interview

What does a UX designer interview process usually include?

Commonly a recruiter screen, a portfolio presentation, interviews with design, product and engineering, and sometimes a design exercise, either live or as a take-home. The mix varies by company.

How many projects should my portfolio show?

Quality matters more than quantity. Two to four well-explained case studies that show your process and impact are usually more useful than many screenshots without context.

Should I do an unpaid take-home design exercise?

That is your call. Many candidates accept a short, clearly scoped exercise. If it seems large, it is reasonable to ask about the expected time or offer an existing case study instead.