Top 30 UX Research Interview Questions and Answers

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.

1. Question 1 of 30

   You must validate a new feature concept without a researcher and before writing production code. Which approach best balances speed and rigor?

   • aConduct a formal moderated usability study with 12 participants over two weeks to comprehensively evaluate behavioral and attitudinal data.
   • bRun an unmoderated concept test with a low-fidelity prototype, recruiting target users in-app and measuring task success and perceived value against a preset threshold.
   • cShip a lightweight MVP behind a feature flag and run an A/B test to compare engagement metrics against a control group.
   • dGather feedback from internal stakeholders and analyze support tickets to validate demand without recruiting external participants.
   Show the answer

   Answer: b · Run an unmoderated concept test with a low-fidelity prototype, recruiting target users in-app and measuring task success and perceived value against a preset threshold.

   B is correct because unmoderated concept tests with prototypes gather both behavioral and attitudinal signals quickly without production code or dedicated research staff. A is the most tempting distractor because A/B testing feels rigorous, but it requires committing production code before validation, which defeats the purpose of lightweight de-risking.

   Read the full bite: Describe a lightweight research method to validate a feature with no researcher

2. Question 2 of 30

   Which plan best demonstrates rigorous instrumentation to validate a qualitative behavioral insight?

   • aCapture all page views and clicks in a dashboard, then search for patterns that match the interview themes
   • bDeploy a post-launch NPS survey to users who encountered the feature and compare scores against a benchmark
   • cMap qualitative themes to specific product events, define success and guardrail metrics, and compare the target cohort against a holdback with a preset minimum detectable effect
   • dRun an A/B test exposing the feature to 50% of all users and declare validation if the treatment group shows higher engagement
   Show the answer

   Answer: c · Map qualitative themes to specific product events, define success and guardrail metrics, and compare the target cohort against a holdback with a preset minimum detectable effect

   The correct approach requires traceability from themes to events, paired success and guardrail metrics, and a predefined analysis plan with a holdback cohort. Option D is tempting because A/B testing sounds rigorous, but testing the general population without linking metrics to specific qualitative themes or defining statistical power fails to validate the original insight.

   Read the full bite: How would you instrument a feature to validate qualitative findings quantitatively?

3. Question 3 of 30

   Which implementation best satisfies GDPR for informed consent before a remote usability test?

   • aAllow the test to initialize immediately and prompt for consent during the first task
   • bPlace a privacy policy link in the footer and start the session, treating continued use as consent
   • cUse a CMP to collect active consent, record it server-side, and gate the test interface until consent is confirmed
   • dPresent a consent banner but store the decision only in browser storage while the test loads
   Show the answer

   Answer: c · Use a CMP to collect active consent, record it server-side, and gate the test interface until consent is confirmed

   The correct approach requires active consent via a CMP, server-side recording for auditability, and blocking test access until consent is granted. A tempting distractor stores consent only in browser storage, which can be altered after the fact and lacks a verifiable server-side record.

   Read the full bite: Implement verifiable informed consent before a remote usability test

4. Question 4 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?

   • aProbe for exceptions, past workarounds, and breakdowns during the session, then triangulate the finding and invite a neutral reviewer to audit your synthesis.
   • bRecord the confirmation and avoid challenging the participant to preserve rapport, then scrutinize the finding during synthesis by comparing it with other sessions.
   • cAsk follow-up questions about why the design fits their workflow so well, then use a structured coding framework during synthesis to compare this session with others.
   • dTreat the participant's validation as reliable proof the design is correct, especially if it supports business goals to ship quickly.
   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?

5. Question 5 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?

   • aA comprehension failure, confirmed because users clicked the field but typed invalid codes.
   • bA discoverability failure, confirmed by session recordings showing users never found the collapsed field, corroborated by near-zero clicks in telemetry.
   • cAn interaction failure, confirmed because users clicked the field repeatedly without success.
   • dA feedback failure, confirmed because users applied the code but could not tell whether it worked.
   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

6. Question 6 of 30

   When reviewing coded interview transcripts, what indicates that a code should be promoted to a theme?

   • aIt represents a pattern seen across multiple participants rather than a one-off observation
   • bIt appears frequently within a single participant's transcript
   • cIt is supported by a vivid, detailed quote that clearly illustrates the participant's perspective
   • dIt matches the researcher's initial hypotheses about what the study would find
   Show the answer

   Answer: a · It represents a pattern seen across multiple participants rather than a one-off observation

   The card emphasizes that a theme emerges only when the same belief or behavior appears multiple times across participants or data sources. A vivid quote from one participant is a tempting distractor because the card explicitly warns against letting a single memorable detail drive a finding.

   Read the full bite: Explain coding in qualitative analysis and your codebook process

7. Question 7 of 30

   Which practice best establishes an auditable evidence chain when tracing qualitative data to journey map stages?

   • aInviting engineers to review a structured repository that indexes raw quotes and observations against specific stages and pain points
   • bTreating the map as a finalized deliverable once the exploratory research phase is complete
   • cValidating stages primarily through quantitative drop-off rates and NPS score correlations
   • dDefending stage definitions by citing the researcher's synthesis expertise and interview volume
   Show the answer

   Answer: a · Inviting engineers to review a structured repository that indexes raw quotes and observations against specific stages and pain points

   The correct answer reflects the card's emphasis on a traceability matrix and collaborative verification with technical stakeholders. Option C is tempting because quantitative metrics identify where problems occur, but the card explicitly warns that drop-off rates and NPS scores alone cannot validate qualitative stage meanings or provide inspectable customer evidence.

   Read the full bite: How do you trace data points to journey map stages?

8. Question 8 of 30

   After user research, a team prepares insight statements for the define stage. Which approach best aligns with their purpose?

   • aReframing 'needs a dashboard' into 'needs to monitor trends' before brainstorming
   • bDrafting statements that specify UI components to reduce ambiguity for developers
   • cFinalizing statements as sprint requirements to hand off to engineers
   • dPrioritizing needs by technical feasibility to narrow scope before ideation
   Show the answer

   Answer: a · Reframing 'needs a dashboard' into 'needs to monitor trends' before brainstorming

   Insight statements deliberately frame needs as verbs (monitor) rather than solutions (dashboard) to keep the design space open before ideation. Option B incorrectly inserts solutions, while D confuses the statement with a delivery artifact.

   Read the full bite: Insight Statements: Frame Problems, Not Solutions

9. Question 9 of 30

   In a mental model diagram, one cluster of user behaviors in the top half has no product features aligned beneath it, while elsewhere a feature sits below the line with no behavior above it. What do these two situations respectively reveal?

   • aThe first is an opportunity gap, a real need nothing is built for; the second is a feature that may be waste, since no observed behavior supports it
   • bThe first indicates a data collection error requiring re-interviews; the second indicates the feature just needs better marketing copy
   • cThe first means the feature is hidden in a nested tower and just needs relocating; the second means the behavior was mislabeled
   • dBoth situations only mean the interview sample size was too small to draw any real conclusion
   Show the answer

   Answer: a · The first is an opportunity gap, a real need nothing is built for; the second is a feature that may be waste, since no observed behavior supports it

   An unsupported behavior cluster is an opportunity gap, a real need with nothing built for it, while a feature with no behavior above it is a candidate for cutting since no observed need supports it. Neither gap is about sample size or mislabeling, they are exactly the alignment gaps the diagram exists to expose.

   Read the full bite: Mental Model Diagram

10. Question 10 of 30

    An A/B test returns a p-value of 0.03. Which statement accurately describes its meaning under the null hypothesis?

    • aThere is a 97% probability that the variant is genuinely better than the control.
    • bThere is a 3% probability that the null hypothesis of no effect is actually true.
    • cThere is a 97% probability that this result will replicate in a future experiment.
    • dIf the null hypothesis of no difference were true, we would observe a result at least this extreme about 3% of the time.
    Show the answer

    Answer: d · If the null hypothesis of no difference were true, we would observe a result at least this extreme about 3% of the time.

    A p-value of 0.03 means that if there were truly no difference between variants, random variation would produce a result this extreme roughly 3% of the time. It does not mean there is a 97% chance the variant is better, because the p-value describes the probability of the data under the null rather than the probability that the null is false.

    Read the full bite: Explain what a p-value represents in an A/B test and interpret 0.03

11. Question 11 of 30

    If you double the variance of a normal distribution while keeping the mean constant, what happens to the probability density curve?

    • aIt develops two distinct peaks on either side of the original mean
    • bIt shifts left or right so the peak moves away from the original mean
    • cIt flattens and widens while its peak remains at the original mean
    • dIt becomes taller and tighter around the original mean
    Show the answer

    Answer: c · It flattens and widens while its peak remains at the original mean

    The card explains that larger variance flattens and widens the curve while the mean alone shifts its horizontal position, so the bell spreads out around the same center. Option D is a tempting distractor because it reverses this relationship, describing the effect of decreasing variance rather than increasing it.

    Read the full bite: Normal Distribution: Two Parameters, One Bell Curve

12. Question 12 of 30

    A journey map flags frustration at a slow search step. Before proposing a fix, what should be asked first to properly scope the problem?

    • aOnly how much engineering effort the fix will take, since that determines whether it is worth prioritizing.
    • bWhether the finding is anecdotal, and if so, whether it can be dismissed until quantitative data appears.
    • cWhat the final UI redesign should look like, so design and engineering can start building immediately.
    • dHow prevalent and severe the pain is, where in the stack it originates, and what success criteria would confirm the fix worked.
    Show the answer

    Answer: d · How prevalent and severe the pain is, where in the stack it originates, and what success criteria would confirm the fix worked.

    The three scoping questions cover prevalence and severity, technical origin, and success criteria, turning the pain point into a bounded, measurable problem. Option C, jumping straight to a UI redesign before knowing the cause, is the exact wrong answer the card warns against.

    Read the full bite: First technical questions to scope a journey-map pain point

13. Question 13 of 30

    When should you choose a t-test over a Z-test to compare two group means?

    • aWhen the two groups have markedly different variances or non-normal shapes
    • bWhen the population standard deviation is unknown and must be estimated from the sample
    • cWhen the total sample size across both groups is smaller than 30
    • dWhen you want the exact probability that the null hypothesis is true
    Show the answer

    Answer: b · When the population standard deviation is unknown and must be estimated from the sample

    The t-test is designed for cases where the population standard deviation is unknown and estimated from the sample, while a Z-test requires it to be known beforehand. Option C is tempting but wrong because the choice depends on whether the standard deviation is known, not on an arbitrary sample-size cutoff.

    Read the full bite: T-test: Are Two Groups Actually Different?

14. Question 14 of 30

    Analytics show high checkout abandonment, but interviews reveal users feel confident. What is the strongest first step to reconcile these findings?

    • aAverage the abandonment rate with the confidence scores to create a single reconciled metric
    • bLaunch a follow-up survey to validate the confidence finding at scale before deciding
    • cTreat the interview findings as anecdotal edge cases and prioritize the abandonment metric
    • dCheck whether the analytics and interviews define abandonment, time periods, and tasks the same way
    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?

15. Question 15 of 30

    During a schema review, the interviewer notes that correcting a participant's email address requires updating multiple study records. Which design flaw produces this problem?

    • aStoring contact information in a separate participants table instead of alongside each study record
    • bRepeating static participant data across every row in a flat participation table
    • cReferencing participants by a participant_id foreign key rather than copying their email
    • dTracking participation history inside a JSON column within the participants table
    Show the answer

    Answer: b · Repeating static participant data across every row in a flat participation table

    Repeating static contact data in every study record violates first normal form and makes updates error-prone. Distractor D misidentifies the correct foreign-key design as the problem, when using participant_id is precisely what avoids duplication.

    Read the full bite: Design a database schema for a research participant panel

16. Question 16 of 30

    Which architectural practice distinguishes an intentionally unified mixed-methods study from a superficial merge of siloed data?

    • aEstablishing shared research questions and user identifiers upfront while linking quant struggles to qual tasks by session
    • bRunning parallel independent studies and reconciling the findings during final reporting and presentation
    • cStoring both dataset types in a shared warehouse with unified schemas and access controls
    • dAppending a quantitative survey to qualitative interviews to capture numerical metrics alongside observational notes
    Show the answer

    Answer: a · Establishing shared research questions and user identifiers upfront while linking quant struggles to qual tasks by session

    True unification requires upfront alignment on shared goals and identifiers plus session-level linkage so quantitative patterns directly guide qualitative investigation. Simply warehousing both datasets in one repository stores them side by side without an intentional integration plan, which is a common misconception.

    Read the full bite: How would you architect a unified quantitative and qualitative user experience view?

17. Question 17 of 30

    A product team reads a thorough written research report each quarter summarizing usability sessions, but no one besides the researcher who ran them ever watches a session directly. Does this practice satisfy the exposure hours model?

    • aYes, because a well written report conveys the same empathy benefit as watching a session directly, since the underlying facts are identical
    • bNo, exposure hours specifically requires direct observation of real users, live or recorded, from the whole team, not a secondhand report
    • cNo, because reports must be published weekly rather than quarterly for the team to accumulate exposure hours
    • dYes, as long as the researcher personally logs more than two hours, the rest of the team's exposure does not matter
    Show the answer

    Answer: b · No, exposure hours specifically requires direct observation of real users, live or recorded, from the whole team, not a secondhand report

    Exposure hours specifically means firsthand observation, live or recorded, from the whole team including engineers and managers, so a quarterly report is exactly the secondhand substitute the concept says does not build real empathy. Publishing cadence and one person's hours, the other wrong options, are beside the point next to that direct observation requirement.

    Read the full bite: Exposure Hours

18. Question 18 of 30

    A researcher interviewed twelve participants and found a checkout confusion theme raised by ten of them. Following the guidance on visualizing qualitative data honestly, how should this finding be presented?

    • aAs eighty three percent of all users experience checkout confusion, extrapolated from the interview sample
    • bAs a statistically significant result with a ninety five percent confidence interval, since ten data points is enough for significance testing
    • cAs ten of twelve interview participants raised the checkout confusion theme, framed as a count within the sample, not a population percentage
    • dThe finding should be left out of any visualization entirely, since a sample of twelve participants is too small to matter
    Show the answer

    Answer: c · As ten of twelve interview participants raised the checkout confusion theme, framed as a count within the sample, not a population percentage

    The honest framing states the count within the actual sample, ten of twelve participants, without implying a population statistic. Converting it into a percentage of all users or a confidence interval, as in the first two options, borrows quantitative authority the qualitative sample cannot support.

    Read the full bite: Data Visualization for Qualitative Data

19. Question 19 of 30

    In a dual-track agile model, how do generative and evaluative research relate to the sprint cadence?

    • aGenerative research must fully complete before any sprint work can begin, and evaluative research only happens after the product ships.
    • bGenerative research explores problems in a discovery track running ahead of and parallel to sprints, while evaluative research tests solutions during and after the build.
    • cBoth types of research happen only at the end of a sprint, differing only in whether they use quantitative or qualitative methods.
    • dEvaluative research defines personas and journey maps to shape scope, while generative research ranks usability issues by severity after launch.
    Show the answer

    Answer: b · Generative research explores problems in a discovery track running ahead of and parallel to sprints, while evaluative research tests solutions during and after the build.

    Generative research runs in a discovery track ahead of and alongside sprints to find problems, while evaluative research tests solutions during and after the build. Option D inverts this by swapping which mode produces personas versus severity-ranked issues.

    Read the full bite: Generative versus evaluative research in sprints

20. Question 20 of 30

    A research director finds that skilled researchers produce excellent insights, yet recruitment, governance, and tooling are inconsistent across divisions. What should the ResearchOps Maturity Matrix diagnose?

    • aWhich divisions need additional research training to manage recruitment and privacy more effectively.
    • bWhether individual study quality and research methods are rigorous enough to support scaling.
    • cThe degree to which UX maturity and research adoption vary across the organization.
    • dGaps in the operational infrastructure governing participant pipelines, data protocols, and tooling strategy.
    Show the answer

    Answer: d · Gaps in the operational infrastructure governing participant pipelines, data protocols, and tooling strategy.

    The matrix audits operational infrastructure such as participant pipelines and governance, not the quality of insights or researcher skill. Although inconsistent recruitment and privacy practices might suggest a training gap, the matrix reveals that fragmented operational systems—not skill deficiencies—are the true bottleneck.

    Read the full bite: ResearchOps Maturity Matrix: Built for Operations

21. Question 21 of 30

    Engineering built exactly what an export-to-CSV ticket specified, but research shows users actually need scheduled recurring reports. What is the recommended way to open that conversation with the team?

    • aExplain that the team built the wrong feature and that the sprint's effort was largely wasted.
    • bPresent the session clips and user-need statement as the final verdict, then hand engineering a revised ticket to execute.
    • cAcknowledge the team delivered exactly what the ticket asked for, then frame the shared, imperfect requirement as the gap to solve together using the evidence.
    • dEscalate to the product manager who wrote the ticket, since the requirements gap is their responsibility to fix alone.
    Show the answer

    Answer: c · Acknowledge the team delivered exactly what the ticket asked for, then frame the shared, imperfect requirement as the gap to solve together using the evidence.

    The recommended approach opens by crediting the correct delivery, then frames the requirement gap as something the whole team owns, backed by evidence, before inviting engineering into solving it together. Option A directly blames the team for wasted effort, which the card says puts people on the defensive.

    Read the full bite: Spec met but user problem unsolved: facilitating the fix

22. Question 22 of 30

    Which markup pattern correctly gives a screen reader name to a button that contains only a decorative icon?

    • aPut aria-label on the button and aria-hidden="true" on the decorative icon
    • bApply aria-label to the SVG icon and omit it from the button
    • cAdd an alt attribute to the SVG icon describing the button's action
    • dUse a title attribute on the button to provide its accessible name
    Show the answer

    Answer: a · Put aria-label on the button and aria-hidden="true" on the decorative icon

    The interactive button—not the decorative icon—must expose the accessible name, so aria-label belongs on the button while aria-hidden prevents the icon from being announced separately. Alt text on SVG is unreliable for naming, and title is inconsistently announced and often inaccessible to keyboard users.

    Read the full bite: Which ARIA attribute fixes an icon-only button missing its screen reader name?

23. Question 23 of 30

    In a usability test, a beautifully designed signup form gets high satisfaction ratings even though 40% of participants fail to complete it due to unclear error messages. What does the aesthetics-usability effect predict is happening?

    • aThe attractive design is actually making the form objectively easier to complete despite the ratings
    • bParticipants are rating the form honestly, and satisfaction always tracks task completion rate
    • cThe high failure rate proves the aesthetics-usability effect does not apply to forms
    • dThe visual polish is raising participants' tolerance and satisfaction ratings, masking the real task failure problem
    Show the answer

    Answer: d · The visual polish is raising participants' tolerance and satisfaction ratings, masking the real task failure problem

    The card's own example shows attractive visuals inflating satisfaction scores while masking a real usability defect, exactly what the effect predicts. The tempting wrong answer assumes the pretty form is actually easier, when the whole point of the bias is that it only feels that way.

    Read the full bite: Aesthetics-Usability Effect

24. Question 24 of 30

    A web form accepts English usernames but silently drops Arabic characters from submissions. What does this failure most clearly indicate?

    • aThe underlying technology assumes a limited character set and fails to support the Arabic script
    • bThe Arabic translations need review by a native speaker
    • cThe form requires locale-specific marketing edits for Arabic-speaking users
    • dThe interface layout must be adjusted for right-to-left reading direction
    Show the answer

    Answer: a · The underlying technology assumes a limited character set and fails to support the Arabic script

    The card's canonical example shows that rejecting non-English characters reveals a technology limitation in script support, not a translation issue. Option B is tempting because Arabic text is involved, but translation review checks linguistic quality, not whether the system can process the script.

    Read the full bite: i18n Testing: Check Scripts, Not Just Strings

25. Question 25 of 30

    What is the primary purpose of localization testing after the localization phase is complete?

    • aTo confirm that the translated product fully accounts for cultural and regional differences beyond language conversion.
    • bTo verify that the underlying code base supports multiple languages and regional formats.
    • cTo perform the cultural adaptation and translation adjustments required for the target market.
    • dTo compensate for a lack of internationalization by identifying locale-specific bugs before release.
    Show the answer

    Answer: a · To confirm that the translated product fully accounts for cultural and regional differences beyond language conversion.

    Localization testing acts as a quality gate that validates whether the second phase truly addressed distinct market differences rather than stopping at translation. Distractor A is wrong because testing verifies adaptation; it does not perform the adaptation work itself.

    Read the full bite: Localization Testing Validates Regional Adaptation

26. Question 26 of 30

    A clinician uses Q-methodology to track a patient's recovery. Which interpretation best aligns with the method's intended purpose?

    • aComparing the patient's viewpoint against a normative population average to calculate an objective severity score
    • bIsolating individual opinions from the viewpoint to identify which specific belief is causing distress
    • cTracking changes in the patient's subjective stance over time to assess meaningful shifts in perspective
    • dUsing the captured viewpoint to verify whether the patient's beliefs about their health are medically accurate
    Show the answer

    Answer: c · Tracking changes in the patient's subjective stance over time to assess meaningful shifts in perspective

    Q-methodology treats the viewpoint itself as data to be studied as a coherent whole, so tracking subjective shifts over time is its proper clinical use. Option D is tempting but represents a fundamental misuse because the method is explicitly not designed to verify factual correctness or align perspectives with external reality.

    Read the full bite: Q-Methodology: Mapping Subjective Viewpoints

27. Question 27 of 30

    Research for a new market shows most users are on low-end Android phones with intermittent connectivity. What should this directly drive on the roadmap before any localized screen ships?

    • aA full UI redesign matching the home market's visual style, since devices and bandwidth are assumed to be similar everywhere.
    • bTranslating all existing strings into the local language, which is treated as sufficient for cultural adaptation.
    • cA single upfront research study, with no further evaluative research planned once the product has launched in the market.
    • dA stricter performance budget and offline caching work, alongside a local payment wallet integration and in-region hosting for data residency.
    Show the answer

    Answer: d · A stricter performance budget and offline caching work, alongside a local payment wallet integration and in-region hosting for data residency.

    Low-end devices and unreliable connectivity translate directly into a performance budget, offline caching, a local payment integration, and in-region hosting for data residency, all decided before a single localized screen ships. Option B, treating localization as translation only, is one of the card's named wrong answers.

    Read the full bite: Phased research strategy to de-risk market entry

28. Question 28 of 30

    A team skips upfront user research and instead A/B tests two checkout button colors. What is the real engineering-cost risk in this approach?

    • aA/B testing is fundamentally unreliable and should be replaced entirely by qualitative interviews before any feature ships.
    • bIt only optimizes the button color already chosen. If the real problem, like a hidden fee causing distrust, goes unaddressed, engineering may later rebuild the whole flow at far greater cost.
    • cThe button color test will fail to reach statistical significance no matter how long it runs, since color changes never produce measurable effects.
    • dUpfront research is only about user empathy, so skipping it has no real consequence for engineering timelines or cost.
    Show the answer

    Answer: b · It only optimizes the button color already chosen. If the real problem, like a hidden fee causing distrust, goes unaddressed, engineering may later rebuild the whole flow at far greater cost.

    A/B testing can only compare variants within a direction already chosen, so it can optimize button color while missing that the real problem, like a hidden fee, requires an expensive rebuild later. Option D wrongly claims upfront research has no engineering-cost consequence, when the card's whole argument is that skipping it risks exactly that cost.

    Read the full bite: Why A/B-only, no upfront research, costs engineers more

29. Question 29 of 30

    When user recruitment is slow, which approach best shows an engineer treating UX research as a shared responsibility?

    • aFocus on writing code and wait for the UX researcher to deliver findings before making technical trade-offs.
    • bParse application logs and partner with internal support staff to generate proxy insights for the researcher.
    • cRecruit five people from your personal network who use similar consumer apps to review the prototype.
    • dShip a basic version of the feature and use post-launch analytics to decide what needs refinement later.
    Show the answer

    Answer: b · Parse application logs and partner with internal support staff to generate proxy insights for the researcher.

    The correct answer demonstrates systems thinking by turning engineering artifacts and internal expertise into actionable proxy data when direct access is scarce. Option D is tempting because it sounds iterative and data-driven, but it commits the anti-pattern of shipping before understanding user needs and merely hoping to iterate later.

    Read the full bite: How can an engineer contribute to UX research with limited user access?

30. Question 30 of 30

    Which control most directly limits the blast radius if the SFU is compromised during a sensitive screen-sharing session?

    • aEnforcing a 90-day retention policy with cryptographic erasure of the decryption key
    • bWatermarking playback with the authenticated viewer's identity to deter leaks
    • cHashing the uploaded recording to verify integrity after network drops
    • dUsing WebRTC Insertable Streams so the SFU processes only ciphertext
    Show the answer

    Answer: d · Using WebRTC Insertable Streams so the SFU processes only ciphertext

    Insertable Streams provides true end-to-end encryption, ensuring a compromised SFU cannot decrypt sensitive media content. Retention policies and watermarks are important governance controls, but they do not prevent an SFU from accessing plaintext streams.

    Read the full bite: How would you secure a moderated screen-sharing session end to end?