← Back to Directory

Meta interview notes, page 31 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·Onsite - System Design / Architecture

Apr 2026
Meta system design round for a software engineer role. One massive question covering basically every layer of a coding judge platform. Walked out unsure if I nailed it or rambled for 45 minutes.
  • Design an online coding practice and judging platform similar to LeetCode or Codeforces. Cover the full end-to-end architecture including user accounts, problem browsing, multi-language submission intake, sandboxed code execution, async grading with a distributed worker fleet, storage and data models, test-data versioning and re-judging, plagiarism detection, rate limiting, caching, observability, and how the system scales to contest spikes while handling worker crashes and queue redelivery correctly.

“This was basically ten questions duct-taped into one.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Product sense question for a PM role at Meta, focused on Reels. Just the one question from what I can tell, but it was meaty enough to chew on for a while.
  • You're the PM for Reels at Meta. Reels watch time is up 20% but Instagram feed posts are down 20%. What do you do?

“This one messed with me because the instinct is to celebrate the Reels number and explain away the posts drop.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta software engineer interview with a coding question involving bomb blast mechanics in a grid. I leaned pretty hard on AI to get through it, which made the whole thing feel like a weird performance where I was just narrating code I barely wrote.
  • Given a grid, simulate a bomb that destroys cells in a cross pattern (up, down, left, right from the detonation point). Implement the logic to handle this.

“I fed this straight to an AI and just read through what came back.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Meta system design screen focused heavily on database fundamentals, specifically transactions and concurrency. More theoretical than I expected for a coding round, but it made sense in hindsight given the scale Meta operates at.
  • Walk me through what a database transaction is, explain the ACID properties, and describe the standard transaction isolation levels including what anomalies each one prevents or allows.

“This is one of those questions where you think you know it cold and then freeze on the details.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Production Engineer interview at Meta, one round focused entirely on a single scenario-based troubleshooting question that kept drilling deeper. The interviewer played the role of someone feeding you clues while you had to work through a production outage live. Felt more like a real incident than a typical interview, which was a bit disorienting at first.
  • A production website is down. Walk through how you would diagnose the issue, starting from the moment you get the alert.
  • The disk is full. How do you free up space without dropping live traffic?
  • Once you've resolved the immediate incident, how do you make sure this doesn't happen again?

“The question sounds broad but they immediately start feeding you context as you go, so it becomes a back-and-forth pretty fast.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta Research Scientist coding round, focused entirely on sparse matrix multiplication. Pretty niche problem but made sense given the role.
  • Given two sparse matrices mat1 (m x k) and mat2 (k x n), compute their product efficiently by exploiting sparsity. How does your approach compare to the naive triple-loop solution in terms of complexity?

“The naive O(m*k*n) solution is the obvious starting point but they clearly wanted more.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Coding screen for a Research Scientist role at Meta. One algorithmic problem, graph-based, cleaner than expected once you see the structure.
  • You have a list of photo pairs where each pair records two consecutively visited locations, but the order within each pair is unknown. Reconstruct the full trip as an ordered path of locations, given that every location was visited exactly once and the trip is not a cycle.

“Took me a minute to see it as a graph problem.”

View Post

Meta·Product Manager·Technical Phone Screen

Apr 2026
Interviewed for a PM role at Meta, got a technical product question about one of their core API endpoints. Short post but the question itself is worth thinking through if you're prepping for Meta.
  • What does the Signup endpoint on Facebook do?

“Seemed deceptively simple and I almost undersold it.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Meta ML engineer interview with a coding question that looked like a string problem but was really about understanding rotational equivalence. Pretty lean on details but the core puzzle was interesting enough.
  • Given a list of strings, group together all strings that are equivalent under some Caesar Cipher rotation (where every character is shifted by the same fixed amount, wrapping around the alphabet).

“My first instinct was to just try all 26 rotations for each string and use that as a key, which works but felt clunky.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Meta onsite for a software engineer role, two back-to-back system design sessions. Both questions were meaty and required going deep on architecture, trade-offs, and security. Left feeling like I could've structured my time better on the first one.
  • Design an online judge platform that compiles and runs user-submitted code across multiple languages, evaluates it against public and hidden test cases, enforces time and memory limits, and returns verdicts like Accepted, Wrong Answer, Runtime Error, and Time Limit Exceeded. Cover APIs, storage, worker scheduling, sandboxing, burst handling during contests, and security.
  • Design a live comment feature for a social media post where new comments appear in near real-time for users viewing the post. Walk through the write path, read path, comment ordering, moderation, and how clients receive updates. Compare long polling, Server-Sent Events, and WebSockets, and explain how you'd handle hot posts with very high fan-out.

“This one ate most of my mental energy.”

View Post