UX Interview Questions: Prepare evidence, not a script

Map this interview before you prepare for every interview

There is no single UX interview loop. The people, order, exercises, and evidence can change with the role and organization. Nielsen Norman Group's research with UX professionals and hiring managers documents that range; it does not support one universal script.

Ask the recruiter what to expect. That is preparation, not gaming the process. You are trying to understand what evidence the team needs and how much time you will have to make it legible.

Build an evidence bank, not 30 memorized answers

Most questions draw from the same small set of experiences. Prepare those experiences well, then adapt the emphasis to what the person is actually asking. A useful answer gives enough context to understand your decision, then makes your contribution and learning easy to find.

Behavioral interview questions

STAR—Situation, Task, Action, Result—can help you remember the pieces of a story. It is not the only valid shape, and the result does not need to be triumphant. Context → tension → your decision → what happened → reflection often sounds more natural for design work.

• “Tell me about a disagreement with a stakeholder or teammate.”

  They may be listening for: How you understand another position, use evidence, and move the work forward.

  Build your answer from: Give the shared goal, the real point of disagreement, what you learned, what you proposed, and what changed. A compromise, an unresolved tradeoff, or a moment when you changed your mind can all be strong endings.

• “Tell me about a project that did not go as planned.”

  They may be listening for: Ownership, reflection, and your ability to adapt without rewriting history.

  Build your answer from: Name the expectation, the signal that challenged it, your part in the outcome, and what you now do differently. Do not turn every failure into a disguised victory.

• “How do you respond to critical feedback?”

  They may be listening for: Whether you can separate the work from your ego and judge feedback instead of merely accepting or rejecting it.

  Build your answer from: Choose feedback that changed a decision. Explain what you first thought, how you tested or interpreted the comment, what you changed or kept, and why.

• “Tell me about a decision you made with incomplete information.”

  They may be listening for: How you work under uncertainty without pretending an assumption is evidence.

  Build your answer from: Separate what you knew, what you assumed, the risk you accepted, the smallest responsible decision you made, and how you planned to learn more.

• “How have you handled competing priorities?”

  They may be listening for: Judgment, communication, and the consequences of saying yes or no.

  Build your answer from: Name the competing needs, the criteria you used, who had input, what moved or stopped, and how you communicated the tradeoff.

• “Tell me about a time you influenced a decision without owning it.”

  They may be listening for: Collaboration and influence beyond a job title.

  Build your answer from: Show how you framed the problem, made evidence legible, invited the right people in, and helped the group reach a decision. Give credit to others.

Portfolio and case-study questions

A portfolio often gives the team its richest evidence about how you have worked, but its importance and format vary. Follow the instructions you receive. If there are none, ask which projects or capabilities the team wants to discuss and how much time is available.

If you are still shaping the work, start with the complete portfolio guide and the case-study structure guide.

• “Walk me through a project you are proud of.”

  They may be listening for: What you notice, choose, and learn—not a tour of every slide.

  Build your answer from: Start with the problem and your role. Spend the most time on two or three consequential decisions, the evidence behind them, and the current outcome or limit.

• “What was your specific contribution?”

  They may be listening for: Honest ownership inside collaborative work.

  Build your answer from: Use I for your decisions and actions, we for shared work, and names or roles when another person contributed something important.

• “Why did you choose this direction?”

  They may be listening for: Whether the final design follows from the problem, evidence, and constraints.

  Build your answer from: Compare the direction with at least one plausible alternative. Explain the tradeoff you accepted—not just why the final version looks polished.

• “What changed between the first idea and the final result?”

  They may be listening for: Iteration that responds to something meaningful.

  Build your answer from: Show the trigger for change, the decision it affected, and what became clearer, safer, faster, or more useful as a result.

• “How did you know whether the design worked?”

  They may be listening for: An honest relationship between claims and evidence.

  Build your answer from: Use the evidence the project actually has: research observations, usability findings, critique, stakeholder decisions, production behavior, or product signals. If it was not measured, say what remains a hypothesis.

• “What would you do differently now?”

  They may be listening for: Growth without disowning your earlier self.

  Build your answer from: Choose one meaningful change and connect it to what you know now. Avoid redesigning the whole project from the safety of hindsight.

• “Which part of this project best represents your judgment?”

  They may be listening for: Your ability to identify the decision—not just the artifact—that mattered most.

  Build your answer from: Point to the moment when options were still open. Explain the competing needs and why your choice was defensible in that context.

• “Which project should we look at next?”

  They may be listening for: Whether you can read the room and connect your work to the role.

  Build your answer from: Offer a useful choice: one project that goes deeper on a skill they asked about and another that shows a different kind of work.

Process, product, and craft questions

Avoid answering these with an idealized end-to-end process that no real project follows. Show how you choose methods, recognize risk, and adjust when time, access, or evidence changes.

• “What is your design process?”

  They may be listening for: How you choose an approach, not whether you can recite a diagram.

  Build your answer from: Describe the decisions that stay constant and the activities that change with risk, time, access, and evidence. Then ground it in one project.

• “How do you start a new problem?”

  They may be listening for: How you reduce ambiguity before rushing to a screen.

  Build your answer from: Name what you first need to understand: the user or audience, job, current behavior, business goal, constraints, and what a useful outcome would look like.

• “How do you conduct research?”

  They may be listening for: Method choice and interpretation, not a list of methods.

  Build your answer from: Begin with the decision the team needed to make. Explain why a method fit, what the evidence could and could not tell you, and what changed afterward.

• “How do you balance user and business needs?”

  They may be listening for: Whether you can surface tension instead of claiming both sides always align.

  Build your answer from: Use a real tradeoff. Name the people affected, the business constraint, the harm or risk, the options considered, and the decision made.

• “How do you work with engineers and product partners?”

  They may be listening for: Shared problem-solving across disciplines.

  Build your answer from: Describe when partners enter the work, how constraints become visible, how decisions are recorded, and one moment their expertise changed your direction.

• “How do you approach accessibility?”

  They may be listening for: Specific habits and evidence—not a generic claim that accessibility matters.

  Build your answer from: Choose a real example: semantic structure, keyboard and focus behavior, readable type, motion controls, contrast measured from actual colors, or testing with assistive technology. Say what you verified and what needed specialist or user input.

• “How do you use a design system?”

  They may be listening for: Whether you can work coherently while recognizing when the system needs to change.

  Build your answer from: Explain how you reuse patterns, test fit, document exceptions, and contribute a new pattern when the product need is real rather than merely different.

• “Which tools do you use?”

  They may be listening for: Whether you can do the role's work and adapt—not allegiance to one brand of software.

  Build your answer from: Name the tools relevant to this role and what you use each one to accomplish. If a required tool is new to you, connect it to an adjacent workflow you already understand and your plan to learn it.

Whiteboard sessions, working sessions, and take-home exercises

Practical exercises can take many forms. A live session may be more conversational than a literal whiteboard problem; a take-home may ask for analysis, critique, a flow, or a presentation. Ask what the team wants to learn, who will be present, what tools are available, how much time to spend, and what a complete response means.

• “How would you improve this experience?”

  They may be listening for: How you frame the job and choose what deserves attention before proposing a redesign.

  Build your answer from: Ask who uses it, what they are trying to do, what evidence or constraints are available, and what kind of improvement matters. Then choose a bounded problem and explain the signal you would test.

• “What assumptions are you making?”

  They may be listening for: Whether you can distinguish a useful working assumption from a fact.

  Build your answer from: Name the assumption, why you need it to proceed, how risky it is, and what new evidence could change the direction.

• “Why did you prioritize that part of the problem?”

  They may be listening for: How you use the task, risk, and available time to choose scope.

  Build your answer from: Connect the scope to the core user job or largest uncertainty. Explain what you intentionally left out and when it would need attention.

• “What would you test first?”

  They may be listening for: Whether the proposed evidence matches the riskiest decision.

  Build your answer from: Name the uncertainty, the smallest responsible test, the people or behavior it needs to include, and what result would change your next move.

• “What would you do with more time?”

  They may be listening for: Whether you understand what the exercise did and did not establish.

  Build your answer from: Do not promise to add polish everywhere. Choose the largest remaining risk, missing perspective, edge case, or technical question and explain why it comes next.

1. 1
   Clarify the task

   Ask who the work is for, what job matters, which constraints are fixed, and what the team hopes to learn from the exercise.
2. 2
   Choose a useful scope

   State what you will focus on in the available time and what you are intentionally leaving open.
3. 3
   Expose options and assumptions

   Show the alternatives that matter, the evidence you wish you had, and the tradeoff behind the direction you choose.
4. 4
   Use the people in the room

   Treat new information as part of the work. Ask for input when it would change the decision instead of pretending the session is solitary.
5. 5
   Close with what comes next

   Name the largest risk, how you would test it, and what the current concept does not yet prove.

Team and working-style questions

“Culture fit” can reward familiarity instead of capability and contribution. A more useful conversation asks how you work, what support you need, what you want to learn, and how this team actually makes decisions. Be specific enough that both sides can notice a mismatch.

• “Why this role and this team?”

  They may be listening for: A specific connection between the work, your direction, and what you can contribute.

  Build your answer from: Connect one real part of the role or product to evidence from your work and something you want to deepen. You do not need to perform lifelong devotion to the company.

• “What kind of environment helps you do your best work?”

  They may be listening for: Useful self-knowledge and compatibility with the actual team.

  Build your answer from: Name the conditions that matter—feedback cadence, focus time, clarity, collaboration, pace—and how you stay effective when those conditions are imperfect.

• “How do you communicate when a project is at risk?”

  They may be listening for: Whether you surface uncertainty early and make the next decision easier.

  Build your answer from: Give the signal, the people affected, the options you brought forward, and how the team decided what to protect or change.

• “What do you want to learn next?”

  They may be listening for: A believable direction that this role can support.

  Build your answer from: Name a capability, why it matters to the work you want to do, and one step you have already taken. A real learning edge is more useful than a disguised strength.

• “Where do you want to be in a few years?”

  They may be listening for: Direction, not a binding prediction.

  Build your answer from: Talk about the kinds of problems, responsibility, or impact you want to grow toward. You do not need to hide a long-term ambition; connect the near-term role to what you genuinely want to learn and contribute now.

Questions to ask the interviewers

You do not need to ask a clever question for its own sake. Ask for information that will help you understand the role, evaluate the team, or make a decision. If a question was already answered, say what you heard and ask a more specific follow-up.

Build a preparation plan around the time you have

There is no mandatory two-week ritual. Start with the highest-risk part of this interview and use the time you actually have. A short, focused rehearsal can be more useful than days of reading generic answers.

Sources and further reading