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

Sample Size for Checkout Test

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

Your question is Sample Size for Checkout 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

ShopNow, a mobile e-commerce app, wants to test a simplified checkout flow that removes one confirmation step. Leadership needs a decision this month because the change affects the holiday release train.

Hypothesis Seed

The product team believes the shorter flow will increase purchase conversion by reducing friction at checkout. However, a false positive is costly because shipping a broken flow could reduce revenue and increase payment failures; a false negative is also meaningful because delaying a real improvement leaves revenue on the table.

Constraints

  • Eligible traffic: 120,000 checkout-starting users per day
  • Current checkout-to-purchase conversion: 24%
  • Maximum experiment duration: 14 days
  • Standard significance level: 5%
  • Desired power: 80%
  • Engineering asks for a recommendation only if the test can detect at least a 2% relative lift in conversion within the time window
  • The experiment platform supports user-level randomization and daily monitoring for safety only

Task

  1. Define the null and alternative hypotheses, the primary metric, 2-4 guardrail metrics, and the minimum detectable effect (MDE). Be explicit about the unit of randomization and unit of analysis.
  2. Calculate the required sample size per arm using the baseline conversion, alpha, power, and MDE above. Show the formula, plug in the numbers, and convert the result into an estimated runtime given available traffic.
  3. Propose the experiment design: allocation, duration, any stratification, and why your randomization choice avoids contamination.
  4. Pre-register the analysis plan: statistical test, peeking policy, how you will handle multiple comparisons, and what you will do if you detect sample ratio mismatch or instrumentation issues.
  5. State a clear ship / don’t ship / iterate rule that respects guardrails. Also explain how you would interpret a statistically significant result that is smaller than the pre-specified MDE.

Assume no major seasonality shocks during the 14-day window, but note any risks that could still bias interpretation.