Top 30 Intermediate UX Research Interview Questions and Answers
30 intermediate multiple-choice UX Research interview questions, past the definitions: how the pieces fit together, what breaks in practice, and the trade-off behind a choice. They come from 30 bites in the UX Research library, the middle slice of the 132 UX Research interview questions in the library. Answer them here or read straight down. Every question carries the correct option, why it is correct, and a link to the bite it came from.
User research, usability testing, personas, journeys
30 questions. Pick an answer, or open “Show the answer” to read it.
Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.
Question 1 of 30
A team is running a usability study across three two-week sprints. How should this research work be managed in the product backlog?
Show the answer
Answer: a · Maintain one backlog item across all three sprints, marking individual tasks done as they are completed.
The card emphasizes that research should live as a single backlog item that stays open across sprints while bite-sized tasks are completed, making B correct. Option D is tempting because it follows strict sprint boundaries, but forcing a research story closed at sprint end regardless of study status is explicitly flagged as a common mistake.
Read the full bite: How does UX research integrate into a two-week agile sprint?
Question 2 of 30
After releasing an MVP export feature, a team wants to know if users can successfully complete exports. Which research approach fits best?
Show the answer
Answer: b · Measuring task success and observing friction while users try the export flow
Once an MVP exists, evaluative research such as usability testing measures task success and solution fit. Observing how reports fit into workflows is a generative method meant to uncover needs before design begins, so it does not validate whether the new export flow actually works.
Read the full bite: Generative versus evaluative research: when to use each
Question 3 of 30
A team running a six month diary study needs to link the same participant's data across sessions, so they generate each participant's ID by taking an unsalted SHA-256 hash of their email address and store only that hash. What is wrong with this approach?
Show the answer
Answer: a · An unsalted hash of a guessable input like an email is trivially reversible by precomputing hashes for common emails, unlike a keyed HMAC with a separately secured key
Because email addresses are guessable, an attacker can precompute hashes for likely emails and match them against the stored value, so an unsalted hash offers little protection. A keyed hash such as HMAC, with the key held separately and access controlled, is what actually secures a stable pseudonym, and the result is still pseudonymization, not the irreversible anonymization the third option claims.
Read the full bite: Anonymization vs pseudonymization and key handling
Question 4 of 30
When handling a GDPR erasure request, what is the correct way to update aggregated analytics dashboards derived from the user's data?
Show the answer
Answer: d · Reprocess the underlying data pipeline to exclude the user and rebuild all affected metrics
The card states that aggregated dashboards must be fixed by reprocessing the underlying pipeline or using differential privacy, because simple subtraction fails for complex metrics like averages and funnels. Option B represents the common misconception of manually adjusting aggregates, which does not reliably remove the user's influence from derived metrics.
Read the full bite: How do you fulfill a GDPR erasure request across data stores?
Question 5 of 30
A participant revokes consent two months after granting it. How should a compliant system handle this?
Show the answer
Answer: d · Append a new revocation event to the immutable ledger while preserving the original grant
Regulators require proof of what the user saw and when, so the original grant must remain intact while revocation is appended as a new event. Updating in place or using boolean flags destroys the audit trail and violates compliance requirements.
Read the full bite: Design a centralized consent platform: core components and database schema
Question 6 of 30
When validating a UX feature constrained by a slow legacy API, which research approach best determines if the constrained experience is shippable?
Show the answer
Answer: b · Scope the study to latency-critical tasks, simulate realistic API delays with engineering stubs, and compare task success against the current baseline
Simulating realistic API delays with stubs isolates the true friction point and benchmarking against the current baseline shows relative improvement, while testing an ideal prototype falsely validates a fantasy experience that engineering cannot ship.
Read the full bite: How do you validate UX within hard technical constraints?
Question 7 of 30
When supplementing a two-week remote diary study with technical instrumentation, which approach best validates self-reported behavior while preserving ecological validity?
Show the answer
Answer: d · Log anonymized feature usage, session duration, and device switches, then correlate them with diary entries via anonymized participant IDs
Option D is correct because it pairs passive, privacy-preserving analytics with anonymized linkage to triangulate diary claims without introducing observer bias. Option A is tempting but wrong because invasive capture like screen recording destroys the natural context that makes diary studies valuable and violates the required anonymization and consent protocols.
Read the full bite: What technical instrumentation supplements a two-week diary study?
Question 8 of 30
Which research pairing best applies triangulation to checkout abandonment by first locating the drop-off and then explaining the human reasoning behind it?
Show the answer
Answer: c · Funnel analytics followed by moderated usability testing to find leaks and observe behavioral barriers
Funnel analytics pinpoints exactly where users abandon, while moderated usability testing reveals cognitive and emotional causes like form confusion; option D is a common trap because two self-report methods only capture post-rationalized excuses, not actual behavior.
Read the full bite: Propose two research methods to investigate checkout abandonment
Question 9 of 30
When building a recruiting pipeline for a niche developer tool, which combination of tactics addresses the three core burdens of qualification, screening, and attendance?
Show the answer
Answer: c · Target active practitioners in specialized communities, verify expertise with a brief technical task after the initial screener, and prepare backup candidates for no-shows
The card emphasizes that strong recruiting targets current practitioners in specialized communities, uses layered technical verification because self-reported expertise is often inflated, and maintains backup candidates to ensure attendance. Option B exemplifies the red flag of relying on titles and a single touchpoint, while B and D fall back on generic sourcing and unverified self-reporting.
Read the full bite: What criteria and questions ensure right users for a specialized dev tool?
Question 10 of 30
A screener for a finance app study is being gamed by professional testers who memorize ideal demographic answers. Which redesign best fixes the screener itself?
Show the answer
Answer: b · Replace guessable questions with behavioral ones about real tasks and add exclusion criteria for frequent panelists and IT professionals
The correct answer pairs behavioral validation (asking about specific recent tasks that are hard to fake) with explicit exclusion criteria (blocking habitual panelists and IT professionals), which structurally redesigns the screener to stop gaming. Option D is tempting because quotas and manual review feel like quality controls, but they fail to fix the screener upfront and do not validate genuine user behavior.
Read the full bite: What two techniques mitigate professional-tester bias in screener design?
Question 11 of 30
Under the recommended design, what actually happens when a participant submits a verified GDPR deletion request?
Show the answer
Answer: a · The system authenticates the requester, then cascades erasure across the primary store, derived datasets, and processors, with a defined approach to backups, and logs fulfillment.
A compliant deletion workflow authenticates the request and cascades erasure through the primary store, derived data, and processors, logging fulfillment. Option B is the one-off, single-table edit the card explicitly names as a wrong answer because it misses copies in analytics, exports, and backups.
Read the full bite: Build a compliant participant recruitment database
Question 12 of 30
Which combination of tools and logic is most appropriate for maintaining participant engagement across a two-week diary study?
Show the answer
Answer: c · Calendly scheduling, cascading reminders via Zapier, and automated no-show rebooking flagged in Airtable
A scalable diary study requires an orchestrated pipeline with self-scheduling, cascading reminders, and automatic no-show rebooking to manage longitudinal complexity. Option D is tempting because Google Forms is a common research tool, but a single static email cannot handle the repeated touchpoints and scheduling logic required for retention.
Read the full bite: Describe a workflow to automate a 50-person diary study
Question 13 of 30
Which strategy best balances effective reach and validity when recruiting a rare user population?
Show the answer
Answer: d · Target niche channels, use snowball referrals, and verify with behavioral screeners plus anti-fraud checks
The card prescribes a four-part pipeline of niche outreach, snowball sampling, behavioral screeners, and anti-fraud checks. Option B is tempting because niche communities are correct, but a demographic questionnaire relies on superficial self-report rather than behavioral verification.
Read the full bite: Propose a strategy for finding and vetting low-incidence participants
Question 14 of 30
After clustering user interview quotes into themes by frequency and severity, what is the next critical step before writing user stories?
Show the answer
Answer: a · Reframe the themes into problem statements or Jobs-to-be-Done to avoid jumping to solutions.
Option A reflects the required problem-framing step that prevents premature solutioning. Option C is tempting because high-frequency themes feel actionable, but skipping framing risks building features that miss the underlying user need.
Read the full bite: Translate qualitative insights into user stories and requirements
Question 15 of 30
After months of design work, a participant confirms your solution meets their needs. What should you do during the session and synthesis to best mitigate confirmation bias?
Show the answer
Answer: a · Probe for exceptions, past workarounds, and breakdowns during the session, then triangulate the finding and invite a neutral reviewer to audit your synthesis.
Probing for exceptions and breakdowns during the session prevents you from accepting a confirming anecdote as proof, while triangulation and a neutral reviewer during synthesis protect against interpreting data to match your investment in the design. Option C is tempting because structured coding is rigorous, but asking only why the design fits deepens the confirming narrative rather than stress-testing it.
Read the full bite: How do you mitigate confirmation bias when a user validates your solution?
Question 16 of 30
When a journey map reveals a five-second checkout spinner, what should a senior engineer do first to find the technical root cause?
Show the answer
Answer: b · Correlate the reported friction with production logs and traces to identify backend bottlenecks at that journey stage.
The card emphasizes that the first step is to validate the mapped pain point by correlating it with production logs, traces, and metrics to identify backend bottlenecks. Option C is a UI-only fix, Option D dismisses the finding as anecdotal, and Option A proposes architecture changes without first isolating the specific bottleneck.
Read the full bite: How would you use a journey map to find technical root causes?
Question 17 of 30
In the discount code example, users never applied a promo code because the field was collapsed by default. What kind of usability failure was this, and how was the diagnosis confirmed?
Show the answer
Answer: b · A discoverability failure, confirmed by session recordings showing users never found the collapsed field, corroborated by near-zero clicks in telemetry.
The card labels this a discoverability failure because users never located the collapsed control at all, confirmed by both recordings and near-zero click telemetry. An interaction failure (option C) would mean they found the control but struggled to operate it, which is not what happened.
Read the full bite: Diagnose and validate a failing usability task
Question 18 of 30
When comparing two APIs for usability, which approach best reveals whether developers will succeed with them in production?
Show the answer
Answer: c · Observing developers complete real tasks using each API with matched IDE and docs
The correct answer is B because API usability is defined by the total experience in realistic tooling and documentation contexts, not by signatures alone. A is tempting because naming review feels rigorous, but it ignores the actual developer workflow and surrounding support system.
Read the full bite: How could you adapt usability testing principles to evaluate two API designs?
Question 19 of 30
You observe a statistically significant drop in a core usability metric after a release. What should you do before pulling engineering resources?
Show the answer
Answer: d · Launch a small qualitative study to diagnose root cause while triaging by task criticality
Quantitative metrics reveal what changed but rarely why, so you should triage by the task's business criticality and run a small qualitative study to find root cause before shifting engineering priorities. Escalating every regression to P0 is a red flag because priority must match both the magnitude of the shift and the task's importance.
Question 20 of 30
Which design best enables accurate reconstruction of a user's cross-session cancellation path while maintaining query performance at scale?
Show the answer
Answer: c · An append-only event stream with session IDs and timestamps, stored separately from daily snapshot tables, and physically sorted by user and time
The correct approach separates immutable behavioral events from versioned entity state and optimizes physical layout for time-series scans, enabling precise path reconstruction. Option B is tempting because immutability is correct, but omitting session IDs and storage-layer ordering forces analysts to guess boundaries and sacrifices query performance.
Read the full bite: How would you model user events to analyze cancellation paths?
Question 21 of 30
When designing an A/B test to measure how API latency impacts D7 retention, which setup best isolates causality?
Show the answer
Answer: d · Bucket users by user ID, inject a consistent server-side delay per bucket, and track D7 retention alongside P99 latency
User-level randomization with consistent server-side delays ensures the only systematic difference between groups is the injected latency, establishing causality. Comparing historical slow versus fast requests is confounded by variables like device type or network quality, so retention differences cannot be attributed solely to latency.
Read the full bite: How would you design an experiment measuring API latency impact on retention?
Question 22 of 30
During thematic analysis, when should a cluster of coded observations be elevated to a high-level theme?
Show the answer
Answer: b · When related findings emerge repeatedly across different participants or data sources
A theme must be grounded in patterns that appear across multiple participants or data sources, not in the volume of a single voice or in memorable anecdotes. Choosing based on vivid quotes or personal hypotheses reflects the superficial, impressionistic analysis that thematic analysis is designed to prevent.
Read the full bite: How do you synthesize low-level codes into high-level themes?
Question 23 of 30
Which sequence best describes a rigorous process for reconciling significant qualitative coding differences?
Show the answer
Answer: d · Quantify disagreement, hold a consensus session on discrepancies, revise the codebook, and pilot on a new sample
Rigorous reconciliation requires quantifying divergence, discussing discrepancies to identify root causes, refining the codebook, and piloting revisions on a new sample before full coding. Option C is tempting because re-coding feels like progress, but it wastes effort by failing to fix the ambiguous definitions that caused the disagreement.
Read the full bite: What is your process for reconciling significant coding differences?
Question 24 of 30
Which scenario best demonstrates that thematic saturation has been reached under Guest et al.'s framework?
Show the answer
Answer: a · After a base of twelve interviews, three consecutive sessions yield only sub-codes and examples under existing high-level themes with no new top-level codes.
Guest et al. define saturation as a Run Length of consecutive interviews that add only sub-variants to existing high-level themes after a Base Size. The fixed rule of fifteen interviews is a tempting but incorrect shortcut because it never empirically checks whether new themes are still emerging.
Read the full bite: How do you determine when you've reached thematic saturation?
Question 25 of 30
An unexpected theme emerges during analysis of interview transcripts. Under what condition is it appropriate to formally expand the project scope to include it?
Show the answer
Answer: c · When the theme is supported by multiple participants and stakeholder buy-in can be secured
The card states that scope expansion requires first verifying recurrence across sources and then obtaining stakeholder buy-in through a formal change process. Option A reflects the red flag of chasing unvalidated themes immediately, while D repeats the common error of treating a single vivid quote as a credible pattern.
Read the full bite: How do you handle a powerful emergent theme outside original research questions?
Question 26 of 30
An A/B test on a new checkout flow reports a 95% confidence interval of -1% to 7% lift. What is the correct interpretation?
Show the answer
Answer: c · The interval spans zero, so the result does not rule out no effect or a small harm, and the wide range signals more data is needed before deciding.
The interval crosses zero, so the true effect could be a small loss or as much as a 7% gain, meaning the data does not support a confident decision either way. Option A is the classic frequentist misreading the card warns against, treating the interval as a probability statement about this one range.
Read the full bite: Confidence intervals versus p-values, explained simply
Question 27 of 30
A PM asks how many users to survey. Which response shows a senior engineer's approach?
Show the answer
Answer: d · First clarifying if a census or sample is needed, then probing population, design, budget, and power constraints
The correct approach treats sample size as a systems tradeoff that depends on census versus sample intent, study design, resources, and statistical power. The rule-of-thumb distractor is tempting because it offers a quick concrete number, but it completely ignores scope and business context.
Question 28 of 30
When an A/B test evaluates twenty success metrics independently at α = 0.05, what happens to the chance of at least one false positive?
Show the answer
Answer: d · It rises substantially above 5% as the family-wise error rate increases
Testing many metrics inflates the family-wise error rate, so the probability of at least one false positive grows well beyond the nominal 5%. Option C is tempting because each individual test does use α = 0.05, but that ignores the accumulation of error across the family of tests.
Read the full bite: What is the multiple comparisons problem in UX research?
Question 29 of 30
Analytics show high checkout abandonment, but interviews reveal users feel confident. What is the strongest first step to reconcile these findings?
Show the answer
Answer: d · Check whether the analytics and interviews define abandonment, time periods, and tasks the same way
The first step is to audit for methodological alignment by comparing definitions, scope, and timing, because the conflict may stem from mismatched metrics rather than contradictory truths. Launching a follow-up survey is tempting but premature: you should first determine whether the datasets actually measure the same behavior before scaling validation.
Read the full bite: How do you reconcile conflicting qualitative stories with quantitative data?
Question 30 of 30
Which architectural approach best distinguishes a queryable research repository from a siloed flat file dump when unifying heterogeneous UX artifacts?
Show the answer
Answer: b · Designing a unified metadata schema that links insights, transcripts, and source data through persistent identifiers
A unified metadata schema with persistent identifiers forms the storage layer that explicitly links insights to heterogeneous evidence, enabling faceted cross-type search and traceability. Option A seems organized but is essentially a flat file dump without structured relationships, which is a key red flag.
Could you explain these out loud?
That is what an interview actually tests. Tezvyn gives you questions like these with what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.