← Back to Directory

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

Apr 2026
Meta PM interview, one question about setting goals for Facebook Rooms over a six month horizon. Pretty open-ended, which sounds nice until you're actually in it.
  • You're the PM for Facebook Rooms. What goals would you set for the next 6 months?

“I went straight into metrics and growth targets without really anchoring on what problem Rooms is even trying to solve right now.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Meta ML engineer interview, one question about model selection that sounds deceptively simple but has a lot of moving parts if you're not prepared for it.
  • How do you decide which model or algorithm to use when approaching a new problem?

“I fumbled the opener a bit.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Went through a Meta SWE coding round and got the classic remove duplicates from a sorted array problem. Pretty standard stuff but worth knowing cold.
  • Given a sorted integer array, remove duplicates in-place so each unique value appears once, using O(1) extra space. Return the count of unique elements.

“Two-pointer approach is the move here.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE coding round with a sliding window string problem. Pretty standard algorithmic stuff but the constraint on O(n) complexity is what makes it interesting.
  • Given a string, find the length of the substring with the greatest number of unique characters. Must run in O(n) time. String is lowercase letters only, up to 100k characters.

“The examples are a bit sneaky.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Meta SWE AI coding round built around a card game where you find triples summing to 15. Four progressive sub-tasks across roughly 55 minutes, and the pacing matters a lot since Q1 can quietly eat your time if you're not careful.
  • Debug a broken draw-cards method where the unit test fails because the drawn triple isn't guaranteed to come from the cards currently on the table.
  • Implement a naive scoring strategy that, each round, picks any three cards on the table that sum to 15.
  • Build a simulation harness to measure how often your naive strategy achieves a perfect game across many randomized runs.
  • Optimize the strategy using backtracking or dynamic programming over draw orderings to maximize the perfect-game rate.

“The sneaky part is the bug isn't in the method you're staring at.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta production engineer screen, just one coding question the whole time. Stack-based bracket matching, which felt almost too straightforward for the role but they wanted to see clean implementation.
  • Given a string containing only bracket characters, write a function to determine whether the brackets are valid (properly opened and closed in the correct order). Use a stack in your solution.

“Pretty much a textbook stack problem.”

View Post

Meta·Product Manager·Onsite - Behavioral / Leadership

Apr 2026
Two behavioral questions at Meta, back to back, about 15 minutes each. Pretty standard stuff but the cross-team collaboration one had more depth to it than I expected.
  • Tell me about a time you had a conflict at work with a peer, manager, or stakeholder. How did you resolve it?
  • Describe a project where you had to collaborate across multiple teams or organizations. How did you align everyone on goals, manage expectations, and keep things moving?

“Went with a story about a disagreement with a stakeholder over scope.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Meta for a software engineer role. The prompt was to design LeetCode with a focus on contest infrastructure and leaderboards, which sounds contained until you get into the weeds on scaling the judge.
  • Design a system like LeetCode, with particular emphasis on supporting coding contests and a real-time leaderboard.
  • How would you scale the code judge infrastructure, and how do you track the state of individual judge instances?

“I went with sandboxed containers for the code execution layer pretty early, which felt like the right call and the interviewer seemed fine with it.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta coding screen, just one question about binary trees. Pretty short session, nothing too wild.
  • Given a binary tree, determine whether it is height-balanced.

“Classic recursion problem but I kept second-guessing myself on what counts as balanced.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview, product analytics question about a metric drop. Pretty classic case-style question but it still trips you up if you haven't practiced the structure.
  • Monthly Active Users are down this month. How do you investigate and respond?

“I went straight to segmentation and probably skipped over clarifying what 'down' actually meant, like down vs last month, vs forecast, vs year-over-year.”

View Post