PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Analytics & Experimentation/DoorDash

Assess Adding Bicycle Dashers

Last updated: Jun 17, 2026

Quick Overview

This question evaluates competency in experimental design, causal inference, marketplace analytics, metric definition, and handling network effects within a two-sided delivery platform.

  • medium
  • DoorDash
  • Analytics & Experimentation
  • Data Scientist

Assess Adding Bicycle Dashers

Company: DoorDash

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: medium

Interview Round: Technical Screen

DoorDash is considering allowing **bicycle couriers (bike dashers)** to fulfill deliveries in a city that is currently served mostly by car/scooter dashers. How would you evaluate whether adding bike dashers is a good idea? Please address all of the following: 1. **Historical analysis:** What historical marketplace data would you use to decide whether this city or specific zones are suitable for bike dashers? 2. **Success criteria:** What primary metrics, secondary metrics, and guardrail metrics would you track? Consider consumer experience, merchant experience, dasher experience, and unit economics. 3. **Experiment design:** How would you run an A/B test or marketplace experiment to estimate the causal impact of enabling bike dashers? 4. **Network effects / interference:** Adding bike dashers can affect dispatching and matching for all orders, not just treated ones. How would you handle these spillover effects in the experiment design and analysis? 5. **Decision-making:** What results would convince you to launch, limit, or roll back the change? Assume you have access to order-level, merchant-level, dasher-level, zone-level, dispatch, weather, and geography data.

Quick Answer: This question evaluates competency in experimental design, causal inference, marketplace analytics, metric definition, and handling network effects within a two-sided delivery platform.

Related Interview Questions

  • Evaluate Biker Feature Success - DoorDash (hard)
  • How would you test product changes? - DoorDash (hard)
  • How to test bike delivery? - DoorDash (medium)
  • Investigate LA successful orders drop - DoorDash (easy)
  • How would you diagnose a completed orders drop? - DoorDash (easy)
DoorDash logo
DoorDash
Feb 2, 2026, 12:00 AM
Data Scientist
Technical Screen
Analytics & Experimentation
3
0

DoorDash is considering allowing bicycle couriers (bike dashers) to fulfill deliveries in a city that is currently served mostly by car/scooter dashers.

How would you evaluate whether adding bike dashers is a good idea?

Please address all of the following:

  1. Historical analysis: What historical marketplace data would you use to decide whether this city or specific zones are suitable for bike dashers?
  2. Success criteria: What primary metrics, secondary metrics, and guardrail metrics would you track? Consider consumer experience, merchant experience, dasher experience, and unit economics.
  3. Experiment design: How would you run an A/B test or marketplace experiment to estimate the causal impact of enabling bike dashers?
  4. Network effects / interference: Adding bike dashers can affect dispatching and matching for all orders, not just treated ones. How would you handle these spillover effects in the experiment design and analysis?
  5. Decision-making: What results would convince you to launch, limit, or roll back the change?

Assume you have access to order-level, merchant-level, dasher-level, zone-level, dispatch, weather, and geography data.

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More Analytics & Experimentation•More DoorDash•More Data Scientist•DoorDash Data Scientist•DoorDash Analytics & Experimentation•Data Scientist Analytics & Experimentation
PracHub

Master your tech interviews with 8,000+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.