User Research & Need Identification Questions

How do you identify and validate real user needs before committing design or product effort? Cover the research mindset: forming explicit assumptions up front, choosing between generative research (open-ended discovery of needs) and evaluative research (testing a specific solution), and picking qualitative versus quantitative methods based on the time and access you have. Include practical skills such as writing sharp research questions, designing screeners and recruitment criteria for representative participants, running rapid or time-boxed research (guerrilla testing, hallway tests, unmoderated remote studies) when timelines are tight, and distinguishing a user's stated need from their underlying goal or a solution they've proposed. Applies across interview formats: live time-constrained exercises, behavioral questions about past research work, and case-style discussions of how research should shape a roadmap or design decision.

EasyTechnical

68 practiced

You have 24 hours to learn about users before building a prototype. List five quick research methods you would choose, explain when each is most appropriate, and identify one key limitation for each method.

HardSystem Design

64 practiced

You're hired as Head of UX Research at a 200-person company with no standardized research processes. Design an organizational plan to embed continuous user research into product development: propose team structure, research ops roles and tooling, an intake and prioritization process, governance, and KPIs to measure impact.

Sample Answer

**Clarify goals & constraints**- Goal: embed continuous, lean user research across product lifecycle to reduce risk, accelerate learning, and improve UX metrics.- Constraints: 200 people, distributed teams, variable research literacy, limited budget to start.

**High-level org & team structure**- Head of UX Research (you) → Research Ops Manager, 3 Senior UX Researchers (embedded), 2 Research Associates, + rotating Design/PM liaisons.- Embedded model: each product squad (~6–8 squads) has a named Senior Researcher or shared cadence with Research Associates; centralized Research Ops for standards, tooling, recruiting.

**Research Ops roles & tooling**- Research Ops Manager: participant recruitment, repository, templates, consent/compliance.- Tools: Dovetail or EnjoyHQ (repository/analysis), Lookback/Hotjar for sessions, UserTesting/Respondent for recruiting, Figma for prototypes, Miro for synthesis, Jira/Notion integration.- Playbooks: consent flows, screener library, templates for plans/consent, synthesis methods (affinity, JTBD), repository taxonomy.

**Intake & prioritization**- Lightweight intake form in Notion linked to product roadmap; monthly research prioritization board using RICE (Reach, Impact, Confidence, Effort) + legal/ethical flags.- Triage weekly: emergencies (usability regressions), sprint-level asks (1–2 week guerrilla), discovery bets (4–8 week studies).

**Governance & standards**- Research Charter defining ethics, data retention, accessibility testing baseline, and publication cadence.- Quarterly Research Council (Design, PM, Eng, Legal) to review priorities, backlog, and cross-product learnings.- Mandates: 1 discovery study before major features; post-launch quick usability checks.

**KPIs to measure impact**- Process KPIs: cycle time (request → study start), % requests fulfilled, participant no-show rate.- Outcome KPIs: task success rate, SUS score delta, time-on-task improvements, conversion/retention uplift tied to feature releases.- Strategic KPIs: % product decisions citing research, number of research insights ingested into roadmap, reduction in rework/bug reports attributed to UX issues.

**Rollout plan (90-day)**- 0–30d: hire ops lead, audit past research, set templates, pilot with 2 squads.- 30–90d: expand embedded coverage, launch repository, first Research Council, baseline KPIs.- Ongoing: iterate tooling, train squads, publicize wins.

Why this works: combines centralized standards and tooling with embedded researchers so teams move fast while maintaining quality, measurable impact, and governance that reduces risk.

EasyTechnical

55 practiced

Explain the difference between open-ended and closed-ended interview questions. Provide three examples of each focused on a checkout flow, and explain why you'd prioritize open questions during early discovery research.

EasyTechnical

67 practiced

Design 6–8 screener questions to recruit participants for a 30-minute remote usability test of a mobile banking app. Include questions that qualify relevant behaviors, exclude edge cases, and capture basic quotas you might enforce (e.g., age, banking usage).

MediumTechnical

63 practiced

Design a lightweight research repository and intake process for an organization lacking centralized research. Specify metadata fields, templates for reports and codebooks, access controls, a prioritization rubric for incoming research requests, and a plan to keep the repository searchable and maintained.

Unlock Full Question Bank

Get access to hundreds of User Research & Need Identification interview questions and detailed answers.

Join thousands of developers preparing for their dream job.