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
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess 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
Get started

Choose Switchback for Marketplace Dispatch

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

Your question is Choose Switchback for Marketplace Dispatch. 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

Scenario

You work on a two-sided marketplace where the dispatch algorithm matches demand to nearby supply in real time. Your team has built a new dispatch policy that is expected to improve completed orders by reducing assignment latency, but you are worried that standard user-level A/B randomization could contaminate results because drivers and customers interact in the same shared market. You need to decide whether to run a standard A/B test or a switchback test, and design the experiment so the result is credible enough to ship.

Constraints

  • Eligible traffic: 120,000 completed-or-cancelled order requests per day across 12 cities
  • Average baseline completion rate: 68%; baseline median assignment latency: 42 seconds
  • Maximum experiment runtime: 21 days
  • Marketplace health guardrails: driver hourly earnings cannot drop by more than 2%, and cancellation rate cannot rise by more than 1 percentage point
  • Engineering can support either 50/50 user-level randomization or city-by-time switchbacks in 30-minute blocks, but not both simultaneously

Question

How would you decide between a switchback test and a standard A/B test here, and how would you design, power, and analyze the experiment so that the ship decision is valid despite interference risk?