← Back to Directory

Meta

FAANG / Big Tech

Most of these Meta write-ups come from Software Engineers (373), then Machine Learning Engineers (105) and Product Managers (5). The most reported rounds are the technical phone screen (289), the system design round (88), the behavioral / leadership round (56) and the onsite coding round (44).

490 interview notes · updated Jun 2026

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
ML system design round at Meta for a research scientist role. The prompt was about detecting weapon sales, which sounds straightforward until you actually try to spec it out.
  • Design an ML system to detect the sale of weapons on the platform.

“This one had a lot of surface area.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round, basically one classic array problem with a couple of follow-ups on complexity. Nothing crazy but the follow-ups are where they actually separate people.
  • Given an integer array and an integer k, find the k-th largest element in the array.

“Started with sorting, which works fine and I said the complexity out loud before they could ask.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round, one question the whole time. The problem sounds straightforward until you realize they want O(log n) and suddenly you're rethinking everything you thought you knew about binary search.
  • Given an integer array where no two adjacent elements are equal, find any peak element. A peak is an index where the value is greater than both its neighbors, with the array boundaries treated as negative infinity. Solve it in O(log n).

“I started with the linear scan and they let me finish before asking if I could do better.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Meta for a software engineer role. The question landed well because I'd reviewed it recently, which made a real difference.
  • Design an online game leaderboard system.

“Timing was lucky here.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Meta system design round for a software engineer role, and it did not go well. The question was about designing a web crawler at scale across 10k machines, and I fumbled the capacity estimation part badly enough that it cost me the offer.
  • Design a web crawling system that runs across 10,000 machines. Consider distributed caching, deduplication, and network throughput.

“I skipped capacity estimation early on because the interviewer said it was 'up to me' when I asked.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Meta MLE technical phone screen focused on a single coding problem with a twist: they wanted two distinct solutions, not just one that works. The problem itself was straightforward but the O(1) space angle is where things got interesting.
  • Implement a calculator that evaluates an arithmetic expression string containing only non-negative integers, '+', '*', and optional whitespace. No parentheses. Standard operator precedence applies (multiplication before addition). Provide both a split-based solution and a single-pass O(1)-space solution, and explain the tradeoffs.

“The split approach clicked fast: split on '+', then for each chunk split on '*' and multiply across, then sum everything.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta Research Scientist coding round, one question about simulating a sequence of operations on a 2D array. Pretty implementation-heavy, less algorithmic insight and more just not messing up the indexing.
  • Given a 2D array and a list of operations to apply in order, implement each operation: swap two rows, swap two columns, reverse a row, reverse a column, and rotate the entire grid 90 degrees (transpose then reverse each row).

“The rotation tripped me up a bit.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta research engineer screen, focused entirely on implementing self-attention from scratch. One question, pretty deep, and they wanted both the math and working code before moving on.
  • Implement scaled dot-product self-attention from scratch using NumPy or PyTorch. Given query, key, and value tensors of shape (batch, seq_len, d_k), compute the attention output using the formula softmax(QK^T / sqrt(d_k)) * V. Walk through the math first, then write the code. Optionally handle a causal mask.

“They asked me to explain the math before touching any code, which I actually appreciated because it slowed me down enough to not make the classic mistake of forgetting the sqrt(d_k) scaling.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Meta MLE interview focused on a pretty meaty ML system design question around feature engineering for the News Feed ranking model. The follow-up about offline vs online metric gaps was where things got interesting and honestly a bit uncomfortable.
  • There's an existing model predicting the probability a user likes a News Feed post. How would you add a new feature capturing whether the user liked posts from a specific author (or a specific post) in the last 6 months? Walk through feature engineering, how you'd serve it at inference time, and how you'd avoid label leakage during training.
  • Once you have that feature, how do you integrate it into the existing model? Should it go in as a raw numeric feature, get embedded, or be constructed as an interaction term with something else? What's the risk to existing features?
  • How would you validate whether this feature actually helps? What offline metrics would you look at, and how would you slice the analysis?
  • Say your offline metrics improve but the online A/B test shows no meaningful gain. What are the possible explanations and how do you debug it?

“This is the kind of question where I started confident and slowly realized I was glossing over the hard parts.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta coding screen, pretty standard stuff. One interval problem and that was basically it.
  • Given an array of intervals, merge all overlapping ones and return the resulting non-overlapping set.

“Sort first, that's the key move.”

View Post

Meta interview guides

Online Assessment

18 Meta OA Reports 2026: CodeSignal Questions and Formats

Software Engineer

Meta Software Engineer Interview 2026: Inside a Senior System Design Case

Software Engineer

Meta Software Engineer Interview 2026: What a Real Technical Screen Reveals

Data Scientist

Inside the Meta Data Scientist Interview in 2026: SQL, Product Analytics & a Real Technical Screen

Meta interview FAQ

What rounds are in the Meta interview?

Candidates most often report a technical phone screen (289 write-ups), a system design round (88), a behavioral / leadership round (56) and an onsite coding round (44).

What does the Meta technical phone screen cover?

Across 289 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (315 questions), Technical Trade-offs (154) and System Design (68).

What is asked in the Meta system design round?

Across 88 system design write-ups, the most tagged question topics are System Design (207 questions), Technical Trade-offs (171) and Data Modeling (59).

Meta interview guides by role

373 notes

Meta Software Engineer interview questions

105 notes

Meta Machine Learning Engineer interview questions