InterviewStack.io LogoInterviewStack.io

DoorDash Key Metrics & Dashboard Requirements Questions

Defining and standardizing DoorDash KPIs, identifying data sources, calculating metric definitions, data governance, and designing dashboards and reporting pipelines to monitor product and business performance. Includes data visualization best practices, dashboard design, interactivity, drill-down capabilities, and alignment with business goals across operations, product, and marketplace analytics.

HardSystem Design
82 practiced
Design a scalable strategy to support 1000+ localized dashboards for DoorDash markets while keeping maintainability high. Describe templating approaches, parameterized dashboards, multi-tenant access control, caching and pre-aggregation, monitoring for stale dashboards, and CI processes to manage dashboard changes and prevent regressions.
HardTechnical
115 practiced
You have a slow daily summary query that joins a 2-billion-row orders table with courier_profiles and geo_location tables. Propose detailed optimization strategies for Redshift and Snowflake: partitioning/clustering keys, sort keys vs clustering, materialized views, denormalization vs star schema, pre-aggregation, and cost estimates. Explain trade-offs between storage, ingestion complexity, and query speed.
HardTechnical
83 practiced
Provide SQL or Python pseudocode to compute rolling retention for monthly cohorts with right-censoring. Output: cohort_month, month_n (0..N), active_users, cohort_size, retention_rate. Explain how you handle users with incomplete observation windows (censoring) and provide complexity considerations for large datasets.
MediumTechnical
79 practiced
Describe how you would compute customer Lifetime Value (LTV) for DoorDash using cohort analysis. Explain cohort definition (by acquisition week/month), revenue window selection, discounting future revenue, handling censored customers (partial observation), adjustments for promotions/refunds, and how to present uncertainty and assumptions to stakeholders.
MediumTechnical
66 practiced
Define an on-time delivery rate KPI for DoorDash where a delivery is on-time if delivered within ETA. Discuss implementation nuances: estimated ETA vs final ETA, clock skew between devices and servers, late status updates, timezone normalization, canceled or refunded orders, and approaches to backfill or exclude late-arriving events.

Unlock Full Question Bank

Get access to hundreds of DoorDash Key Metrics & Dashboard Requirements interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.