Top 20 UX interview questions and how to answer them Pinned

Interviews for UX roles test two things: how you think and how you communicate. Almost every question below is a version of "show me your reasoning". Use this guide to prepare your own answers in your own words. Do not memorise someone else's script.

How to prepare in 30 minutes

• Pick 3 projects you can talk about for 10 minutes each. For every one, know the problem, your role, what you did, what changed, and what you would do differently.
• Use a simple structure. For stories, use Situation, Task, Action, Result (STAR). For opinions, use Point, Reason, Example.
• Put numbers on results where you honestly can: time saved, errors reduced, conversion, satisfaction. If you have no numbers, describe the observable change.
• Say "I" for your work and "we" for the team's. Interviewers want to know what you personally did.
• Keep answers to about two minutes. Stop, then ask if they want more detail.

---

The 20 questions

1. Tell me about yourself

Why they ask: to hear how you frame your story and whether it fits the role.

How to answer: give a 60 to 90 second summary: where you are now, how you got here, and why this role is the natural next step. Use present, past, future.

Starter: "I'm a product designer focused on research-led work in fintech. I started in graphic design, moved into UX after seeing how much usability problems cost customers, and for the last three years I've led end-to-end design for a payments app. I'm looking for a team where I can go deeper on design systems, which is why this role caught my eye."

2. Why did you choose UX?

Why they ask: to understand your motivation and whether you grasp what UX is.

How to answer: share a real moment that pulled you in, then connect it to what you value: understanding people, solving problems, making things clearer. Avoid "I like making things pretty".

Starter: "I watched my parent struggle to book a medical appointment online and give up. I realised the problem was not their ability but the design. I wanted to be the person who removes that kind of friction."

3. Walk me through a project from your portfolio

Why they ask: this is the heart of the interview. They want your decisions, not your screens.

How to answer: follow a clear arc: the problem and who it affected, your role, the key insight, two or three decisions with the trade-offs you weighed, the outcome, and what you learned. Spend most time on decisions.

Tip: rehearse it aloud with a timer. Be ready to go deeper on any screen.

4. What is your design process?

Why they ask: to see whether you work in a structured, adaptable way.

How to answer: describe your typical flow (understand, define, explore, test, deliver), then immediately show flexibility: how it changes with time, team size and risk. Back it with a brief example.

Starter: "I start by making sure we are solving the right problem, then explore several options before narrowing, and test early with real users. On a recent tight deadline I skipped a full study and ran five quick prototype tests instead."

5. Tell me about a time you disagreed with a stakeholder

Why they ask: to see how you handle conflict and influence without authority.

How to answer: use STAR. Show that you listened first, understood their goal, used evidence (research, data, a quick prototype) rather than opinion, and reached a result or a respectful compromise.

Avoid: painting the other person as foolish. Show respect.

6. How do you respond to critique and feedback?

Why they ask: designers get critiqued constantly. They want someone who learns, not someone defensive.

How to answer: explain how you separate feedback about the work from feedback about you, how you ask clarifying questions, and how you decide what to act on. Give one example where feedback changed your design for the better.

7. How do you work with developers?

Why they ask: shipping needs collaboration, not handoffs.

How to answer: talk about involving engineers early, sharing constraints, agreeing on components and tokens, reviewing builds, and being available during implementation. Show that you respect technical limits and negotiate scope together.

Starter: "I invite an engineer to the first design review so feasibility shapes the idea, not kills it at the end."

8. How do you measure the success of a design?

Why they ask: to see whether you connect design to outcomes.

How to answer: define success before designing: a user goal plus a business goal. Mention both behaviour (task success, time on task, drop-off) and attitude (satisfaction, confidence). Say how you would collect them and what you would do if the numbers disappoint.

9. How do you choose which research method to use?

Why they ask: to check you match the method to the question, not the other way round.

How to answer: start from the question and the stage. Early and unclear: interviews or observation. Testing a design: usability tests. Needing numbers: surveys or analytics. Mention constraints such as time, budget and access to users.

10. How do you prioritise when everything is urgent?

Why they ask: every team has more work than time.

How to answer: describe a simple framework (impact on users and business against effort and risk), how you align with the product manager, and how you communicate trade-offs openly. Show you can say "not now" with a reason.

11. Tell me about a mistake or a project that failed

Why they ask: to see self-awareness and growth.

How to answer: pick a real, modest failure, own your part without excuses, explain what you learned, and show how you changed your behaviour afterwards. Do not choose something that reveals a serious flaw for the role.

12. How do you approach accessibility?

Why they ask: accessibility is a core part of quality and often a legal requirement.

How to answer: say you build it in from the start, not at the end: colour contrast, keyboard use, focus order, labels, clear language, and testing with assistive technology and real users with disabilities. Mention WCAG as a baseline and give one concrete thing you have done.

13. How do you work with limited time or budget?

Why they ask: real teams are constrained.

How to answer: show you can scale your process: guerrilla testing, five-user tests, existing data, competitor and heuristic reviews, and focusing on the riskiest assumptions. Explain what you would cut and what you would never cut.

14. Tell me about a time data or research changed a decision

Why they ask: to see whether research actually influences you and the team.

How to answer: use STAR. Describe the original plan, what you found, how you shared it in a way people would act on, and what changed. Give the result.

15. How do you present your work to executives or non-designers?

Why they ask: influence matters as much as craft.

How to answer: lead with the problem and the outcome, not the process. Use their language (goals, risk, cost), show a short story with one clear recommendation, and keep detail ready for questions.

16. How would you improve a product you use? (design critique)

Why they ask: to watch you think on your feet.

How to answer: do not jump to solutions. Say who the users are and what they are trying to do, point out two or three real issues with reasons, then propose changes and how you would test them. Say what you do not know.

17. How do you see AI changing UX work?

Why they ask: to understand your curiosity and judgement.

How to answer: be balanced. Mention where AI helps (summarising notes, drafting variations, speeding up routine work) and where human judgement still matters (understanding people, ethics, deciding what is worth building). Give an example of how you use it carefully.

18. What are your strengths and weaknesses?

Why they ask: self-awareness and honesty.

How to answer: choose strengths that matter for this role and back each with a short example. For a weakness, choose a real one you are actively improving, and explain what you are doing about it. Avoid "I work too hard".

19. Why do you want to work here?

Why they ask: to see genuine interest and preparation.

How to answer: research the product, the users and the team. Name something specific you admire or would improve, and connect it to your skills and goals. Generic praise is easy to spot.

20. What are your salary expectations?

Why they ask: to check you are within budget and how you negotiate.

How to answer: research the range for the role, level and location first. Give a range based on that research, say it depends on the full package and responsibilities, and show you are flexible. If you are asked first and unsure, it is fine to ask about their range.

Starter: "Based on my research for this level and location, I'm looking at a range of X to Y, and I'm open to discussing the whole package."

---

Before you finish: questions to ask them

Always have 3 or 4 questions ready. Good ones:

• How does design work with product and engineering here?
• How do you do user research, and how often do you speak to customers?
• What does success look like in the first 6 months?
• What is the biggest challenge the team faces right now?

Final tips

• Practise out loud, ideally with a friend or a mentor.
• Be honest. Do not claim work you did not do. Interviewers dig into details.
• Follow up with a short thank-you message the same day.
• Learn from each interview. Write down the questions you found hard and improve your answers.

Have a question that always trips you up? Share it below and let the community help.