PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Analytics & Experimentation/DoorDash

Design analysis to reduce cold-delivery complaints

Last updated: Apr 27, 2026

Quick Overview

This question evaluates a data scientist's end-to-end analytics and experimentation competencies, including precise metric definition, causal diagnostics and attribution, randomized and quasi-experimental design, and operational impact measurement.

  • hard
  • DoorDash
  • Analytics & Experimentation
  • Data Scientist

Design analysis to reduce cold-delivery complaints

Company: DoorDash

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Technical Screen

You are the data scientist at a food-delivery marketplace seeing an increase in 'cold food' complaints. Design an end-to-end analysis and action plan (no product/app UI changes allowed). Be precise: 1) Define one primary metric and at least two guardrails. Specify exact formulae, numerator/denominator, inclusion/exclusion rules (completed deliveries only; first cold complaint within 24h per order; exclude re-deliveries/cancellations), time window, and aggregation grain. Justify why your primary metric is superior to alternatives (e.g., refund rate, mean drop-off temperature, CSAT). 2) Enumerate the key slices and covariates (city, weather, cuisine, container type, distance, elevation, pickup wait, drop-off wait, courier equipment such as insulated bag, batching, time-of-day, weekend/holiday, restaurant prep SLAs). 3) Lay out a diagnostic plan to attribute drivers: separate kitchen- vs. courier- vs. handoff-driven cooling using stage-duration breakdowns and appropriate models; describe controls for confounding (seasonality, surge, rain) and small-sample shrinkage. 4) Propose an experiment to provide couriers with insulated bags: state randomization unit, stratification, sample-size/power back-of-envelope with assumptions, duration, primary and secondary metrics, and spillover/contamination risks. 5) If an RCT is infeasible, propose a quasi-experiment (e.g., difference-in-differences on staggered rollouts, or IV using sudden rain as an instrument). State identifying assumptions and two falsification checks. 6) Recommend 3–5 operational changes that do not alter the product (e.g., operational batching limits, pickup queue prioritization, courier incentives for swift handoff, restaurant packaging standards), and how you would measure impact at 2 weeks vs. 8 weeks, including ROI and operational cost trade-offs. Assume 'today' is 2025-09-01.

Quick Answer: This question evaluates a data scientist's end-to-end analytics and experimentation competencies, including precise metric definition, causal diagnostics and attribution, randomized and quasi-experimental design, and operational impact measurement.

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
Oct 13, 2025, 9:49 PM
Data Scientist
Technical Screen
Analytics & Experimentation
6
0
Loading...

Cold-Food Complaints: End-to-End Analysis and Action Plan

You are the data scientist at a food-delivery marketplace that is seeing an increase in "cold food" complaints. Design an end-to-end analytical and operational plan. Do not propose any product/app UI changes; focus on measurement, diagnostics, experimentation, and ops.

Assume today is 2025-09-01.

Requirements

  1. Primary Metric and Guardrails
    • Define exactly one primary metric and at least two guardrails.
    • Provide precise formulas: numerator, denominator, inclusion/exclusion rules (completed deliveries only; count only the first cold complaint within 24 hours per order; exclude re-deliveries and cancellations), time window, and aggregation grain.
    • Justify why your primary metric is superior to alternatives (e.g., refund rate, mean drop-off temperature, CSAT).
  2. Slices and Covariates
    • Enumerate key slices and covariates to analyze (e.g., city, weather, cuisine, container type, distance, elevation, pickup wait, drop-off wait, courier equipment such as insulated bag, batching, time-of-day, weekend/holiday, restaurant prep SLAs).
  3. Diagnostic Plan and Driver Attribution
    • Separate kitchen- vs courier- vs handoff-driven cooling using stage-duration breakdowns and appropriate models.
    • Describe controls for confounding (seasonality, surge, rain) and small-sample shrinkage.
  4. RCT: Insulated Bags for Couriers
    • Propose an experiment to provide couriers with insulated bags.
    • State randomization unit, stratification, sample-size/power back-of-the-envelope with assumptions, duration, primary and secondary metrics, and spillover/contamination risks.
  5. Quasi-Experiment if RCT Is Infeasible
    • Propose a quasi-experiment (e.g., difference-in-differences on staggered rollouts, or an instrumental variable approach).
    • State identifying assumptions and two falsification checks.
  6. Operational Changes (No UI Changes)
    • Recommend 3–5 operational changes (e.g., batching limits, pickup queue prioritization, courier incentives for swift handoff, restaurant packaging standards).
    • Explain how you would measure impact at 2 weeks vs 8 weeks, including ROI and operational cost trade-offs.

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.