Intermediate everything in UX Research, page 2
Client-side versus server-side A/B testing
Client-side flickers and is bypassable; server-side assigns before response, hides logic, suits backend changes.
Recruiting channels for a B2C usability study
Compare panels for speed versus in-product intercepts for authenticity, weigh cost, screening rigor, and bias.
Turning a vague onboarding goal into research questions
Define success metrics, decompose the funnel, pair quantitative drop-off with qualitative why.
Why A/B-only, no upfront research, costs engineers more
A/B testing optimizes within a chosen direction but cannot reveal the right problem; building wrong wastes engineering cycles and tech debt.
Generative versus evaluative research in sprints
Generative explores problems before building and feeds requirements; evaluative tests solutions during and after build and feeds fixes.
Confidence intervals versus p-values, explained simply
Define a CI as a plausible range for the true effect with its precision, contrast it with a binary p-value, and read [-1%, 7%] as inconclusive because it spans zero.
Diagnose and validate a failing usability task
Pinpoint the failure step from session and telemetry data, form a root-cause hypothesis, ship a targeted fix, and re-test to validate.
Build a compliant participant recruitment database
Capture granular, timestamped consent with lawful basis; minimize, encrypt, and retention-limit storage; and build self-service deletion that cascades.
Anonymization vs pseudonymization and key handling
Anonymization is irreversible and exits GDPR scope; pseudonymization is reversible via a separated key; secure that key in a KMS with strict access.
Exposure Hours
Exposure hours measure the time each team member spends directly observing real users. Research by UIE found teams that watch users at least two hours every six weeks make markedly better design decisions, because firsthand empathy beats secondhand reports.
Mental Model Diagram
A mental model diagram aligns what users think and do, gathered from research, against what a product actually offers, exposing gaps where features are missing or unused so teams build for real behavior rather than assumptions.
How would you track clicks on a new 'Export Data' button?
Tests prod analytics design beyond console.log. Outline: typed event schema, client validation, beacon or queue with batching, and queryable storage. Red flag: fire-and-forget tracking without retry, sampling, or privacy checks.
Outline a research plan to diagnose low adoption despite positive usability tests
Tests distinguishing usability from adoption drivers. Strong answers hypothesize discoverability, motivation, and timing gaps; use behavioral triangulation, contextual inquiry, and surveys. Red flag: blaming users or redesigning before diagnosing the funnel.
How would you secure a moderated screen-sharing session end to end?
Cover encrypted WebRTC transport, KMS-backed storage, access controls, PII redaction, and retention policies.
UX researcher finds usability issues in your feature. Your process?
It tests triaging qualitative UX feedback with telemetry and cross-functional collaboration. Reproduce the issue, correlate with logs, isolate UI or backend causes, then co-design a fix via prototype or A/B test.
Design metadata and data structure for a searchable research repository
Tests structuring qualitative data for search and reuse. A strong answer uses linked tables for studies, participants, insights, and clips, with fields for date, method, theme tags, and severity.
How do you proactively collaborate with a researcher before a complex study?
This tests cross-functional partnership. A strong answer hits four things: share system boundaries, align on research goals via mutual education, scope the study for tangible user impact, and reframe methods into accessible language.
How do you break down an abstract UX solution into shippable stories?
This tests translating vague UX research into incremental delivery. A strong answer uses story mapping with UX and Product to find thin vertical slices that reduce confusion, validating each increment.
Describe the technical setup and trade-offs of large-scale unmoderated checkout usability testing
Clickstream logging, success rates, surveys; contrast speed with moderator engagement.
How can an engineer contribute to UX research with limited user access?
Treating UX research as a team sport using engineering assets when participants are scarce. Answers cover: mining logs for proxies; prototyping with internal experts; leveraging sales for intros.
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