← Back to Directory

Meta interview notes, page 86 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 that went deep on graph traversal, specifically a BFS variant I hadn't fully thought through before. The keys-and-doors twist sounds like a minor extension until you realize the whole visited-state logic has to change.
  • Given a grid where lowercase letters are keys and uppercase letters are locked doors, extend a standard BFS to handle collecting keys and unlocking doors. How do you define visited state, and what are the tradeoffs as the number of keys grows?

“My first instinct was to just track (row, col) like normal BFS and I immediately started going down that path before catching myself.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Did a technical screen at Meta for what seemed like a product or engineering role. One question, pretty open-ended, left me second-guessing my structure the whole time.
  • How would you diagnose a connection issue with Instagram?

“I started at the client layer and worked my way down, which felt logical at the time but I think I skipped over some obvious stuff like DNS and CDN failures too quickly.”

View Post

Meta·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Did a behavioral round for an EM role at Meta. Just the one question from what I can tell, pretty standard stuff but still worth thinking through.
  • Walk me through a time you had to tackle a particularly difficult problem.

“Classic prompt but I always underestimate how much they want to dig into your actual reasoning process, not just the outcome.”

View Post

Meta·Software Engineer·Hiring Manager Screen

May 2026
Interviewed at Meta for a bizops role, one round, pretty standard behavioral territory.
  • Walk me through a recent program you were responsible for.

“I had an answer prepped but rambled way too much on context and not enough on what I actually did.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta coding screen, one question the whole time, path normalization for a cd command. Seemed straightforward but there are enough edge cases to trip you up if you're not careful.
  • Implement a function that takes a current working directory and a path argument (as passed to a cd command) and returns the resulting absolute path. It should handle absolute paths, relative paths with dots and double-dots, multiple consecutive slashes, trailing slashes, and edge cases like cd-ing up from root or receiving empty input.

“Thought I had it locked in after the first few minutes, then the interviewer asked what happens when you do cd ..”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

May 2026
Meta SWE onsite coding round. One algorithm problem, implement a solution in Python or whatever language you prefer. Pretty standard setup but the problem itself had some specific constraints worth knowing about.
  • Implement an algorithm to solve the '361' problem, which involves specific constraints around bytecode or similar low-level requirements.

“The problem description was a bit cryptic going in.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

May 2026
Interviewed at Meta for an ML engineer role and got a tree problem that sounds straightforward until you're actually in it.
  • Given a binary tree, find the common ancestors of two given nodes.

“Classic problem but I still fumbled the edge cases a bit.”

View Post

Meta·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Meta behavioral round for a software engineer role, four questions deep into the usual leadership and self-reflection territory. Nothing technically surprising but the ambiguity question had more teeth than I expected.
  • What project are you most proud of, and what was your specific contribution to it?
  • Describe a time you had to move a project forward when requirements were unclear and you had little direction. How did you define the scope and get it done?
  • Tell me about a time someone pushed back hard on a decision or idea you had. What did you do?
  • Tell me about a time you received really harsh feedback. How did you handle it and what actually changed as a result?

“I'd rehearsed this one so much it started to sound rehearsed, which is its own problem.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

May 2026
Interviewed for an MLE role at Meta and got a mix of matrix logic and sliding window problems. Nothing too wild but the median one was rough under pressure.
  • Given a square matrix, check whether every element along the main diagonal is the same value.
  • Design a class that tracks a sliding window of fixed size over a stream of numbers and returns the running average after each new value is added.
  • For an array of integers and a window size k, output the median of the elements inside the window as it slides across the array one step at a time.

“Simpler than it sounds and I almost over-engineered it.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta data engineer screen, one coding question that looked simple but had a few layers to it once they started asking follow-ups about scale and memory constraints.
  • Given an iterable of friendships as unordered pairs of user IDs, implement a function that returns the mutual friends of two given users. Then discuss complexity, edge cases, and how your approach changes if the data is too large to fit in memory.

“The core implementation is pretty clean: build an adjacency map once, then intersect the two friend sets.”

View Post