Analyze T2 Results and Recommend Launch Strategy

Quick Overview

Analyze T2 Results and Recommend Launch Strategy evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Analyze T2 Results and Recommend Launch Strategy

Company: Uber

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Technical Screen

##### Scenario E-commerce platform tests two treatments (T1, T 2) that affect Gross Bookings (GB) and Variable Consideration (VC) ##### Question T1 shows no significant change in GB or VC, while T2 shows a significant GB increase but significant VC decrease. Explain these results to the PM and recommend next steps. Given T2 confidence intervals (GB [+0.1%, +2.3%] ≈ +$0.48/order; VC [–2.5%, –1.5%] ≈ –$0.20/order), decide whether to launch and justify. Design a segmentation analysis to identify cohorts where GB lifts without hurting VC. If we will run 20 parallel feature experiments, define launch criteria, statistical thresholds, and how you will control error rates. ##### Hints Contrast statistical vs practical significance, revenue vs margin trade-offs, multiple-testing corrections, and cohort discovery techniques.

Overview: Analyze T2 Results and Recommend Launch Strategy evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Community answers

Answer by SS

False Discovery Control Multiple Testing Problem: Running 20 tests at α = 0.05 → Expected 1 false positive even if nothing works Need to control Family-Wise Error Rate (FWER) or False Discovery Rate (FDR) Approach: Benjamini-Hochberg Procedure (FDR Control) Rank all 20 p-values: p₁ ≤ p₂ ≤ ... ≤ p₂₀ Set target FDR = 0.05 (tolerate 5% false discoveries) Find largest k where: p_k ≤ (k/20) × 0.05 Reject all hypotheses H₁, H₂, ..., H_k Alternative: Bonferroni (More Conservative) Adjusted α = 0.05/20 = 0.0025 per test Controls FWER but reduces power
|Home/Analytics & Experimentation/Uber
Uber logo
Uber
Aug 4, 2025
hardData ScientistTechnical ScreenAnalytics & Experimentation
94
0

Analyze T2 Results and Recommend Launch Strategy

A/B Test Interpretation, Launch Decision, Segmentation, and Multi-Experiment Error Control

Context

You ran two A/B tests on an e-commerce platform:

  • T1 and T2 are feature variants intended to impact two business metrics:
    • Gross Bookings (GB): pre-fee, pre-incentive order value (a growth metric).
    • VC: Variable Contribution (margin) per order (i.e., contribution margin after variable costs). Assumption: A decrease in VC is margin-negative. If your org defines VC differently (e.g., as a contra-revenue where a decrease is good), flip the sign logic accordingly.

Observed Results

  • T1: No statistically significant change in GB or VC.
  • T2: Statistically significant increase in GB but statistically significant decrease in VC.
    • T2 confidence intervals:
      • GB: [+0.1%, +2.3%] ≈ +$0.48 per order
      • VC: [–2.5%, –1.5%] ≈ –$0.20 per order

Tasks

  1. Explain these results to the PM (statistical vs practical significance; growth vs margin trade-offs; plausible mechanisms).
  2. Decide whether to launch T2 using the given CIs and per-order impacts, and justify the decision.
  3. Design a segmentation analysis to identify cohorts where GB lifts without hurting VC.
  4. If you will run 20 parallel feature experiments, define:
    • Launch criteria and statistical thresholds for the primary and guardrail metrics.
    • How you will control false discoveries and error rates across the portfolio.

Hints

  • Contrast statistical vs practical significance.
  • Weigh revenue (GB) vs margin (VC) trade-offs.
  • Apply multiple-testing corrections where appropriate.
  • Use principled cohort discovery techniques that avoid p-hacking.

Clarifying Questions to Ask Guidance

  • Clarify the business objective, unit of analysis, time window, exposure definition, and primary metric.
  • State assumptions about instrumentation, randomization, sample size, and data quality.
  • Separate descriptive analysis from causal claims.

What a Strong Answer Covers Guidance

  • A metric framework with primary, guardrail, and diagnostic metrics.
  • A credible analysis or experiment design with clear assumptions and bias checks.
  • SQL/statistical logic for segmentation, variance, confidence, and data validation where relevant.
  • An actionable recommendation that explains trade-offs and next steps.

Follow-up Questions Guidance

  • What sanity checks would you run before trusting the result?
  • How would you handle novelty effects, seasonality, or selection bias?
  • What decision would you make if metrics disagree?
Loading comments...