Estimate infrastructure or operational capacity needed for Logistics Platform

Problem Statement Description

Product context: DoorDash is a local commerce and delivery platform; its products include restaurant delivery, DashPass, grocery and retail delivery, merchant tools, and dasher tools.

DoorDash’s Logistics Platform must reliably match customer orders from restaurants, grocery stores, and local merchants with available Dashers while keeping delivery times, Dasher utilization, merchant experience, and unit economics healthy. In this guesstimate, you are asked to estimate the infrastructure or operational capacity needed to support that logistics system.

Frame the problem as if DoorDash is planning for a defined market, time period, or demand scenario, such as peak dinner hours, a city launch, a holiday surge, or daily nationwide operations. You may choose and state a reasonable scope, but your estimate should make clear what “capacity” means: Dasher supply, order dispatch throughput, support staffing, server/request load, routing capacity, or another operational bottleneck relevant to the Logistics Platform.

The estimate should consider:

- The geographic and time scope of the estimate, including whether it covers one city, multiple markets, or national operations

- The unit of capacity being estimated, such as active Dashers, concurrent deliveries, dispatch decisions per minute, support contacts, or system transactions

- Customer demand drivers, including order volume, peak-hour concentration, delivery categories, and marketplace seasonality

- Dasher-side assumptions, including active rate, shift length, utilization, batching, acceptance behavior, and delivery completion time

- Marketplace constraints such as restaurant prep time, travel distance, pickup/dropoff density, and service-level expectations

- Adoption and frequency assumptions for different order types, including food delivery, grocery, convenience, or local commerce

- Sensitivity to key variables, such as peak-to-average demand ratio, average delivery duration, cancellation rate, or Dasher availability

- Sanity checks against real-world signals like city population, merchant density, road capacity, and comparable delivery marketplace behavior

Your goal is to produce a structured, defensible estimate rather than a precise number. Clearly state assumptions, build the estimate step by step, identify the biggest drivers of uncertainty, and explain how DoorDash could use the result to plan staffing, marketplace balancing, infrastructure readiness, and launch or surge preparedness.