Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Ground Research in Real Behavior

EasyProduct Sense00:00
Practice interviewer
In session
5 left
00:00

Your question is Ground Research in Real Behavior. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Company Context

HabitFlow is a Series B mobile productivity app with 6M monthly active users and a freemium subscription model. It competes on simplicity and habit-building workflows, but recent feature launches have underperformed because teams relied heavily on interview feedback and internal assumptions rather than observed user behavior.

Problem

Over the last two quarters, HabitFlow launched three research-backed features, but only one achieved meaningful adoption. A postmortem showed a recurring pattern: users said they wanted more customization and planning tools, yet product analytics showed most users completed tasks through quick-add, recurring reminders, and simple streak views. Leadership now wants a repeatable research approach that keeps discovery grounded in what users actually do, not just what they say.

The Head of Product asks you to design a research and decision-making process for a new initiative aimed at improving 8-week retention for new users, currently 24%, with a target of 30% within two quarters.

Deliverables

  1. Define how you would structure user research so it reflects real user behavior rather than assumptions.
  2. Identify which user segments and behaviors you would prioritize for this retention problem.
  3. Explain how you would combine qualitative and quantitative inputs to make product decisions.
  4. Recommend what type of feature or product changes you would test first, and why.
  5. Define how you would know whether the research process itself is improving decision quality.

Constraints

  • MVP recommendations must be testable within 10 weeks.
  • Research team has 1 UX researcher, 1 data analyst, and 2 PMs.
  • Event instrumentation is incomplete for some onboarding flows.
  • Engineering can support only one medium-sized retention initiative this quarter.
  • Leadership wants evidence before approving broader platform changes.