Select and prioritize metrics with guardrails

Quick Overview

This question evaluates a candidate's ability to design a robust metrics framework for product experiments, covering selection and normalization of success metrics, feature-only sizing and ecosystem metrics, explicit cannibalization reads, guardrails, multiple-testing control, and back-of-the-envelope LTV/ARPDAU impact estimation.

Select and prioritize metrics with guardrails

Company: Meta

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: medium

Interview Round: Technical Screen

A new Groups Stories feature aims to increase meaningful engagement without harming the broader ecosystem. Build a metrics framework and pick a minimal gating set: 1) define three top-line goal metrics (success metrics) and why they are normalized (per DAU, per viewer, or per poster); 2) list feature-only metrics (treatment-only CTR/creation rate) for sizing if launched; 3) ecosystem metrics to catch second-order effects (sessions, retention, revenue); 4) explicit cannibalization reads (impact on Feed, Marketplace, Pages); 5) guardrails (latency, crash, report rate, cancellations) and sanity checks; 6) specify a multiple-testing control method (e.g., Holm–Bonferroni vs BH) and when you’d prefer each; 7) show how you’d back-of-the-envelope the LTV and ARPDAU impact from a +1% DAU movement. Prioritize the three metrics that must be green to roll out to 100%, and explain why others are secondary.

Quick Answer: This question evaluates a candidate's ability to design a robust metrics framework for product experiments, covering selection and normalization of success metrics, feature-only sizing and ecosystem metrics, explicit cannibalization reads, guardrails, multiple-testing control, and back-of-the-envelope LTV/ARPDAU impact estimation.

|Home/Analytics & Experimentation/Meta
Meta logo
Meta
Oct 13, 2025, 9:49 PM
mediumData ScientistTechnical ScreenAnalytics & Experimentation
1
0

Design a Metrics Framework for a New Groups Stories Feature

Context

You are evaluating a new Groups Stories feature whose goal is to increase meaningful engagement while avoiding harm to the broader product ecosystem. Propose a metrics framework for experimentation and rollout gating, including success metrics, guardrails, and ecosystem checks.

Tasks

  1. Define three top-line goal (success) metrics and specify the normalization base (per DAU, per viewer, or per poster) and why.
  2. List feature-only sizing metrics (e.g., treatment-only CTR, creation rate) to estimate volumes if launched.
  3. List ecosystem metrics to catch second-order effects (e.g., sessions, retention, revenue).
  4. Specify explicit cannibalization reads on other surfaces (e.g., Feed, Marketplace, Pages).
  5. Define guardrails (e.g., latency, crash, report rate, cancellations) and sanity checks.
  6. Specify a multiple-testing control method (e.g., Holm–Bonferroni vs Benjamini–Hochberg) and when you’d prefer each.
  7. Show a back-of-the-envelope calculation for LTV and ARPDAU impact from a +1% DAU movement.

Finally, pick a minimal gating set (three metrics that must be green to roll out to 100%) and explain why the other metrics are secondary.

Loading comments...