← Back to Directory

Meta interview notes, page 168 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
Meta PM interview with a single product design question about group travel. Pretty open-ended, which sounds fun until you're actually in it and realize you have no idea where to anchor.
  • You're a PM at Meta. How would you design a product for group travel?

“I spent the first couple minutes just trying to figure out what angle to take.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta DS interview with a pretty gnarly SQL question about visibility share ranking. Single question but it had multiple parts and a bunch of edge cases to track. The kind of problem where you think you understand it and then realize you missed something halfway through writing the query.
  • Write a SQL query to find the top 3 shops by average daily visibility share over a 7-day window for US non-bot traffic, applying session-level deduplication, handling days with zero eligible sessions, and using CTR as a tiebreaker on deduplicated impressions.

“This one has layers.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Meta SWE coding round, grid traversal problem with incremental test cases. Pretty standard BFS stuff but the multi-step structure tripped me up a bit.
  • Given a 2D grid with walls, an empty cells, a start position S and a target T, find the shortest path from S to T using 4-directional movement. Return -1 if no path exists.

“BFS was the obvious move and I knew it immediately, but the problem was structured as a series of test cases building on each other, so I kept second-guessing whether my clean solution would hold up for later parts.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Meta and got hit with a metrics/root cause question about a sharp drop in a key product event. Not much else to report, just the one question from what I can piece together.
  • Events created on Facebook have dropped 100%. How do you diagnose and respond to this?

“Classic metric drop question but the 100% part throws you off a bit.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round, one problem but the interviewer kept layering on constraints until I was basically rewriting my solution from scratch. The no-stack, single-pass requirement was the part that actually tripped me up.
  • Evaluate a string arithmetic expression containing non-negative integers and the operators +, -, *, / (no parentheses), respecting standard operator precedence and left-to-right associativity. Then do it in a single pass with O(1) extra space, no stack, no recursion.

“I had a working stack-based solution in my head pretty fast, then they said no stack.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Quick ML theory question from a Meta interview, the kind that sounds straightforward but has a specific answer they're looking for.
  • In K-Nearest Neighbors, what happens to variance and bias when you set k=1?

“k=1 means the model just memorizes every training point, so variance goes through the roof and bias drops to basically zero.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta EM interview with a graph traversal problem dressed up in a story about finding some guy named Alibada moving through rooms. Interesting framing but pretty clearly a BFS/DFS question underneath.
  • You have a collection of rooms connected to each other. A person starts in one room and moves to an adjacent room each day. Write a program to determine whether you can find this person given the room layout.

“Took me a second to see past the story and realize this is just graph reachability with a time component.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta software engineer interview with two coding problems. One tree traversal question and one binary search problem where they specifically wanted O(log n) complexity, not just a working solution.
  • Given a binary tree where each node contains a single digit, compute the sum of all numbers formed by root-to-leaf paths.
  • Given a sorted array and a target value, return all indices where the target appears. The catch: they want O(log n) time, not a linear scan.

“Pretty classic tree recursion problem.”

View Post

Meta·Data Scientist·Onsite - Behavioral / Leadership

Jun 2026
Behavioral prep list for a Data Scientist role at Meta. Four questions, all focused on influence, conflict, and onboarding dynamics. Nothing technically heavy but the expectations around specificity and measurable impact are real.
  • Tell me about a breakthrough project you led or had a significant hand in.
  • Describe a time you disagreed with a teammate, manager, or someone from another team.
  • How did you bring a new manager or stakeholder up to speed on a project's status, risks, and context?
  • What do you actually do to help new teammates get up to speed and feel part of the team?

“This one sounds easy until you realize 'breakthrough' is doing a lot of work.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta DS interview with a meaty system design question about building a hashtag recommendation system. One question but it had like four parts baked in, so it felt more like a 30-minute conversation than a single prompt.
  • Design a hashtag recommendation system for a social media platform. What signals and features would you collect? How would you handle cold-start users with little or no data? How would you combine those features into a scoring function, and how would you learn or set the weights?

“The cold-start part is where I stumbled.”

View Post