← Back to Directory

Meta interview notes, page 213 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 - Product Sense / Strategy

Jul 2026
PMM interview at Meta, one question that sounds breezy until you realize how much structure they actually want underneath it.
  • Pick an app you use all the time. Now walk me through how you'd take a brand new feature of that app to market.

“I picked Instagram and immediately second-guessed myself since, you know, Meta.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jul 2026
Meta data scientist interview with a couple of SQL questions built around Instagram's video call data. Nothing too crazy on the surface, but the second question had a few moving parts that tripped me up a bit.
  • Using video call logs from the past 7 days, how many users initiated a call with more than 3 distinct people?
  • Of French users who were daily active yesterday, what percentage appeared in at least one video call (as either caller or recipient)?

“Seemed straightforward but I almost forgot to filter by the date range properly.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jul 2026
Meta SWE coding round, one question, string parsing. Not glamorous but not easy either.
  • Given a string, determine whether it represents a valid number. Valid numbers include integers, decimals, and values with an exponent (e/E) followed by a signed integer. Strings like '0.1', '+3.14', '2e10', and '3e+7' are valid; strings like '1e', 'e3', '99e2.5', and '--6' are not.

“Looked simple and then I started listing edge cases and it just kept growing.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jul 2026
Did a coding round at Meta for a software engineer role. One question, BST-based, felt manageable but I second-guessed myself more than I should have.
  • Given a binary search tree and a range [low, high], compute the sum of all node values that fall within that range.

“My first instinct was to do a full traversal and just skip nodes outside the range, which works but ignores the BST property entirely.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jul 2026
Meta SWE interview that focused on designing a mini banking system from scratch. Pretty involved for a coding round, felt more like a system design question dressed up as an OOP problem.
  • Design a BankSystem class with createAccount, deposit, and pay methods. Define the data models, validation rules, return values, and the data structures backing each operation. What are the time and space complexities?

“This one sprawled way more than I expected.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Meta SWE system design round where I had to design a chess game from scratch. Not the most common design problem so it threw me off a bit, but it covered a decent range of concepts.
  • Design a chess game that supports friend invitations, move undo (only before the opponent responds), and a live leaderboard showing win/loss rankings.

“The undo mechanic is where I got tripped up.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jul 2026
Meta PM interview with a product design question around travel and home-swapping. Pretty open-ended, which I wasn't fully prepared for.
  • Design a product that helps people swap or exchange homes while traveling.

“I went straight to user segmentation and started listing traveler types, which felt okay in the moment but in hindsight I spent way too long there.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Jul 2026
Four independent coding problems in what felt like a Meta onsite coding round. The problems ranged from a grid simulation to a segment tracking problem to something that looked deceptively easy but had a weird edge case buried in it. No behavioral stuff, just pure coding the whole time.
  • Simulate placing a sequence of Tetris-like pieces (types A through E, no rotation allowed) onto an n x m grid. For each piece, find the first valid top-left anchor by scanning top-to-bottom then left-to-right, place it there, and stop if no valid placement exists. Return the final grid state.
  • Given a sequence of house-building operations on an integer number line (coordinates can be in the billions), after each build output the length of the longest contiguous segment of built positions.
  • Starting from a rating of 1500, apply a sequence of rating changes. Return both the maximum rating ever reached and the final rating.
  • Given an array of non-negative integers, repeatedly find the leftmost nonzero element x, subtract x from consecutive elements to its right as long as each element is >= x, add x to a result accumulator, and repeat until the array is all zeros. Return the accumulated result.

“The scan order part is what gets you.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Meta system design round, one big question about WhatsApp architecture with a follow-up on scale and reliability. Pretty open-ended, which I wasn't fully prepared for.
  • Design the system architecture for WhatsApp, and walk through how you'd handle scale, performance, and reliability.

“I started with the messaging flow and worked outward but spent way too long on the client-server handshake before even touching storage or delivery guarantees.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jul 2026
Meta SWE coding round with a bitmask-style subset problem. Pretty clean problem statement but the edge cases around repeated characters within a single word tripped me up at first.
  • Given a list of words, find the largest subset you can concatenate such that no character appears more than once across the whole concatenated string. Each word itself must also have no repeated characters. Return the maximum total length.

“My first instinct was greedy and it was wrong.”

View Post