PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Analytics & Experimentation/DoorDash

Diagnose why average waiting time increased

Last updated: Mar 29, 2026

Quick Overview

DoorDash data scientist analytics prompt on diagnosing increased dasher wait time using event-level timestamps, metric validation, decomposition, root-cause analysis, product and operations levers, and experiment guardrails.

  • Medium
  • DoorDash
  • Analytics & Experimentation
  • Data Scientist

Diagnose why average waiting time increased

Company: DoorDash

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: Medium

Interview Round: Onsite

# Diagnose Why Average Waiting Time Increased You are a Data Scientist supporting DoorDash logistics. Over the last 1 to 2 weeks, the business metric average waiting time has increased noticeably. Assume waiting time is defined as: `dasher_wait_time_minutes = pickup_time - arrival_at_store_time` You have event-level order data, including order created, merchant confirmed, dasher assigned, dasher arrived, pickup, and dropoff timestamps. You also have merchant attributes, dasher attributes, market-level supply and demand data, and experiment or product-change logs. ### Constraints & Assumptions - The goal is to diagnose the root cause before recommending fixes. - Include data quality validation before interpreting the metric movement. - Consider marketplace, merchant, dasher, customer, product, and operations explanations. - Assume any proposed fix must be evaluated with guardrails for cost, customer experience, merchant experience, and dasher earnings. ### Clarifying Questions to Ask - Is the increase global or concentrated in specific markets, merchants, hours, or order types? - Did the metric definition, instrumentation, or filtering change recently? - Are we looking at mean wait time only, or also percentiles such as p50, p90, and p95? - Were there recent changes to dispatch, batching, merchant prep-time prediction, promotions, or supply incentives? ### What a Strong Answer Covers - Reproduce the metric and validate timestamp quality, time zones, missing data, cancellations, and outliers. - Decompose the change by market, time, merchant, cuisine, order size, dasher segment, batching, and product surface. - Separate merchant prep delays from dasher arrival timing, assignment latency, routing, and demand/supply imbalance. - Identify change points and connect them to launches, promotions, weather, holidays, merchant onboarding, or operational events. - Propose levers such as better prep-time prediction, dispatch timing, merchant throttling, courier incentives, batching rules, and merchant operations tooling. - Evaluate fixes with experiments or quasi-experiments using primary metrics and guardrails. ### Follow-up Questions - How would you distinguish a true merchant-prep issue from an instrumentation issue? - If only a few high-volume merchants drive the increase, what would you do? - What guardrail metric would protect dasher earnings? - How would you design an experiment for a new dispatch-timing model?

Quick Answer: DoorDash data scientist analytics prompt on diagnosing increased dasher wait time using event-level timestamps, metric validation, decomposition, root-cause analysis, product and operations levers, and experiment guardrails.

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
Jul 7, 2025, 12:00 AM
Data Scientist
Onsite
Analytics & Experimentation
12
0

Diagnose Why Average Waiting Time Increased

You are a Data Scientist supporting DoorDash logistics. Over the last 1 to 2 weeks, the business metric average waiting time has increased noticeably.

Assume waiting time is defined as:

dasher_wait_time_minutes = pickup_time - arrival_at_store_time

You have event-level order data, including order created, merchant confirmed, dasher assigned, dasher arrived, pickup, and dropoff timestamps. You also have merchant attributes, dasher attributes, market-level supply and demand data, and experiment or product-change logs.

Constraints & Assumptions

  • The goal is to diagnose the root cause before recommending fixes.
  • Include data quality validation before interpreting the metric movement.
  • Consider marketplace, merchant, dasher, customer, product, and operations explanations.
  • Assume any proposed fix must be evaluated with guardrails for cost, customer experience, merchant experience, and dasher earnings.

Clarifying Questions to Ask

  • Is the increase global or concentrated in specific markets, merchants, hours, or order types?
  • Did the metric definition, instrumentation, or filtering change recently?
  • Are we looking at mean wait time only, or also percentiles such as p50, p90, and p95?
  • Were there recent changes to dispatch, batching, merchant prep-time prediction, promotions, or supply incentives?

What a Strong Answer Covers

  • Reproduce the metric and validate timestamp quality, time zones, missing data, cancellations, and outliers.
  • Decompose the change by market, time, merchant, cuisine, order size, dasher segment, batching, and product surface.
  • Separate merchant prep delays from dasher arrival timing, assignment latency, routing, and demand/supply imbalance.
  • Identify change points and connect them to launches, promotions, weather, holidays, merchant onboarding, or operational events.
  • Propose levers such as better prep-time prediction, dispatch timing, merchant throttling, courier incentives, batching rules, and merchant operations tooling.
  • Evaluate fixes with experiments or quasi-experiments using primary metrics and guardrails.

Follow-up Questions

  • How would you distinguish a true merchant-prep issue from an instrumentation issue?
  • If only a few high-volume merchants drive the increase, what would you do?
  • What guardrail metric would protect dasher earnings?
  • How would you design an experiment for a new dispatch-timing model?

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.