← Back to Directory

Meta interview notes, page 14 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·Online Assessment (OA)

Apr 2026
Meta coding round for a software engineer role, done inside a large existing codebase you had to read and extend rather than start from scratch. The core problem was a card game with a specific scoring mechanic and you had to build out a strategy layer on top of it. Definitely a different format than the usual blank-slate leetcode setup.
  • Given a card game where sets of 3 cards summing to 15 score points and cards are continuously replenished from a deck, implement a strategy that maximizes total score across a full game. You're working inside a large pre-existing codebase.
  • When multiple valid disjoint sets of 3 cards are all playable at the same time, how do you decide which one to play first, and does the order even matter?
  • How deep a search tree can you realistically afford here, and what's your justification for the cutoff?

“The setup itself wasn't too bad to understand but the codebase context made everything slower.”

View Post

Meta·Machine Learning Engineer·Onsite - Coding / Algorithms

Apr 2026
Coding round for an MLE role at Meta, but don't let the job title fool you, there's no ML in this interview at all. Pure SDE-style algorithm problems, medium to hard difficulty, and they care a lot about how you think out loud.
  • Solve one or two medium-to-hard algorithm or data structure problems covering topics like arrays, strings, hashmaps, trees, graphs, or dynamic programming.

“Coming in as an MLE candidate I half-expected something model-related, so the pure DSA format was a bit of a reset.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Meta SWE coding round focused on tree traversal variations. Three problems, all BFS-based, but the way they were grouped together made it feel like one extended question with escalating requirements.
  • Given a binary tree, return the value of the rightmost node at each level (right side view).
  • Now return the leftmost node at each level instead (left side view).
  • For each level of a binary tree, return the average value of all nodes at that level.

“Pretty standard BFS question once you realize you just grab the last element of each level's queue snapshot.”

View Post

Meta·Product Manager·Onsite - Behavioral / Leadership

Apr 2026
Interviewed at Meta for a product role, one question about scrappy execution under resource constraints. Short post, not much to go on.
  • Tell me about a time you had to ship a product without the resources you needed. How did you make it work?

“I had a decent story for this but I think I spent too long on the setup and rushed the actual tradeoffs I made.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta coding screen for a software engineer role, one algorithmic question on interval merging with a slightly different input format than the classic version. Nothing too wild but the input parsing detail is easy to miss if you're on autopilot.
  • Given two separate integer arrays representing interval start points and end points, merge all overlapping intervals and return the result.

“The core logic is the same as the classic merge intervals problem but they split the input into two parallel arrays instead of giving you pairs.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta coding interview with a graph or greedy problem about minimizing water supply costs across a village. Not much context on how it went but the problem itself is a classic minimum spanning tree type setup.
  • Given a village with multiple houses, find the minimum total cost to supply water to all of them.

“This is a minimum spanning tree problem in disguise, but the twist is usually that you can also build a well at any house, so you have to model that as a virtual node connected to every house.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview with a product strategy question about Instagram. Just the one question but it had a lot of layers to it, more than I expected going in.
  • You're the PM for Instagram. How would you approach the decision of whether to invest in a verification badge feature?

“This felt deceptively simple and I kind of walked into it too fast.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Meta system design round focused entirely on a versioned key-value store. Pretty deep rabbit hole once the rollback semantics came up, and the conversation about memory tradeoffs went longer than I expected.
  • Design an in-memory key-value store that supports get, put, and rollback to any previous state of the entire store. Walk through snapshot creation, restore mechanics, and how you'd handle per-key version history.

“Started with the obvious stuff, a hash map with a snapshot list, but they pushed hard on the tradeoff between storing full copies versus diff logs.”

View Post

Meta·Software Engineer·Online Assessment (OA)

Apr 2026
Took the Meta SWE online assessment and got a banking system problem. Didn't nail all the test cases but passed anyway, which was a relief.
  • Implement a banking system with the required operations and constraints.

“Didn't get all the test cases to pass, which had me pretty sure I was done.”

View Post

Meta·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Meta for a software engineer role. Pretty short on details but the one thing that came up was around their 'move fast' value.
  • Tell me about a time you moved quickly on something, even with incomplete information or uncertainty.

“This is basically a core values question dressed up as behavioral.”

View Post