PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Analytics & Experimentation/DoorDash

Diagnose rising cold-food complaints and choose metrics

Last updated: Jun 14, 2026

Quick Overview

This question evaluates a data scientist's diagnostic analytics skills, including hypothesis generation, causal inference, metric engineering, and A/B/quasi-experimental design in a food-delivery marketplace context.

  • Medium
  • DoorDash
  • Analytics & Experimentation
  • Data Scientist

Diagnose rising cold-food complaints and choose metrics

Company: DoorDash

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: Medium

Interview Round: Technical Screen

## Case: Customers complain food arrives cold You are a **Data Scientist (Analytics-focused)** at a food delivery marketplace (e.g., DoorDash). Over the last few weeks, customer support tickets and app feedback indicate a **material increase in “food arrived cold” complaints**. Leadership asks you to diagnose likely causes and propose data-driven fixes. ### Business context (assume typical delivery flow) An order goes through: 1. **Order placed** (customer selects items, pays) 2. **Restaurant accepts & prepares** 3. **Dasher assigned & travels to pickup** 4. **Pickup happens** (food is handed to dasher) 5. **Travel to drop-off** 6. **Delivered** Assume you have access to event-level order logs (timestamps for each step), restaurant and dasher attributes, geography, batching/stacking flags, and customer feedback (ratings, complaint reason codes, refunds/credits). ### Tasks 1. **Hypothesize potential drivers** of colder food (generate multiple plausible root causes across restaurant operations, dispatch/assignment, dasher behavior, batching/stacking, distance/ETA accuracy, and seasonality/weather). 2. For each hypothesis, specify: - **What data/fields you would analyze** (and what joins or slices you’d do conceptually) - **What comparisons** you’d run (time series, cohorting, matched comparisons, geo/restaurant segments, etc.) - **Key confounders** to control for (e.g., order distance, cuisine type, weather, promos changing demand mix) 3. Propose **metrics** to measure: - **Customer feedback / experience** (include multiple options and tradeoffs) - **Revenue / business impact** (include multiple options and tradeoffs) - **Guardrails** (to avoid improving “warmth” at the expense of other outcomes) Clearly identify **one primary metric** and a small set of **diagnostic/guardrail metrics**. 4. Recommend **at least two interventions** (product/ops/policy) you would test, and outline an **experiment or quasi-experiment** plan: - Unit of randomization (order/restaurant/dasher/geo) - Success criteria and expected side effects - How you would handle interference/network effects (marketplace supply/demand) and delayed outcomes (refunds, repeat rate) Deliver your answer as a structured investigation plan plus an experimentation plan.

Quick Answer: This question evaluates a data scientist's diagnostic analytics skills, including hypothesis generation, causal inference, metric engineering, and A/B/quasi-experimental design in a food-delivery marketplace context.

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
Sep 25, 2025, 12:00 AM
Data Scientist
Technical Screen
Analytics & Experimentation
3
0
Loading...

Case: Customers complain food arrives cold

You are a Data Scientist (Analytics-focused) at a food delivery marketplace (e.g., DoorDash). Over the last few weeks, customer support tickets and app feedback indicate a material increase in “food arrived cold” complaints. Leadership asks you to diagnose likely causes and propose data-driven fixes.

Business context (assume typical delivery flow)

An order goes through:

  1. Order placed (customer selects items, pays)
  2. Restaurant accepts & prepares
  3. Dasher assigned & travels to pickup
  4. Pickup happens (food is handed to dasher)
  5. Travel to drop-off
  6. Delivered

Assume you have access to event-level order logs (timestamps for each step), restaurant and dasher attributes, geography, batching/stacking flags, and customer feedback (ratings, complaint reason codes, refunds/credits).

Tasks

  1. Hypothesize potential drivers of colder food (generate multiple plausible root causes across restaurant operations, dispatch/assignment, dasher behavior, batching/stacking, distance/ETA accuracy, and seasonality/weather).
  2. For each hypothesis, specify:
    • What data/fields you would analyze (and what joins or slices you’d do conceptually)
    • What comparisons you’d run (time series, cohorting, matched comparisons, geo/restaurant segments, etc.)
    • Key confounders to control for (e.g., order distance, cuisine type, weather, promos changing demand mix)
  3. Propose metrics to measure:
    • Customer feedback / experience (include multiple options and tradeoffs)
    • Revenue / business impact (include multiple options and tradeoffs)
    • Guardrails (to avoid improving “warmth” at the expense of other outcomes) Clearly identify one primary metric and a small set of diagnostic/guardrail metrics .
  4. Recommend at least two interventions (product/ops/policy) you would test, and outline an experiment or quasi-experiment plan:
    • Unit of randomization (order/restaurant/dasher/geo)
    • Success criteria and expected side effects
    • How you would handle interference/network effects (marketplace supply/demand) and delayed outcomes (refunds, repeat rate)

Deliver your answer as a structured investigation plan plus an experimentation plan.

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.