← Back to Directory

Meta interview notes, page 35 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·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE coding round, got a tree problem that looked manageable at first but has a few gotchas that'll trip you up if you haven't seen it before.
  • Given a binary tree, a target node, and an integer K, return all node values that are exactly K edges away from the target node.

“The downward direction is easy enough, just DFS from the target.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE interview with a tree problem that looks clean on the surface but has enough edge cases to trip you up if you haven't thought carefully about tie-breaking rules.
  • Given the root of a binary tree, group nodes into vertical columns by assigning each node an x-coordinate (root = 0, left child = x-1, right child = x+1). For each column from leftmost to rightmost, list node values top to bottom. When multiple nodes share the same x-coordinate and depth, order them by their left-to-right level-order position. Return all columns as a list of lists. Walk through your traversal approach, how you handle ties, and what data structures you'd use. Give time and space complexity.

“The x-coordinate assignment part I got down fast.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview with a product design question that covered a lot of ground fast. The scope was wide enough that I kept second-guessing whether to go deep on one area or stay broad, which is probably the whole point.
  • Design a marketplace app for dog walking. Walk through the core user journeys, what you'd build for an MVP, the high-level architecture across mobile and backend, and how you'd think about scope and scale.

“This question is deceptively wide.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at Meta with a product sense question framed around Back Market's checkout experience. One question, case-style, focused on whether you'd actually build what a colleague is pitching.
  • You own the purchase experience at an e-commerce marketplace for refurbished goods. A colleague flags that many users are trying to buy products in bulk from sellers and proposes building a dedicated checkout flow with invoicing to support them. How do you respond?

“My first instinct was to just agree and start scoping the feature, which is probably the wrong move.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at Meta focused on product strategy for Facebook Pay. Just one question but it was a meaty one that required thinking through goals, prioritization, and a rough roadmap under time pressure.
  • You are a PM at Meta. What are the goals for Facebook Pay over the next 6 to 12 months, and how would you approach tackling them?

“I fumbled the opening by jumping straight into features before anchoring on what success even looks like for a payments product.”

View Post

Meta·Machine Learning Engineer·Onsite - System Design / Architecture

Apr 2026
ML system design round at Meta for an engineer role. Single question, pretty open-ended, focused on building a monitoring system for a fantasy sports app. The scope was broad enough that you could go in a lot of directions, which was both the interesting part and the stressful part.
  • Design an ML monitoring system for a fantasy sports application. Your design should address data drift, model performance degradation, outlier detection, and data quality issues.

“I started with data quality and worked outward, which in retrospect was probably the right call since everything downstream breaks if your inputs are garbage.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE coding round, one problem, classic tree stuff. Nothing too wild but the details matter more than you'd think.
  • Given a binary tree where nodes can hold negative integers, find the maximum sum achievable along any path in the tree. The path can start and end at any nodes and doesn't need to pass through the root.

“The key thing that trips people up is that a path can't branch, so you can't return a forked value upward.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Quick ML interview at Meta, just one question about overfitting. Not much to go on but it's a core concept they clearly care about.
  • What techniques do you use to prevent a model from overfitting?

“Pretty standard but you can still stumble if you just list buzzwords without explaining the tradeoffs.”

View Post

Meta·Data Scientist·Technical Phone Screen

Apr 2026
Meta DS interview with a product experimentation question about rolling out restaurant recommendations in the News Feed. Pretty involved for a single question but it covered a lot of ground.
  • Meta is thinking about adding restaurant recommendations to the News Feed. Walk through how you'd design an experiment to evaluate this: what's the treatment and control, what metrics would you track, how do you think about sample size, and what would it take to actually ship this?

“This one sprawled in a way I didn't expect.”

View Post

Meta·Data Scientist·Technical Phone Screen

Apr 2026
Meta DS interview, SQL round focused on pixel event data. One question, pretty well-scoped, but the NULL handling edge case is where people probably slip up.
  • Given a table of daily pixel event counts broken down by signal type, write a SQL query that computes, for each pixel, the percentage of observed events that were invalid yesterday. Exclude missing events from the denominator, and handle the case where a pixel has zero observed events.

“The core aggregation is straightforward enough: sum invalid and total observed per pixel, divide.”

View Post