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

Test Pause Orders Feature

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

Your question is Test Pause Orders Feature. 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

Merchants get too many orders and stop accepting them; DoorDash introduced a feature to pause orders. Design an A/B test to measure this product.

Asked in the onsite case stage. Clarify the available traffic, test duration, merchant eligibility, and whether the feature is automatically triggered or manually controlled. Then address:

  1. State the hypothesis and define a primary metric, guardrails, and an explicit MDE.
  2. Choose the unit of randomization and analysis, calculate sample size, and assess whether the traffic supports the test.
  3. Pre-register the statistical analysis, including peeking, multiple comparisons, and sample ratio mismatch checks.
  4. Explain likely pitfalls, including novelty, interference, and mismatch between merchant-level assignment and order-level outcomes.
  5. Give a ship, do-not-ship, or iterate rule that respects guardrails.