Covers end to end planning, design, and operationalization of user research studies and the concrete skills needed to collect and analyze user data. Candidates should be able to define research goals and hypotheses tied to product or business objectives; select appropriate qualitative and quantitative methods such as user interviews, contextual inquiry, diary studies, ethnographic observation, moderated and unmoderated usability testing, prototype testing, card sorting, surveys, cohort and analytics analysis, heatmap and session recording review; design screening criteria and sample size and recruitment strategies; create moderation guides, scripts, and test tasks; run studies in person and remotely; capture, transcribe, and code observations; apply analysis techniques such as thematic coding, affinity mapping, triangulation, and basic statistical checks; synthesize findings into artifacts such as personas, user journeys, jobs to be done, pain points, and prioritized recommendations; surface limitations and bias and validate findings; practice ethical research including informed consent and data privacy; and manage operational constraints such as timeline, budget, and participant access. For senior candidates include designing research strategies, defining appropriate power and sampling trade offs, creating reproducible study templates and processes, mentoring others, and describing how research choices and analysis techniques informed product or documentation decisions.
HardTechnical
31 practiced
You must recruit enterprise users for research but have a very small pool of target customers who are busy and reluctant to participate. Propose a comprehensive recruitment plan including stakeholder-assisted recruitment, incentives, proxy strategies (when appropriate), data-sharing/legal considerations, and methods to mitigate sample bias and small-n limitations.
Sample Answer
**Approach summary (one-liner)** I’d run a multi-channel, stakeholder-enabled recruitment plan that combines prioritized outreach, high-value incentives, proxy sessions where valid, strict legal safeguards, and research techniques to reduce bias and maximize learning from small-N studies.**Stakeholder-assisted recruitment** - Partner with sales/CS/account managers to identify and warm-introduce busy contacts; provide email templates, 1‑pager value pitches, and calendar links. - Align with product/exec sponsors to authorize “time-limited advisory” invitations where participation is framed as strategic influence. - Offer internal champions reporting (short debriefs) to show business value and close the loop.**Incentives & logistics** - High-value, relevant incentives: credits, consulting hours, or product roadmap previews. - Short, flexible formats: 30-min remote interviews, asynchronous diary tasks, or on-site shadowing bundled with customer meetings. - Offer scheduling convenience: reverse-calendar invites, concise agendas, and opt-in recordings/transcripts.**Proxy strategies (when appropriate)** - Use proxies (power users, implementers, partners) only for tactical tasks not requiring end-user context; validate proxy findings later with one or two core customers. - Context-mapping sessions with proxies + artifact review to approximate enterprise workflows.**Data-sharing & legal** - Use NDAs and one-page consent; coordinate with legal for minimal-risk data capture. - Anonymize and aggregate outputs; provide customers control over quotes and screenshots.**Mitigating bias & small-n limits** - Triangulate: combine qualitative sessions, analytics, support tickets, and sales interviews. - Use rapid iterative cycles (n=3–6) with different customers, focusing on depth, not breadth. - Document limitations, confidence levels, and run validation checkpoints (A/B tests, pilots) before broad changes.I’d present a 6-week plan with expected outputs, risks, and fallback proxy steps so stakeholders can approve quickly.
MediumTechnical
39 practiced
Describe a structured approach to analyze heatmaps and session recordings so you surface true usability issues and avoid common misinterpretations (e.g., false positives from accidental clicks). Include how you'd combine these findings with quantitative funnel metrics and qualitative interview quotes.
Sample Answer
**Approach overview (why this matters)** I treat heatmaps and session recordings as hypothesis-generating tools, not proofs. My goal is to triangulate behavior with funnel metrics and user quotes to surface real usability issues and avoid false positives.**Step 1 — Prep & segmentation** - Define goal (e.g., checkout completion). - Segment by device, traffic source, new vs returning, and high-exit vs converted sessions to avoid mixing behaviors.**Step 2 — Heatmap analysis (patterns, not pixels)** - Inspect click, move, and scroll maps by segment. - Look for clustering, repeated non-CTA clicks, or unexpected dead zones. - Apply thresholds (e.g., >5% of segment clicking same spot) to reduce noise.**Step 3 — Session recording triage** - Prioritize sessions from users who dropped out at a funnel step or had errors. - Watch multiple sessions to confirm reproducible friction (not single accidental taps). - Note timing, repeated attempts, rage clicks, and context (form validation, loading).**Step 4 — Correlate with quantitative metrics** - Map heatmap findings to funnel drop-off rates and conversion trends. - Use event timestamps to link recordings to analytics events (errors, JS exceptions). - If a hotspot aligns with a spike in abandonment or error events, it’s higher priority.**Step 5 — Add qualitative evidence** - Pull relevant interview quotes or usability test transcripts that mention confusion about the element/flow. - Use quotes to explain intent and mental models behind observed actions.**Step 6 — Synthesize & recommend** - Create a short report: observation, supporting heatmap/data, 2–3 recordings, related funnel metric, and verbatim user quote. - Recommend low-effort validation (A/B test, instrumented prototype, moderated usability test) before full redesign.**Edge cases & safeguards** - Filter out bot traffic, accidental mobile taps, and outliers. - Always seek multiple converging signals (heatmap + recordings + funnel + quote) before labeling an issue as systemic.
MediumTechnical
39 practiced
You need to calculate how many users are required for an A/B test to detect a 10% relative uplift in conversion. Baseline conversion is 20%, alpha=0.05, power=0.8. Explain (a) how you would estimate required sample size conceptually, (b) what additional information you'd need, and (c) alternatives if the calculated sample size is unachievable in the short term.
Sample Answer
**(a) Conceptual approach — how I'd estimate sample size**I’d frame it as a power calculation: starting from the baseline conversion p0 = 20%, the minimum detectable effect is 10% relative → absolute uplift p1 = 0.20 * 1.10 = 0.22 (2 percentage points). Using standard two-sample proportions power formula (alpha = 0.05, power = 0.8) I’d compute the required N per group so the test has an 80% chance to detect that 2pp difference. Practically I’d use a stats package or online calculator to avoid manual errors.**(b) Additional information I’d need**- One- or two-tailed test (usually two-tailed unless direction is certain)- Whether allocation is 50/50 or uneven- Expected variance from historical data (daily/weekly conversion stability)- Duration constraints (traffic per day) and any segmentation (mobile vs desktop)- Whether to correct for multiple comparisons**(c) Alternatives if sample size is unachievable**- Increase minimum detectable effect (accept larger MDE) and justify trade-off- Run the test longer or throttle traffic allocation- Use sequential methods (group sequential or Bayesian A/B testing) to stop early- Improve measurement sensitivity (reduce noise by better tracking, limit segments)- Run qualitative tests or usability studies to iterate before full-scale experimentAs a UX designer I’d communicate trade-offs to PM/engineers and propose a mix of smaller experiments and qualitative research to move forward while statistical power is achieved.
EasyTechnical
34 practiced
Given interview notes and usage logs from small businesses using an invoicing tool, describe how you'd create three personas and what behavioral metrics or qualitative signals you'd use to differentiate them. Also explain how you'd avoid stereotyping when turning patterns into personas.
Sample Answer
**Approach summary**As a UX designer I’d synthesize interview notes + usage logs into evidence-backed personas by combining quantitative behavioral metrics with qualitative signals from interviews.**Three personas (example)**1. **"Busy Bookkeeper"**- Behavioral metrics: logs show daily invoice batch creation, high use of templates, low use of help pages.- Qualitative signals: interview quotes about time pressure, values keyboard shortcuts and bulk actions.2. **"Occasional Freelancer"**- Metrics: infrequent sessions, few advanced features used, invoices drafted then abandoned.- Signals: mentions limited billing knowledge, prefers mobile and simple defaults.3. **"Growing Small Biz Owner"**- Metrics: increasing monthly invoices, frequent customer segmentation, integrates payments and reports.- Signals: concerned about cash flow, asks about automation and reporting.**Signals to differentiate**- Frequency & session length, feature touchpoints (create/edit/send), abandonment rates, time-to-pay; plus interview themes, goals, frustrations, business context.**Avoiding stereotyping**- Base personas only on clustered data + multiple quotes; validate prototypes with users from each cluster; keep personas flexible (avoid demographics-only labels); document confidence levels and counterexamples; iterate personas when new data contradicts assumptions.
EasyTechnical
60 practiced
You will run a moderated usability test of a new e-commerce checkout flow. Draft a concise moderation guide skeleton that includes: pre-session steps, intro and consent script, 4–6 realistic tasks (with success criteria), probe questions, and debrief questions. Highlight how you'd handle think-aloud prompting without leading participants.
Sample Answer
**Pre-session steps**- Confirm participant, device, browser; send calendar + instructions.- Set up recording, screen share, note-taker, prototype build.- Test audio/video; have consent form ready; prepare incentive.- Timebox: 45 minutes (5 intro, 30 tasks, 10 debrief).**Intro & consent script**- “Hi, I’m [Name], UX Designer. Thank you. Today we’ll test a new checkout flow. This is not a test of you — it’s of the design. We’ll record screen/audio; recordings used for research only. You can pause or stop anytime. Do you consent to participate and be recorded?” (obtain verbal/checked consent)**Tasks (4–6) — realistic + success criteria**1. Create account and save shipping address. - Success: account created, address stored in profile.2. Find a medium-priced running shoe in size 9 and add to cart. - Success: correct product, size selected, added to cart.3. Apply a promo code and choose expedited shipping. - Success: promo accepted, shipping method changed, price updates.4. Complete checkout using saved card and request gift receipt. - Success: order placed, confirmation shown, gift receipt option selected.5. Cancel order from order confirmation page (optional). - Success: cancellation option visible and confirmed.**Probe questions**- What were you expecting to happen here?- What made you choose that option?- Was anything confusing or surprising?- How would you describe this step to a colleague?**Debrief questions**- Overall impressions? Biggest friction?- Anything you liked or would change?- How likely to use this site vs competitors? Why?**Think-aloud prompting (non-leading)**- Encourage neutral prompts: “Please keep talking about what you’re thinking.” - If silent: “What are you looking at now?” or “What are you expecting to happen next?” - Avoid suggesting actions or outcomes (don’t say “Try clicking X” or “Does this button seem confusing?”). - Reflect back neutrally: “I noticed you paused — what are you considering?”
Unlock Full Question Bank
Get access to hundreds of User Research Methods and Execution interview questions and detailed answers.
