← Meta Interview Insights

Meta·Data Scientist·Onsite - Product Sense / Strategy·Senior

Senior
Mar 2026

Summary

Meta DS onsite with a big open-ended case on rolling short video into a social newsfeed. Covered metrics, data modeling, and experiment design all in one question. Pretty demanding for a single session.

Questions Asked (3)

Q1

What goal metrics and guardrail metrics would you define when rolling out short video into a social platform's newsfeed?

Product Analytics & MetricsProduct Sense & Ideation
Author's notes

I led with time spent and daily active engagement, which felt safe, but I fumbled a bit on guardrails.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the product goal of adding short video to the newsfeed—likely increasing engagement and time spent—then define goal metrics that directly measure success against that goal, and guardrail metrics that ensure the change doesn't harm the core newsfeed experience or user well-being. Structure your answer around a clear framework: goal metrics (e.g., video views, watch time), guardrail metrics (e.g., newsfeed engagement, user satisfaction), and consider trade-offs and long-term effects.

Pro tip: Emphasize that guardrails should include both ecosystem health metrics (e.g., meaningful social interactions) and user well-being metrics (e.g., reported negative experiences), showing you understand Meta's commitment to responsible product development.

1. Clarify the product goal

State the primary objective of integrating short video into the newsfeed, such as increasing overall engagement, time spent, or attracting new users, and align metrics to that goal.

2. Define goal metrics

Identify metrics that directly measure success toward the goal, like daily video views, watch time per user, or percentage of users engaging with short video.

3. Define guardrail metrics

Select metrics to monitor for unintended negative consequences, such as declines in core newsfeed engagement, user satisfaction, or increases in reports of harmful content.

4. Consider trade-offs and long-term effects

Discuss potential trade-offs between short video and other content types, and include metrics for long-term user retention and well-being.

5. Prioritize and set thresholds

Explain how to prioritize metrics and set acceptable thresholds for guardrails to guide rollout decisions.

Key Points to Mention

  • Goal metrics: video views, watch time, engagement rate with short video, time spent per user
  • Guardrail metrics: overall newsfeed engagement, meaningful social interactions, user satisfaction (e.g., surveys), content diversity
  • User well-being metrics: reported negative experiences, problematic use, mental health indicators
  • Ecosystem health: impact on creators, content quality, and long-term retention
  • Trade-offs: cannibalization of other content, potential decrease in friend interactions
  • Experimentation: A/B testing to measure causal impact and monitor guardrails

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

Design a data model for a social platform that supports User, Content (text, image, or video), and User-Content interactions. How would you structure it?

Data ModelingSystem Design
Author's notes

Went with a polymorphic content table and a separate interactions table keyed on user and content IDs.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale, then propose a normalized relational schema with separate tables for users, content, and interactions, using polymorphic associations for content types and interactions. Discuss trade-offs between normalization and denormalization for read-heavy social feeds, and mention indexing and partitioning strategies for scalability.

Pro tip: Emphasize how the data model supports key product metrics like engagement and retention, and discuss how you would handle evolving content types (e.g., new media) without major schema changes.

1. Clarify Requirements and Scale

Ask about expected scale (users, content volume, interactions per second), read/write patterns, and latency requirements. This informs decisions on normalization, sharding, and caching.

2. Define Core Entities and Relationships

Identify User, Content, and Interaction as primary entities. Specify attributes for each (e.g., User: user_id, name; Content: content_id, type, text, media_url; Interaction: user_id, content_id, type, timestamp).

3. Design Schema with Polymorphic Associations

Propose tables: Users, Content (with type field and nullable columns for text, image_url, video_url), and Interactions (with type field for like, comment, share). Use foreign keys to link interactions to users and content.

4. Address Scalability and Performance

Discuss indexing (e.g., on user_id, content_id, timestamp), partitioning (e.g., by date or user_id), and denormalization for feed generation. Mention caching and read replicas for high read throughput.

5. Consider Extensibility and Trade-offs

Explain how to handle new content types or interaction types (e.g., using a type table or JSON columns). Discuss trade-offs between normalization (consistency) and denormalization (performance).

Key Points to Mention

  • Polymorphic associations for content types (text, image, video) and interaction types (like, comment, share)
  • Indexing strategies on foreign keys and timestamps for efficient queries
  • Partitioning and sharding for scalability (e.g., by user_id or date)
  • Denormalization for feed generation and caching to reduce latency
  • Handling evolving content types without schema changes (e.g., using JSON or type tables)
  • Trade-offs between normalization and denormalization in social platforms

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q3

How would you measure the impact of adding short video to the newsfeed? Walk through your A/B test setup, segmentation choices, and any secondary effects you'd watch for.

A/B Testing & ExperimentationProduct Analytics & Metrics
Author's notes

This was the part I felt most comfortable with.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by defining a clear goal and primary success metric (e.g., meaningful engagement) that aligns with Meta's long-term objectives. Then outline a rigorous A/B test design with appropriate randomization, power analysis, and guardrail metrics. Finally, discuss segmentation strategies and potential secondary effects, including novelty effects and cannibalization, to provide a comprehensive answer.

Pro tip: Emphasize the importance of measuring long-term effects and user well-being, not just short-term engagement, to show alignment with Meta's focus on sustainable growth. Also, mention the need to pre-register the analysis plan to avoid p-hacking.

1. Define Success Metrics

Identify the primary metric (e.g., daily active users, time spent, or meaningful interactions) and guardrail metrics (e.g., user satisfaction, well-being, or content diversity). Ensure metrics align with product goals and long-term value.

2. Design the Experiment

Set up a randomized controlled trial with proper randomization unit (e.g., user-level), determine sample size and duration via power analysis, and ensure control and treatment groups are comparable. Consider using a holdout group for long-term measurement.

3. Choose Segmentation and Analysis

Pre-define segments (e.g., demographics, user activity level, content preferences) to analyze heterogeneous treatment effects. Use appropriate statistical methods (e.g., CUPED, regression adjustment) to increase sensitivity and control for covariates.

4. Monitor Secondary Effects

Watch for novelty effects, cannibalization of other features, changes in content quality, and impacts on user well-being. Also monitor technical metrics like latency and error rates.

5. Interpret and Decide

Analyze results with confidence intervals and p-values, consider practical significance, and evaluate trade-offs. Recommend rollout, iteration, or termination based on overall impact and alignment with strategic goals.

Key Points to Mention

  • Randomization unit and sample size calculation
  • Primary and guardrail metrics (e.g., engagement, well-being)
  • Segmentation by user demographics and behavior
  • Novelty effect and long-term holdout
  • Cannibalization of other features (e.g., text posts, images)
  • Statistical power and multiple testing correction

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.