← Back to Directory

Meta interview notes, page 109 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
Security engineer screen at Meta with one scenario-based question about hardening a work laptop for a high-risk environment. Pretty focused, no fluff.
  • Your manager asks you to bring your work laptop to DEFCON. How do you secure it before and during the trip?

“This one has more layers than it looks.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta data engineering interview focused almost entirely on SQL optimization, specifically around reducing table scans in a big analytics query. It was more hands-on than I expected, less theory and more 'show me the plan and fix it'.
  • You're given a large analytics query with multiple CTEs. How would you refactor it to reduce the number of table scans?
  • When would you prefer a GROUP BY aggregation over a CTE, and how do you justify that choice in terms of the execution plan?
  • Walk through how you'd use EXPLAIN to verify scan counts and iterate on a query's execution plan.
  • Draft a quick solution to the query optimization problem first, then refine it. How does your approach change between the first pass and the final version?

“This one tripped me up more than I expected.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview with a product strategy question framed around running a travel incubator. Pretty open-ended, which I wasn't fully prepared for.
  • You are the Head of Product at a travel incubator. What would you build?

“The roleplay framing threw me a bit.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

May 2026
Meta MLE coding round, one problem the whole session. It started as a basic BFS maze question and then they kept adding constraints until I was basically rewriting the whole thing live.
  • You have a 2D grid maze with walls, open cells, a start, and an end. Implement BFS to find the shortest path. Then extend it: add keys (lowercase letters) and doors (uppercase letters) where you can only pass through a door if you already hold the matching key. How does your visited state need to change, and what's the minimum steps to reach the goal?

“The first part felt easy and I think I got a little too comfortable.”

View Post

Meta·Machine Learning Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Meta for an MLE role. Just one question but they really wanted the full story, not a quick answer.
  • How do you handle conflicts at work with peers, managers, or cross-functional partners? Walk through your general approach and a specific recent example including the disagreement, the different perspectives, how you worked to understand the other side, and what the outcome was.

“I had a story ready but underestimated how much they'd push on the 'understanding the other side' part.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE interview with a graph theory question that went deeper than I expected. No code required, just reasoning out loud, which sounds easier than it is when someone's watching you think.
  • For an unweighted graph, walk through how you'd find the shortest path between two nodes without writing any code. Explain the algorithm step by step, analyze its time and space complexity, and justify why it actually works.
  • Compare BFS and DFS for shortest path finding. When would you use each, and what are the trade-offs in terms of correctness, time/space complexity, and memory usage?
  • How does your approach change when the graph has weights on its edges?

“The 'no code' part tripped me up more than the actual algorithm.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE interview with a data structures design problem. Pretty focused, just the one question but it required some real thought about how to handle the tradeoffs.
  • Design a custom data structure that supports get() and setall() operations, both in O(1) time.

“My first instinct was a plain hashmap and I started going down that path before realizing setall() would be O(n) if you iterate every key.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE coding round, one question on shortest word ladder. Pretty straightforward problem on the surface but the edge cases will get you if you're not careful.
  • Given two words, find the length of the shortest word ladder (transforming one word into another by changing one letter at a time, where each intermediate word must be valid).

“Classic BFS problem and I knew that going in, but I fumbled the visited set logic at first and was computing redundant paths.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE coding round, one geometry problem that looked deceptively simple. The kind of question where you feel good for the first five minutes and then realize you've been thinking about it wrong the whole time.
  • Given a set of 2D points with integer coordinates, find all groups of four points that form a rectangle. Output each valid combination sorted by x and y coordinates, one per line.

“My first instinct was brute force all combinations of four points and check each one, which works but is slow and I knew they'd push back on it.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Had a product sense round at Meta for a PM role, one question about adding parking features to Google Maps. Pretty straightforward setup but the question itself has a lot of surface area if you let it.
  • How would you design parking features on Google Maps?

“I started by trying to clarify who we're actually building for, commuters vs occasional drivers vs people in unfamiliar cities, because the answer changes a lot depending on that.”

View Post