Meta — Facebook — Product Sense & Metrics

Role context: Data Scientist, Product Analytics (Facebook) · Est. study time: 40 min · 4 practice questions

How to prepare for this role

The loop is four rounds: Analytical Reasoning (structure an ambiguous product question, pick data, design a measurement), Analytical Execution (hypotheses plus applied statistics, usually with SQL), AI-Native DS Technical Skills (using AI tools in the analysis workflow without losing rigor), and Behavioral. Across all of them the interviewer is really testing one instinct: before you solve a problem, can you tell whether it's a problem worth solving? They will hand you a vague prompt ("engagement dropped in Brazil"), then add constraints mid-answer (seasonality, a holiday, a competitor, network effects) and watch whether your reasoning stays coherent.

Where to spend your prep time:

• Product sense and metrics (this article) — Facebook's surfaces, why it ranks on Meaningful Social Interactions, and how an engagement metric can backfire.
• Root-cause and product cases — practice decomposing a metric move by segment before diagnosing. See the Product Case section.
• Experimentation and statistics — A/B design, network interference, reading results honestly. See the A/B Test & Causal Inference section.
• SQL and communication — be fast in SQL, and rehearse the recommendation out loud: what you'd tell the PM, and why.

The through-line: find the right problem, define the right metric, defend it against gaming, and land a clear decision. That matters more than any method.

What Facebook actually is

Facebook is Meta's original social network and still one of the largest products on earth. The identity to carry into every answer: a personal and community network that connects people to friends, family, groups, and local commerce, monetized almost entirely by advertising. The loop is simple to state: people connect and post, Feed ranking surfaces the most relevant content, interactions (comments, reshares, reactions) bring people back, and that attention creates the ad inventory that funds everything.

The single most important thing to understand about Facebook's measurement history is Meaningful Social Interactions (MSI). Around 2018, Feed ranking shifted away from raw time spent toward interactions between people — comments, reshares, replies, reactions — weighted by how close the two people are (friends and family and groups over passive publisher content). The stated reasoning was that Facebook had been overvaluing time on the platform and undervaluing genuine interaction.

MSI is also Facebook's most famous lesson in metric design. Rewarding comments, reshares, and strong reactions (including "angry") ended up promoting divisive, outrage-driving content, because that is what those signals reward. It is a clean, real example of the core idea a Product DS lives by: a proxy metric optimizes for exactly what it measures, so an engagement metric must travel with an integrity guardrail.

The engagement loop

At each step a DS asks: where do people drop, which interactions are meaningful versus merely reactive, and which content builds a durable return habit versus a short outrage spike. The bottom branch matters as much as the top: a comment driven by anger still counts as an interaction, which is exactly how a well-intentioned metric can go wrong.

The sides of the market

The sides — people, advertisers, and inside Marketplace the buyers and sellers — mean most decisions carry a cross-side tension. More ad load lifts revenue but costs the person's experience; ranking that maximizes raw engagement can amplify low-quality content that erodes long-term trust; a Marketplace change that helps buyers can starve seller liquidity. Naming that trade-off is half of a strong answer.

Metrics by layer

North Star (engagement quality):

• Meaningful Social Interactions (MSI) — interactions between people, weighted by relationship. The Feed objective, chosen over time-spent to reward genuine connection.

Reach and activity:

• DAU and MAU, and the DAU/MAU stickiness ratio — how many days a monthly user actually shows up.
• Content-creation rate — the share of people who post or comment, the supply that feeds the network.

Communities and commerce:

• Groups — active vs passive members, contributions per member, group joins and retention.
• Marketplace — listings, buyer-seller conversations, message-to-seller rate, transactions (a two-sided liquidity problem).

Monetization:

• Ad revenue, ARPU, impressions, ad load, price per ad — the ads that fund almost all of it.

Integrity guardrails:

• Prevalence of violating content, reports, misinformation exposure, "see less" — the signals that keep the engagement metric honest.

The senior point in one line: an engagement metric like MSI can be gamed by outrage and low-quality content, so it never travels alone — always pair it with an integrity guardrail.

The data you'd look at daily

Most days this role works with logs of what Feed showed and what people did about it. Three tables do most of the work (example columns and rows):

1. Feed impression log — one row per post shown to one person (billions of rows a day):

author_tie is the column that makes this Facebook rather than any feed. MSI weights an interaction by how close the two people are, so a comment from a close friend and a comment on a publisher post are not the same event, and a table that collapses them cannot measure the thing being optimized.

The last row is the failure mode in a single line: four comments and two reshares is a strong MSI contribution, and the angry reaction plus the report say it is the kind of engagement nobody wants. Both facts come from the same row, which is why the integrity columns live next to the engagement ones rather than in a separate system.

2. Experiment scorecard — one row per experiment × metric. This is what you read to make a ship call:

A 4.4% MSI lift is a large win by Feed standards, and this scorecard is still a hold. Three integrity rows moved together in the wrong direction, which is the signature of a ranking change that found engagement in divisive content. The number the ranker optimizes went up because the product got worse.

3. Daily metric aggregate — one row per day × slice; what the dashboards roll up from:

Reading the global row alone would hide every interesting thing here. New people interact at less than half the rate of established ones and report twice as often, because they have not built a friend graph yet. Groups is the most engaged surface and the one with the highest violating-content prevalence, which is the trade-off in one line. And ARPU differs by roughly 10x between regions, so a global average is dominated by wherever the ads sell.

What the dashboards look like at Facebook

Two views matter most each day.

The health dashboard — checked every morning by the team and leadership:

Your job is to explain every Watch or Alert cell. The pairing to look at first is creation falling while reports rise: people posting less and flagging more is usually the same underlying story about what the Feed is currently rewarding.

A trend tile sits alongside it, and on this product it is always a pair:

Beyond those two views, a Facebook Product DS reads the product the way it actually runs:

• Engagement with an integrity guardrail. The primary read is an MSI-style engagement metric, always shown next to integrity signals (violating-content prevalence, reports) so a hollow or harmful lift is visible.
• Decomposed, not blended. DAU and engagement are split by country, cohort (new vs existing), surface (Feed / Groups / Marketplace / Reels), and device, because a flat global number usually hides offsetting segment moves.
• Experiments that respect the network. Because a change to one person's Feed spills over to their friends, social experiments use cluster randomization, not naive user-level splits (see the A/B section).
• Read over time. Effects are watched over a days-in window to separate a novelty spike from durable change, and against seasonality and external events.

Every read ends in a decision for a PM or leader: ship, hold, iterate, or investigate.

Quick check

Practice Questions