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

Launch Decision for Onboarding Test

MediumA/B Testing & Experimentation00:00
Practice interviewer
In session
5 left
00:00

Your question is Launch Decision for Onboarding Test. 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

Context

StreamFlow, a subscription video app, redesigned its new-user onboarding to reduce friction: the new flow cuts signup from 5 screens to 3 and delays preference collection until after first play. The PM asks whether to launch if the experiment looks directionally positive but is not statistically significant.

Hypothesis Seed

The team believes the shorter onboarding will increase activation by reducing abandonment during account setup. However, it may also lower downstream retention if users provide fewer preferences, so the launch decision cannot rely on a single top-line metric.

Constraints

  • Eligible traffic: 120,000 new-user signups per day
  • Only 35% of signups are truly new users who have never installed before; exclude re-installs where possible
  • Maximum experiment duration: 14 days, because marketing campaign creative changes after that
  • False positive cost: shipping a weaker onboarding to all new users could hurt paid conversion and week-1 retention
  • False negative cost: delaying a good onboarding means losing activation during a major acquisition push
  • Engineering can support only a simple 50/50 split and one primary decision metric

Deliverables

  1. State the null and alternative hypotheses, and decide whether the test should be one-sided or two-sided.
  2. Define the primary metric, 2-4 guardrails, and at least one secondary metric. Include a clear MDE for the primary metric.
  3. Calculate the required sample size and determine whether the 14-day traffic budget is enough.
  4. Choose the unit of randomization and explain how you would analyze the test, including peeking policy, multiple-comparisons treatment, and what to do if results are directionally positive but not statistically significant.
  5. List key pitfalls for this experiment, including at least one instrumentation or interference risk, and give a ship / don’t-ship / iterate rule that respects guardrails.

Use the following planning assumptions for your calculations:

  • Baseline activation rate (complete signup and start first stream within 24 hours): 32%
  • Smallest business-meaningful lift: +1.6 percentage points absolute
  • Baseline paid conversion within 7 days: 8.5%
  • Baseline D7 retention: 24%
  • Significance level: 0.05
  • Desired power: 80%