This was a lot to hold in your head at once.
Start by tying the feature to DoorDash's marketplace goals—growth, engagement, and profitability—then define a metric tree with primary and guardrail metrics. For the experiment, outline a randomized design with pre-period data for variance reduction (CUPED) and sequential testing, and justify the traffic split based on expected effect size, risk, and business constraints.
Pro tip: Emphasize that the traffic split isn't just statistical—it's a business decision balancing learning speed with the cost of a bad experience, and that pre-period data can dramatically increase sensitivity without increasing sample size.
Identify how the feature drives growth (e.g., order frequency, new customer acquisition), engagement (e.g., promotion redemption), and profitability (e.g., incremental profit, ROI). Map these to a metric tree with a primary success metric (e.g., incremental orders) and guardrail metrics (e.g., margin, customer satisfaction).
Choose randomization unit (e.g., customer or market), define treatment and control, and determine sample size and duration based on minimum detectable effect (MDE) and power. Consider potential interference and novelty effects.
Use pre-experiment data to apply variance reduction techniques like CUPED or stratified randomization to increase power. Also check for pre-existing differences to validate randomization.
Decide between 80/20 and 50/50 based on risk tolerance, expected effect size, and business constraints. Monitor leading indicators and guardrails daily, and use sequential testing to allow early stopping if needed.
After the experiment, analyze the primary metric with pre-period adjustment, check guardrails, and evaluate heterogeneous treatment effects. Make a launch decision based on statistical significance, practical significance, and business impact.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.