How would you improve reliability and latency 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 coordinates real-time delivery matching, dispatch, routing, order state updates, Dasher app experiences, merchant readiness, customer ETAs, and marketplace balancing across food, grocery, and local commerce. In this interview, you are asked to think as a Technical PM responsible for improving the platform’s reliability and latency for Dashers and the broader delivery ecosystem.

Focus on the end-to-end workflow where an order is created, assigned, accepted, picked up, routed, and delivered. Reliability or latency issues may show up as delayed assignments, stale ETAs, missed order state transitions, Dasher app lag, incorrect batching, routing delays, failed notifications, or degraded marketplace decisions during peak demand, bad weather, app releases, or infrastructure incidents.

You should frame the problem technically and product-wise: what reliability and latency mean for this platform, how failures affect Dashers, customers, merchants, and DoorDash’s unit economics, and how you would evaluate trade-offs between speed, accuracy, cost, resilience, and marketplace fairness. Do not assume this is only an infrastructure problem; consider APIs, data freshness, mobile clients, backend services, third-party dependencies, observability, rollout safety, and operational response.

The experience should consider:

- Critical user journeys for Dashers, including offer receipt, acceptance, navigation, pickup, drop-off, earnings visibility, and support escalation.

- Service-level expectations for latency, availability, freshness, and correctness across dispatch, routing, ETA, notifications, and order-state systems.

- APIs, event streams, data dependencies, mobile app behavior, network variability, caching, retries, idempotency, and failure modes.

- Reliability and latency instrumentation, including p95/p99 latency, error rates, queue lag, dropped events, stale location data, assignment failures, and incident impact.

- Segmentation by geography, merchant type, order type, Dasher device/network quality, peak periods, weather events, and marketplace density.

- Privacy, security, and trust considerations around location data, identity, payments, and operational visibility.

- Rollout and mitigation planning, including experiments, feature flags, staged launches, alerting, dashboards, incident playbooks, and rollback criteria.

- Product trade-offs across Dasher earnings, delivery reliability, merchant ROI, customer experience, and cost to serve.

Your goal is to define a structured approach for improving reliability and latency on DoorDash’s Logistics Platform, showing how you would identify the highest-impact bottlenecks, set measurable technical and product outcomes, align engineering and operations teams, and make pragmatic trade-offs without prescribing a single implementation upfront.