PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Analytics & Experimentation/Meta

Design and analyze notification pinning experiment

Last updated: Mar 29, 2026

Quick Overview

This question evaluates experimental design, causal inference, metric definition and instrumentation, sample size estimation, and analysis skills in the context of a UI-driven notification pinning feature.

  • hard
  • Meta
  • Analytics & Experimentation
  • Data Scientist

Design and analyze notification pinning experiment

Company: Meta

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Technical Screen

Design an experiment to evaluate a feature that pins accounts with active notifications to the top of the account switcher for users who have ≥2 accounts. Specify: (1) targeting (only multi-account users) and the unit of randomization (person_id vs account_id) with rationale for avoiding cross-account interference; (2) exposure definition (what counts as being treated and an exposure log you would require); (3) primary success metrics (e.g., per-person notification view rate, click-through to notified account, notification-to-action conversion) and guardrails (e.g., time spent on accounts without notifications, overall session length, error rate, complaint reports); (4) sample size and duration assumptions using baseline metrics you would estimate from the provided tables, including how you’d handle unequal activity levels across users; (5) ramp plan, novelty effects control, and pre-experiment balance checks; (6) how you’d detect and correct interference or cannibalization across a person’s accounts (e.g., cluster/person-level randomization, ghost exposure, or exclusion windows); (7) analysis details: intent-to-treat vs treatment-on-the-treated, handling users who gain/lose accounts mid-test, missing data, multiple-testing control across segments (2, 3, 4+ accounts), and difference-in-differences or CUPED to reduce variance; (8) stop/go criteria and how you’d translate metric movements into a launch decision, including acceptable guardrail movement thresholds.

Quick Answer: This question evaluates experimental design, causal inference, metric definition and instrumentation, sample size estimation, and analysis skills in the context of a UI-driven notification pinning feature.

Related Interview Questions

  • Measure scheduled posts feature success - Meta (medium)
  • Estimate ads ranking revenue impact - Meta (medium)
  • How should you evaluate unconnected content? - Meta (medium)
  • Should WhatsApp launch group calls? - Meta (medium)
  • How would you grow Meta products? - Meta (medium)
Meta logo
Meta
Oct 13, 2025, 9:49 PM
Data Scientist
Technical Screen
Analytics & Experimentation
0
0
Loading...

Experiment Design: Pinning Accounts With Active Notifications in the Account Switcher

Context

You are evaluating a UI feature that pins accounts with active notifications to the top of the account switcher. The feature is only relevant for people who manage multiple accounts (≥2). Design a rigorous experiment covering the items below.

Task

  1. Targeting and randomization
  • Target population: only multi-account users (≥2 accounts).
  • Choose the unit of randomization (person_id vs account_id) and justify your choice with respect to avoiding cross-account interference.
  1. Exposure definition and logging
  • Define what counts as being exposed/treated.
  • Specify the exposure log schema you require to enable correct intent-to-treat and on-exposure analyses.
  1. Metrics
  • Primary success metrics (e.g., per-person notification view rate, click-through to the notified account, notification-to-action conversion, time-to-action).
  • Guardrails (e.g., time spent on accounts without notifications, overall session length, error rate, complaint reports, mistaken switches).
  1. Sample size and duration
  • State assumptions and how you would estimate baselines from provided tables.
  • Account for unequal activity levels across users and clustering.
  • Provide the computation approach and an illustrative example.
  1. Ramp plan and validity controls
  • Traffic ramping plan, monitoring, and rollback rules.
  • How you will control for novelty effects.
  • Pre-experiment balance checks.
  1. Interference/cannibalization detection and correction
  • How to detect and mitigate cross-account interference or cannibalization (e.g., cluster/person-level randomization, ghost exposure in control, exclusion windows).
  1. Analysis details
  • Intent-to-treat vs treatment-on-the-treated.
  • Handling users who gain/lose accounts mid-test.
  • Missing data handling.
  • Multiple testing control across segments (2, 3, 4+ accounts).
  • Variance reduction (e.g., difference-in-differences, CUPED).
  1. Stop/go criteria and launch decision
  • Define statistical and practical significance thresholds for primary metrics.
  • Acceptable guardrail movement thresholds and how to weigh trade-offs.

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More Analytics & Experimentation•More Meta•More Data Scientist•Meta Data Scientist•Meta Analytics & Experimentation•Data Scientist Analytics & Experimentation
PracHub

Master your tech interviews with 8,000+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.