Intermediate interview questions in UX Research, page 4
Checking if a 5% A/B lift is significant
State hypotheses, check predetermined sample and power, run the right test for the metric, read p-value and confidence interval.
Comparing skewed task-time data without a t-test
T-test assumes normality and is mean-sensitive to outliers; use Mann-Whitney U on ranks; trade-off is it tests distribution shift, not means.
Using personas to drive technical decisions
Derive constraints like device, network, accessibility from personas; let them shape framework, payload shape, performance budgets.
Extracting actionable insights from a long report
Start with executive summary and recommendations, trace findings to evidence, filter for engineering-actionable items, confirm with the researcher.
Instrumenting a feature to validate a qualitative insight
Restate the pain as a hypothesis, define a primary behavioral metric plus guardrails, instrument events, compare against baseline.
Re-evaluating personas when engagement is low
Bring behavioral evidence, separate persona-wrong from execution-wrong, propose joint research to validate or invalidate.
Automating research participant recruitment and scheduling
Screener intake, eligibility matching, calendar booking, notifications, incentive payout; handle no-shows and idempotency.
Privacy compliance in a participant management system
Versioned consent records, data classification and minimization, anonymization or pseudonymization, deletion workflow across stores and backups.
Architecting a multi-tenant ResearchOps platform
Tenant isolation model, RBAC plus governance and classification, searchable metadata and a taxonomy for cross-team synthesis.
Tracing a research insight to shipped code
Give insights stable IDs, link them through tickets to commits and feature flags via tool integrations, measure outcome metrics.
Defining and instrumenting UX KPIs for a feature
Tie KPIs to user goals via a framework like HEART, define events before building, validate tracking pre-launch.
Scaling one researcher across three squads
Triage by impact, enable democratized research with guardrails, build reusable templates and a shared repository.
Translating a Job Story into mobile features
Decompose situation, motivation, expected outcome; map commute constraints to offline, audio, quick-scan features.
Fixing text overflow from long localized labels
Avoid fixed widths, use flexible layouts, allow wrapping or word-break, ellipsis as last resort, pseudo-localize to test.
How to diagnose and fix ignored sidebar navigation?
Form testable hypotheses (contrast, layout, blocking), propose specific CSS/DOM changes, sketch A/B test plan.
Making D3.js visualizations accessible to screen readers?
Dual-render strategy (viz + semantic table), ARIA live regions for dynamic updates, keyboard event handlers, focus management.
How to sync eye-tracking data with DOM events?
Record gaze points with millisecond precision, map to DOM via bounding box lookup, correlate with click events via shared timestamp.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles