← Back to Directory

Meta interview notes, page 75 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

May 2026
Meta SWE interview with a graph/DP problem that looked straightforward on the surface but had a follow-up that made me rethink my whole approach. The recursion depth angle was something I hadn't prepped for specifically.
  • Given an m x n integer matrix, find the length of the longest path of strictly increasing values where movement is restricted to up, down, left, and right. Design an efficient algorithm and walk through its time and space complexity.
  • Follow-up: for very large matrices where deep recursion could cause a stack overflow, how would you redesign the solution to be iterative or otherwise avoid blowing the call stack?

“I went straight to DFS with memoization, which is the right call, but I fumbled explaining why the memoization was valid here.”

View Post

Meta·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Meta PM interview, one scenario-based question about a metric drop in the ad creation flow. Pretty focused session, no fluff.
  • As the PM for Facebook Ad Manager, you notice the ad publishing rate dropped 10% starting around 10PM last night. Walk through what you'd do.

“This is a classic metric drop question but the ad creation workflow angle makes it a bit more layered than your average DAU dip scenario.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Meta DS interview with a SQL-heavy technical screen. Two questions back to back, both pulling from the same notification/survey dataset. Not a vibe check, they wanted to see you think through join semantics and aggregation grain in real time.
  • Using a surveys table and a survey responses table, write a SQL query that computes the overall survey response rate, defined as the number of responses divided by the number of surveys sent. Make sure to handle the case where some surveys have no response.
  • Write a query that compares the average survey rating between new users (signed up less than 30 days before the survey was sent) and existing users. Think carefully about how you define and control the aggregation level.

“My first instinct was an inner join and I almost went with it.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

May 2026
Meta SWE coding round, one main problem on grid shortest path. Pretty standard BFS stuff but the follow-ups kept coming and that's where things got interesting.
  • Given a grid maze with walls, a start cell, and a goal cell, find the length of the shortest path moving in four directions through empty cells. Return the number of moves, or -1 if no path exists.

“BFS from the start, track distances, return the distance at the goal cell.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

May 2026
Meta ML engineer interview with a graph algorithm problem. Pretty standard coding round, nothing too wild, but DAG traversal always makes me second-guess my base cases.
  • Given a Directed Acyclic Graph (DAG), write a function that returns the length of the longest path in the graph.

“My first instinct was BFS which was wrong.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview with a product strategy question about Meta Pay. Single question but it had three parts, which I didn't fully appreciate until I was halfway through rambling about strategy without touching metrics at all.
  • What are the strategic reasons Meta might have for building Meta Pay, what goals should Meta set for it, and how would you measure whether it's succeeding?

“Spent way too long on the 'why build this' part and basically had to rush through metrics at the end.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

May 2026
Meta ML Engineer coding round, just one problem but the follow-up constraint is where it gets interesting. Pretty clean problem on the surface but the O(1) space requirement forces you to actually think instead of just flood-filling your way out.
  • Given an m x n grid of characters where 'X' marks a battleship and '.' marks empty space, count the number of distinct battleships. Battleships are horizontal or vertical and guaranteed not to be adjacent. Follow-up: do it in O(m*n) time, O(1) space, without modifying the board.

“The naive approach is easy enough, just DFS or BFS and mark visited cells.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Meta data scientist interview with a probability and statistics focus. Two questions, both conditional probability flavored, one a binomial conditioning problem and the other a Bayesian setup with a three-state room model. Pretty math-heavy for what I expected.
  • There are N conference rooms and K meetings assigned uniformly at random. Given that room 1 is not empty, what is the expected number of meetings in room 1?
  • Two rooms exist where the three states (both occupied, exactly one occupied, both empty) are equally likely. If you pick a room at random without looking, what's the probability it's occupied? Then, given you enter and find it occupied, what's the probability the other room is also occupied?

“The binomial part wasn't too bad once I remembered you're conditioning on at least one meeting landing there.”

View Post

Meta·Software Engineer·Hiring Manager Screen

May 2026
One question from a Meta data engineer loop, nothing fancy. Just a career development question but it's the kind that can trip you up if you haven't thought about it before the call.
  • How do you plan to grow professionally as a data engineer?

“I rambled a bit about learning new tools and taking on harder projects, which in hindsight was pretty thin.”

View Post

Meta·Data Scientist·Recruiter / HR Screen

May 2026
Recruiter screen for a Data Scientist role at Meta. Pretty standard stuff, just the usual get-to-know-you questions before anything technical.
  • Can you walk me through your background and career so far?
  • What's prompting you to leave your current role, and why does this position interest you?

“Rambled a bit trying to connect everything into a clean story.”

View Post