Unit Economics And Pricing Analytics

What's being tested

DoorDash is probing whether a Data Scientist can evaluate pricing, incentive, and fulfillment changes through the lens of unit economics, causal inference, and marketplace experimentation. Strong answers connect customer behavior, merchant pricing, Dasher supply, and contribution margin without drifting into engineering or purely strategic hand-waving. Interviewers are looking for metric judgment: what is the right success metric, what are the guardrails, how would you estimate impact credibly, and how would you handle interference across a three-sided marketplace? The best candidates can reason from both experimental evidence and observational data, quantify uncertainty, and explain tradeoffs between growth, profitability, and marketplace health.

Core knowledge

• Unit economics means measuring profit per transaction, user, merchant, geography, or cohort. A basic delivery-order margin frame is:
  $\text{Contribution Profit} = \text{Consumer Fees} + \text{Commission} + \text{Ad Revenue} - \text{Dasher Pay} - \text{Promos} - \text{Refunds/Credits} - \text{Payment/Support Costs}.$
  Clarify whether fixed costs are excluded.

• Pricing changes affect both revenue and demand, so never evaluate a fee only by incremental dollars per order. Estimate $\Delta \text{Profit} = \Delta \text{Revenue} - \Delta \text{Variable Cost}$ while accounting for changes in conversion_rate, order_frequency, AOV, retention, refund_rate, and Dasher_utilization.

• Elasticity is central for fee and menu-price questions. Own-price elasticity is often approximated as:
  $E = \frac{\%\Delta Q}{\%\Delta P}.$
  If a $1 fee raises order price by 5$-0.6$. Segment by cuisine, income proxy, geography, new versus existing users, and time of day.

• Marketplace interference is a major experimental risk. Treating consumers may change Dasher availability, delivery times, merchant batching, or marketplace liquidity for control users. For strong interference, prefer geo-randomization, switchback experiments, market-level randomization, or cluster-robust inference over naive user-level A/B testing.

• Randomization unit should match the mechanism. A consumer fee can often randomize by user, but Dasher programs or fulfillment modes may require randomizing by market, zone, or time block. Merchant price inflation analyses are usually observational, requiring matched item panels and careful sampling rather than simple randomized experiments.

• Primary metrics should reflect the business decision. For a fee test, the likely primary metric is contribution_profit_per_visitor or contribution_profit_per_order, not just revenue_per_order. Guardrails include order_volume, conversion_rate, delivery_time, refund_rate, merchant_cancellations, Dasher_acceptance_rate, and customer retention.

• Intent-to-treat estimates are usually the default for experiments: compare all users assigned to treatment versus control, regardless of exposure. If only some users see the fee, report both ITT and treatment-on-treated using exposure or instrumental-variable logic, but do not let post-treatment filtering bias the result.

• Sample size and power matter because profit metrics are noisy. For a two-sample mean comparison, a rough per-arm sample size is:
  $n \approx \frac{2\sigma^2(z_{1-\alpha/2}+z_{1-\beta})^2}{\delta^2}.$
  Use historical variance for profit_per_user, not just order-level variance, and account for clustering if randomizing by market.

• Heterogeneous treatment effects are often the story in pricing. A fee may improve profit in dense urban markets but reduce conversion in suburban areas; bike couriers may reduce cost downtown but hurt ETA in low-density zones. Pre-specify key cuts to avoid cherry-picking: geography, customer tenure, merchant vertical, basket size, and supply-demand balance.

• Observational price inflation studies need matched merchant-item panels. Compare DoorDash menu prices versus in-store prices for the same item, merchant, geography, and time period. Watch for item substitutions, menu reclassification, taxes/fees excluded from menu price, and survivorship bias if discontinued items vanish from the panel.

• Forecasting inflation gaps should separate signal from sampling noise. Use weighted averages by order volume or merchant mix, report confidence intervals via bootstrap or cluster-robust standard errors, and consider simple baselines before complex models: seasonal naive, ARIMA, exponential smoothing, or hierarchical time-series models by category and market.

• Decision quality requires translating estimates into launch logic. A statistically significant lift in revenue_per_order may still be a bad launch if long-term retention falls or if Dasher supply worsens. Conversely, a small average effect may be compelling if concentrated in large, profitable segments with clean guardrails.

Worked example

For **“Evaluate Impact of $1 Fee on Fast-Food Profitability,”** start by clarifying whether the$1 applies to all fast-food orders, a subset of users, specific markets, or certain basket sizes, and whether the goal is short-term contribution profit or long-term customer value. In the first 30 seconds, state that you would evaluate both incremental margin and demand response, because the fee mechanically increases revenue per completed order but may reduce conversion or frequency. Organize the answer around four pillars: experiment design, metric framework, interference/segmentation, and decision criteria.

For design, propose a randomized experiment at the consumer or market level depending on expected spillovers; if fast-food demand affects local Dasher availability, geo or zone-level randomization is safer. For metrics, use contribution_profit_per_eligible_user as the primary metric, with secondary diagnostics like orders_per_user, conversion_rate, AOV, fee_revenue, Dasher_pay_per_order, and refund_rate. For guardrails, include delivery_time, customer_retention, merchant_cancellations, and customer support contacts. Explicitly flag the tradeoff between user-level randomization, which is more powered, and market-level randomization, which better protects against marketplace interference. Close by saying that, with more time, you would estimate heterogeneous effects by market density, basket size, customer tenure, and competitor sensitivity before recommending a broad launch or targeted rollout.

A second angle

For “Assess Success Criteria for Bike-Courier Delivery Launch,” the same unit-economics logic applies, but the intervention changes fulfillment cost and reliability rather than consumer price. The primary question becomes whether bike couriers improve contribution_profit_per_order by lowering Dasher pay, parking delays, or batching inefficiency without worsening ETA, cancellation, or courier supply health. Randomization may need to happen by zone and time window because delivery supply is shared, making user-level treatment less credible. The analysis should also segment by density, distance, weather, order size, and merchant type because bikes may work well for short downtown trips but fail for long suburban routes. Instead of elasticity, the key mechanism is operational cost-to-serve and service quality impact.

Common pitfalls

Pitfall: Treating revenue lift as profit lift.

A tempting answer is “a $1 fee increases revenue by$1 per order, so profitability improves.” That ignores fewer orders, different basket composition, higher refunds, retention effects, and potential Dasher or merchant cost changes. A stronger answer anchors on contribution_profit_per_eligible_user and decomposes the result into price, volume, and cost components.

Pitfall: Ignoring marketplace interference.

A naive A/B test can look clean statistically while violating the stable unit treatment value assumption. If treated customers reduce demand, control customers may see faster delivery or better Dasher availability, contaminating the estimate. Call out interference early and justify the randomization unit rather than defaulting to user-level assignment.

Pitfall: Overfitting the narrative with too many segments.

Segmentation is valuable, but listing twenty cuts without a plan sounds like fishing. Pre-specify the few segments tied to mechanism: density for bike couriers, basket size for fees, cuisine or merchant type for price inflation, and tenure for retention sensitivity. Then use exploratory cuts only to generate follow-up hypotheses.

Connections

Interviewers may pivot from here into experimental design, especially cluster randomization, switchbacks, power analysis, and sequential monitoring. They may also ask about causal inference for non-randomized launches, time-series forecasting for inflation gaps, or metric design for marketplace health and profitability.

Further reading

• Trustworthy Online Controlled Experiments — Kohavi, Tang, and Xu’s practical guide to experiment design, metrics, guardrails, and pitfalls.

• Causal Inference: The Mixtape — accessible treatment of difference-in-differences, matching, instrumental variables, and causal identification.

• Mostly Harmless Econometrics — rigorous foundation for applied causal inference in observational business settings.