← Back to Directory

Meta interview notes, page 47 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
PM interview at Meta with a strategy question about payments. Just the one question from what I can tell, but it was a meaty one that required actually thinking through build vs. partner tradeoffs in a real product context.
  • Imagine Meta Pay doesn't exist. Would you recommend Meta build a payment solution in-house or partner with an external provider? Walk through your reasoning.

“I went straight to the build side because Meta has the scale and the data, but I realized midway through I hadn't actually argued against it.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta software engineer interview, two coding questions back to back. Both were pretty classic but the follow-up discussions on complexity tradeoffs felt more serious than I expected for a phone screen.
  • Design a fixed-capacity in-memory cache that evicts the least recently used key when full, supporting get and put operations in O(1) average time. Walk through your data structure choices, how you track recency, how evictions work, and the time and space complexity.
  • Given an array of 2D points and an integer k, return the k points closest to the origin using Euclidean distance. Start with a sorting-based approach, then discuss Quickselect and a max-heap as alternatives, including their complexities and when you'd pick each.

“I knew this one cold so maybe that hurt me.”

View Post

Meta·Data Scientist·Technical Phone Screen

Apr 2026
SQL-heavy technical screen for a DS role at Meta, two questions back to back, both on the same pair of tables. Nothing behavioral, just pure query writing under pressure.
  • Given a posts table and a users table, write a SQL query that returns the count of distinct users who have at least one post that received at least 2 replies within 7 days of the post's creation time.
  • Among users who have received at least one reply to any of their posts, what percentage have received replies from at least 2 distinct reply authors who are based in the US?

“The core join isn't hard but I tripped up on the time window filter.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview focused on payments, specifically a metrics and strategy question about what happens when your key numbers move in a direction that looks bad but might not be. Pretty lean on details but the question itself was meaty.
  • You're the PM for Meta Payments. After launching in India and Southeast Asia, the average transaction value has dropped significantly. How do you define success here, and how do you decide whether to keep going?

“This one requires you to resist the instinct to treat a falling average as a bad thing.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE coding round with a single algorithm question focused on complexity optimization. The problem was straightforward to recognize but the optimal solution takes some real thought to get right.
  • Given an integer array and a value k, find the k-th smallest element using an algorithm with the best possible worst-case time complexity. A quick select solution exists but can you do better in the worst case?

“I knew quick select right away but the whole point was that they wanted something better for worst-case.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview with a product design question about building a language learning app. Pretty open-ended, which sounds fun until you're actually sitting there trying to figure out where to start.
  • Design a language learning app for Meta.

“Spent probably too long on the user segmentation piece before getting to actual features.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE coding round, one problem the whole time. Looked deceptively simple at first but the subset search angle took me a minute to fully see.
  • Given an array of strings, find a subset you can concatenate such that the resulting string has the maximum number of unique characters, with no character appearing more than once across the whole concatenation.
  • How would your approach change if the character set wasn't limited to lowercase English letters, say it included digits, uppercase, or arbitrary Unicode?
  • How would you convert your recursive subset search into an iterative DP over subsets, and what are the memory tradeoffs?

“My first instinct was to sort by length and greedily grab words, which is wrong.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Coding screen for an ML engineer role at Meta. One question, sliding window style, felt straightforward until I started second-guessing my approach mid-implementation.
  • Write a function that takes an array of integers and a window size N, then checks whether any contiguous subarray of length N contains duplicate values.

“I went straight for a sliding window with a hash set and it mostly worked, but I fumbled the part where you evict the element leaving the window.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE coding round, one question on binary search applied to frequency counting. Pretty focused session, nothing too wild.
  • Given a sorted array and a target value, find how many times the target appears in the array using binary search. You need to locate both the leftmost and rightmost positions of the target.

“The core idea clicked pretty fast since the array is sorted, two binary searches gets you there.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta frontend design interview, one main coding/design problem with a follow-up discussion. The question was meaty enough that the whole session basically revolved around it.
  • Build a React table component that supports pagination and sorting, with clean component decomposition, sensible state design, and dynamic column configuration. Follow-up: how would you extend it and make it work on mobile?

“Spent the first few minutes just thinking out loud about how to split things up, like a Table wrapper, a Header row, a Body, a Pagination control.”

View Post