← Back to Directory

Meta interview notes, page 192 of 238

FAANG / Big Tech

Most of these Meta write-ups come from Software Engineers (1,194), then Data Scientists (489) and Product Managers (453). The most reported rounds are the technical phone screen (1,190), the product sense round (466), the system design round (255) and the behavioral / leadership round (205).

2377 interview notes · updated Jul 2026

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM loop at Meta, product sense round. Just the one question about Instagram Live but they really wanted to dig into it.
  • As a PM at Meta, how would you define and measure the success of Instagram Live?

“I jumped straight to engagement metrics and kind of regretted it.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Got a probability question at Meta that sounds deceptively simple but really isn't. Bayesian reasoning in a stats context, no fluff.
  • You flip a coin 10 times and every result is heads. What's the probability the coin is fair?

“This is a Bayes' theorem question and I almost answered it like a frequentist, which would've been completely wrong.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round with a tree problem that looks straightforward until you actually sit down with it. Nothing too exotic but the weighted edges add a layer that trips you up if you're not careful.
  • Given a weighted tree, find the length of the longest path between any two nodes.

“My first instinct was BFS and that was a mistake.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Meta with a product design question about building a marketplace-style feature for finding handypeople. Pretty open-ended, which I wasn't fully prepared for.
  • You're a PM at Meta. How would you design a product that helps users find and connect with handypeople (plumbers, electricians, etc.)?

“I went straight to features and the interviewer kind of just waited.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round, one question the whole time. The robot bounded in circle problem, which sounds straightforward until you actually have to reason through all the edge cases on the fly.
  • Given a sequence of movement instructions for a robot starting at the origin and facing north, determine whether the robot will remain bounded within some finite region if the instructions are repeated indefinitely. The solution must use constant space.

“I knew the key insight was about direction after one full cycle, not just position.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta data scientist interview with a stats-heavy question on comment distribution analysis. Single question but it went pretty deep into distributional testing and inequality metrics, more than I expected for a phone screen.
  • How would you quantitatively evaluate how comments are distributed across posts on a social platform? Walk through which metrics and statistical tests you'd use and what hypotheses you'd set up.

“I started with mean and variance which felt immediately wrong the second I said it out loud.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Meta system design round focused on building a personalized ranking and recommendation system at massive scale. The question was meaty and covered a lot of ground, from data ingestion to model serving to caching strategy.
  • Design a large-scale personalized ranking and recommendation system that serves millions of users in real time, supports continuous updates from user interactions, and returns results in under a second.

“This one is deceptively wide.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta data scientist interview with a probability/statistics question that felt more like a grad school exam than a product interview. One question, clean setup, but you need to actually know your Bayes.
  • Given a known fraud rate, a true-positive rate, and a false-positive rate for a flagging system, use Bayes' theorem to calculate the probability that a flagged account is actually fraudulent.

“I knew the formula but fumbled the plug-in step because I mixed up which rate went where.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Meta SWE coding round, one meaty interval problem that sounds straightforward until you actually have to think about edge cases under pressure.
  • Given two sorted lists of non-overlapping closed intervals, merge them into a single sorted list representing their union. You need to explain how you handle touching boundaries like [1,3] and [3,5], empty inputs, and invalid intervals where start exceeds end. Also state the time and space complexity and walk through an O(m+n) two-pointer solution.

“The core merge logic clicked pretty fast for me, two pointers advancing through both lists, pick the smaller start, extend the end greedily.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta software engineer interview with two algorithm questions back to back. Nothing behavioral, just code. Felt like a standard technical screen but the second question had more depth to it than I expected.
  • Given the root of a binary tree, return the values of the nodes visible from the right side, ordered top to bottom.
  • Given an unsorted array of distinct integers, find the index of any local minimum, where a local minimum is an element strictly less than both its neighbors. Treat out-of-bounds neighbors as positive infinity. Describe your algorithm and analyze the time complexity.

“Classic BFS level-order traversal, just grab the last node at each level.”

View Post