Apply differential privacy to user behavior queries and explain epsilon trade-offs
Mastery of formal privacy guarantees and noise-based query systems. Inject Laplace or Gaussian noise scaled to query sensitivity; track cumulative epsilon across queries; lower epsilon tightens privacy but increases variance and error bars.
Design a centralized consent platform: core components and database schema
WHAT IT TESTS: immutable, auditable consent governance across jurisdictions. ANSWER OUTLINE: separate CMF from CMP; build an append-only ledger with versioned wording, per-activity granularity, and real-time revocation.
How do you fulfill a GDPR erasure request across data stores?
This tests cross-system deletion under GDPR's 30-day SLA. A strong answer maps PII lineage across S3, databases, and analytics; uses soft deletes for backups; and handles dashboards via reprocessing.
How would you instrument a feature to validate qualitative findings quantitatively?
WHAT IT TESTS: turning UX hunches into telemetry. A GOOD ANSWER COVERS: mapping themes to events, picking guardrail and success metrics, and sampling. RED FLAG: generic analytics with no traceability to the original insight.
Generative versus evaluative research: when to use each
WHAT IT TESTS: Knowing when to explore problems vs validate solutions by phase. ANSWER OUTLINE: Generative precedes design to find needs; evaluative follows a build to test it. RED FLAG: Treating research as one phase or saying testing only happens last.
How does UX research integrate into a two-week agile sprint?
This tests if you see research as ongoing discovery, not a predev phase. A good answer covers backlog work across sprints, outcome-based prioritization, and engineer touchpoints in refinement. Red flag: saying research happens only before coding starts.
Explain qualitative vs quantitative user data with engineering examples
WHAT IT TESTS: If you know qualitative is direct observation and quantitative is indirect measurement, plus engineering examples. ANSWER OUTLINE: Contrast the two modes and give one example per type. RED FLAG: Calling it open- versus closed-ended questions.
What is the primary purpose of UX research before starting development?
Tests if you see pre-dev research as risk reduction. Strong answer: it validates real user needs before code, exposes unknown requirements while changes are cheap, and avoids building for imaginary users.
Peer Review: Research's Blind Spot Check
Peer review is a blind spot check by qualified strangers who have no stake in your success. It keeps published research honest by catching flaws the author missed. The trap is treating publication as truth just because it survived review.
Centralized vs Decentralized UX Research Teams
Centralized UX works like an agency, loaning researchers to products and returning them to a resource pool; decentralized embeds UX in product teams. This matters when UX is added after engineering. The footgun is freezing structure rather than evolving it.
Informed Consent in UX Research
Informed consent is the ethical line between a casual chat and research abuse. Once you record, transcribe, or share participant data, you need explicit permission. The footgun is treating a friendly call as private when your notes permanently expose it.
Research Competency Matrix: Mapping Team Growth
A competency matrix maps craft and human skills against career stages to reveal gaps. Use it to plan hiring and align capabilities with organizational needs. The footgun is treating it as a rigid checklist instead of a customizable reflection tool.
ResearchOps Playbooks: Standardize UX Research
A ResearchOps playbook is your team's operating manual for repeatable research. It matters when multiple researchers recruit, analyze, and report across squads. The footgun is writing it once and letting it rot instead of treating it as a living process.
Research Socialization: Make UX Insights Visible
UX research only drives outcomes if people see it. Research socialization pushes insights beyond design and product teams to the wider business. When studies sit trapped in folders, strategy gets built blind.
Third-Party UX Recruiters: Methodological Bouncers, Not Body Shops
Third-party UX recruiters are quality filters, not just people finders. They validate participants fit your methodology, not demographic checkboxes. Use them when one wrong user corrupts a usability study.
Incidence Rate: The Recruitment Cost Multiplier
Incidence rate is the fraction of people who pass your screener. In UX research, a 5% rate means screening twenty people to interview one. Teams often forget to pre-filter panels by demographics they already know, burning budget on obvious rejections.
Executive-Level UX Research Communication
Executives fund outcomes, not observations. Frame research by business risk and revenue, not methods. This applies when you need budget or strategic alignment. The footgun is drowning leaders in process details that bury recommendations and stall action.
UX Research Staffing: The 1:5:50 Ratio
A 2020 industry survey found the most common UX team structure is one researcher for every five designers and fifty developers. These ratios signal staffing norms but should never replace measuring actual research impact or team maturity.
UX Maturity: Six Stages of Organizational UX
UX maturity maps how deeply user-centered design lives in an organization, from ignored to user-driven. It matters when scaling research or justifying headcount.
GSR: Tracking Emotional Arousal Through Skin Conductivity
GSR reads unconscious arousal via skin conductivity you cannot control. UX teams use it to surface stress during usability tests users underreport. It measures intensity, not valence, so a spike alone cannot distinguish delight from frustration.