Design an Experiment to Evaluate New ML Model

Quick Overview

This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Design an Experiment to Evaluate New ML Model states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Design an Experiment to Evaluate New ML Model

Company: Meta

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Onsite

##### Scenario Ads platform wants to validate engineers’ claim that a new ML ranking model outperforms the existing recommender. ##### Question How would you design an experiment to evaluate the new ML recommendation system? Which primary and guard-rail metrics would you monitor and why? An A/B test shows a 5% lift in CTR—how do you judge practical significance? CTR doubles for Indian males aged 18-55—what might this indicate and what next steps would you take? If the test yields +5% CTR and +5% revenue, would you roll the model out globally? Explain your decision process. ##### Hints Discuss randomization, sample size, heterogeneous effects, business trade-offs, and ethical checks.

Quick Answer: This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Design an Experiment to Evaluate New ML Model states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

|Home/Analytics & Experimentation/Meta
Meta logo
Meta
Aug 4, 2025, 10:55 AM
hardData ScientistOnsiteAnalytics & Experimentation
2
0

Design an Experiment to Evaluate New ML Model

Experiment Design: Validating a New Ads Ranking Model

Context

You operate an ads platform with an existing recommender/ranking model. Engineers built a new ML ranker that is hypothesized to improve outcomes. You need to run an online controlled experiment (A/B) to validate performance, choose appropriate metrics, assess significance, and make a rollout decision, including handling heterogeneous effects and ethics.

Tasks

  1. Experiment design
    • What is your randomization unit, ramp plan, duration, and sample size approach?
    • How will you guard against marketplace interference and data-quality issues?
  2. Metrics
    • Define 2–3 primary KPIs and a set of guard-rail metrics. Explain why each matters for users, advertisers, and the platform.
  3. Practical significance
    • An A/B test shows a +5% lift in CTR. How do you judge practical (business) significance vs. statistical significance?
  4. Heterogeneous effects
    • CTR doubles for Indian males aged 18–55. What might this indicate, and what next steps do you take to validate and respond?
  5. Rollout decision
    • If the test shows +5% CTR and +5% revenue, do you roll out globally? Explain your decision process, including trade-offs and ethical checks.

Constraints & Assumptions

  • Preserve the scope, facts, inputs, and requested outputs from the prompt above.
  • If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
  • Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

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...