Estimate infrastructure or operational capacity needed for DashPass at global scale

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 is evaluating what it would take to support DashPass at global scale across food delivery, grocery, retail, and other local commerce categories. As a candidate, you are being asked to estimate the infrastructure or operational capacity required to serve a much larger DashPass member base while maintaining delivery reliability, marketplace balance, merchant outcomes, and Dasher experience.

This is a guesstimate problem, so the focus is not on producing a single “correct” number. You should define the scope clearly, choose the capacity unit you are estimating, state assumptions, and build a structured model that connects DashPass adoption to order volume, delivery demand, marketplace load, and operational support needs.

You may interpret “capacity” as technology infrastructure, Dasher supply, support operations, fulfillment/logistics capacity, or a clearly scoped combination of these. The important part is to make the scope explicit and keep the estimate internally consistent across geographies, customer segments, and order categories.

The estimate should consider:

- The geographic scope of “global scale” and which markets or regions are included

- The relevant population base, such as households, active DoorDash users, or addressable subscription customers

- Expected DashPass adoption, member activity, order frequency, and category mix

- The unit of capacity being estimated, such as peak orders supported, active Dashers needed, support contacts, server/API load, or operational headcount

- Differences between average demand and peak demand, including mealtimes, weekends, holidays, and promotions

- Marketplace constraints involving Dasher availability, merchant preparation capacity, delivery distance, batching, and service-level expectations

- Key assumptions, sensitivity drivers, and sanity checks against known marketplace behavior or comparable services

- Guardrails such as unit economics, Dasher earnings, cancellation rates, lateness, customer support burden, and merchant ROI

Your goal is to produce a clear, defensible estimate that DoorDash leadership could use to understand the scale of investment or operational readiness required for DashPass expansion. The final answer should show a logical estimation path, call out the biggest uncertainties, and explain which assumptions most affect the result.