UX Designer interview questions

UX and UI describe different but connected parts of product design.

• UX covers the end-to-end experience of completing a user goal.
• UI focuses on the interface’s visual hierarchy, controls, and interactive presentation.
• The disciplines overlap because unclear controls or weak hierarchy can disrupt the wider experience.

I turn an unclear request into a specific problem before exploring solutions.

• I identify who has the problem and what that person is trying to accomplish.
• I ask what evidence supports the problem and which constraints shape the work.
• I rewrite the request around the user, context, and desired outcome without prescribing a feature.

A requested feature is only one possible response to an underlying user need.

• I ask what happened before the request to understand its trigger and context.
• I clarify the progress or outcome the user expects rather than accepting the proposed feature literally.
• I compare alternative solutions and test which one serves the underlying need best.

I test the assumptions that combine high uncertainty with serious consequences first.

• I check foundational beliefs, such as whether the target user actually has the stated problem.
• I record assumptions explicitly so the team can compare uncertainty and impact.
• I choose the fastest ethical research method that can provide useful evidence.

A useful problem statement guides design without locking the team into one solution.

• It identifies a specific user, goal or obstacle, and relevant context.
• It includes evidence that the problem exists instead of relying on an unsupported opinion.
• It is focused enough to direct ideas but open enough to allow different design approaches.

I define early success as observable progress toward the user’s goal.

• I name the target behavior, such as recovering an account without contacting support.
• I attach a measurable outcome, such as the completion rate for that flow.
• I add guardrails such as errors or abandonment so improvement in one metric does not hide harm.

Involving users early reduces the cost of discovering that the team is solving the wrong problem.

• Early conversations can reveal missing context or an incorrect understanding of the need.
• Tests with rough flows can expose confusion before polished screens consume more effort.
• Low-fidelity artifacts are easier to change because visual details have not become fixed.

Qualitative and quantitative research answer complementary UX questions.

• Qualitative methods such as interviews and observation explain behaviors, motivations, and causes.
• Quantitative methods measure patterns at scale through data such as completion rates or survey responses.
• Using both can show what is happening and provide evidence about why it may be happening.

A research plan connects a product decision to a feasible way of gathering evidence.

• It states the decision, research questions, and criteria for relevant participants.
• It defines the method, tasks or discussion topics, schedule, and consent process.
• It explains how observations will be captured, analyzed, and shared with the team.

I choose a research method from the learning goal and the product stage.

• I use interviews to explore motivations and specific past behavior.
• I use observation when I need to understand a real workflow and its context.
• I use usability testing to learn whether people can complete tasks with a proposed design.

A recruitment screener should select people whose experience is relevant to the research question.

• I screen for meaningful behaviors, context, and experience rather than broad demographics alone.
• I include only criteria that can affect how participants encounter the problem or task.
• I exclude conflicts such as employees or professional test participants when they could bias the study.

There is no universal participant count for user interviews.

• I base the sample on the study scope, audience diversity, and whether meaningful patterns recur.
• Five to eight well-matched people can reveal themes in a focused junior project.
• I report the sample limits and do not claim that a small qualitative study represents the whole market.

A neutral interview question lets the participant describe experience without being steered.

• It does not reveal which answer the researcher hopes to hear.
• It does not assume that the participant had a particular experience.
• I ask about the last choice of a delivery option instead of asking whether express delivery was convenient.

Questions about past behavior usually produce stronger evidence than hypothetical predictions.

• Concrete events are easier for people to recall reliably than imagined future choices.
• The last real occurrence reveals triggers, actions, and the sequence of the experience.
• Follow-up questions can uncover constraints and workarounds that broad preference questions miss.

I probe with open prompts while keeping my own interpretation out of the participant’s answer.

• I ask what happened next to continue the participant’s account.
• I invite the person to show an action or explain what made it difficult.
• I allow silence instead of offering an explanation that the participant may simply accept.

I redirect an off-topic participant without dismissing potentially useful context.

• I briefly acknowledge the point so the participant knows they were heard.
• I return to a prepared research question or mention the remaining session time.
• If the tangent is relevant, I note it and revisit it after covering the essential topics.

Research consent must be informed, explicit, and reversible.

• Participants should know the study purpose and what information will be recorded.
• They should understand how their data will be used and that they can stop without penalty.
• I obtain permission before recording and retain only information the team genuinely needs.

Observation is stronger than an interview when important parts of a workflow are hard to recall or explain.

• It can reveal implicit steps and interruptions that participants may omit in conversation.
• It preserves physical context and shows workarounds as they happen.
• I observe with permission and ask about reasons afterward instead of guessing why an action occurred.

Observation notes should preserve what happened while keeping interpretation clearly separate.

• I record visible actions, direct quotes, useful timestamps, and relevant context.
• I capture tools, sequence, interruptions, errors, and workarounds in the workflow.
• I label my interpretations separately and avoid collecting unnecessary personal information.

A survey supports UX research by measuring known patterns across a larger group.

• I use it to estimate how common a behavior is or to collect structured feedback.
• I keep each question focused, provide balanced response options, and pilot the survey first.
• I do not rely on a survey alone to discover deep motivations that require qualitative follow-up.