← Back to Directory

Meta interview notes, page 189 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 - Cross-functional / Panel

Jun 2026
Research round at Meta for a Research Engineer role. The last chunk of the interview opened up into a pretty free-form discussion about building an AI agents team from scratch, which was a nice change of pace from the usual grind but also harder to prepare for than I expected.
  • If you had unlimited resources, how would you build a team focused on AI agents? Walk through team composition, research priorities, infrastructure investments, evaluation strategy, and how you'd structure milestones.

“This was the whole last 20 minutes and I kind of underestimated how much ground it would cover.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta data scientist SQL round, two tasks in one problem set. The question was dense and the edge cases were the whole point, not an afterthought.
  • Given two tables tracking post views and reactions, write SQL to count distinct posts that had at least one view from an unconnected user lasting more than 60 seconds in a 7-day window. If the same user viewed the same post multiple times on the same day, deduplicate by taking the max duration before applying the filter.
  • Using the same two tables and 7-day window, compute the average reactions per post for Friend vs Unconnected viewers. Join reactions to views on post_id, viewer_id, and ds. When multiple view rows match a single reaction, use the one with the highest duration. The denominator should be all distinct posts that appeared in views for that group, including posts with zero reactions.

“The dedup step tripped me up at first.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Meta system design round, proximity search in the style of Yelp or Google Maps. Pretty standard for this level but there's a lot of surface area to cover and the time goes fast.
  • Design a proximity search service similar to Yelp or Google Maps. The system should store places with attributes like name, coordinates, category, and rating, support radius-based queries with filtering and sorting, handle high read throughput with moderate writes, and keep data reasonably fresh.

“I spent too long on the data model upfront and barely had time to talk through the geospatial indexing side, which is obviously the core of the problem.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Meta for a software engineering role. The prompt was to design a LeetCode-style coding platform end-to-end, which sounds straightforward until you start thinking about sandboxed code execution at scale. A lot of ground to cover in one session.
  • Design an online coding practice and interview platform similar to popular coding challenge sites. Cover the full system: architecture, data modeling, code execution with sandboxing, scaling the judge layer, caching, and how you'd evolve the design over time.

“This one ate up a lot of time because I kept wanting to jump straight into the execution sandbox piece, which is the fun part, but the interviewer kept pulling me back to basics like auth flows and problem storage.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta DS technical screen, three SQL problems back to back with a shared schema. The questions escalated pretty fast from basic aggregation to funnel metrics with dedup logic. Felt like a timed exam more than a conversation.
  • Given a posts table and a comments table, for each calendar day compute the total number of posts created and what percentage of those posts received at least one non-deleted comment within 24 hours of the post being created.
  • For the past 30 days, find the top 3 users by their rate of posts that received at least one non-deleted comment within 24 hours. Only include users with at least 5 posts. Break ties by higher post count first, then lower user_id.
  • For the reengage_v1 email campaign, compute daily unique open rate and click-through rate. The denominator should be delivered sends only (exclude bounced sends). Count at most one open and one click per send_id. Return campaign, date, delivered send count, unique opens, unique clicks, open rate, and CTR.

“The is_deleted filter is easy to forget under pressure and I almost did.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Meta ML Engineer interview with a debugging-focused coding round. The question looked approachable until I realized how much nuance they wanted out of a 'simple' BFS fix.
  • You're given a BFS implementation that loops infinitely on certain inputs. Find the bug and fix it, then explain your fix and its implications for correctness and complexity.

“The bug was pretty obvious once I saw it, no visited tracking anywhere.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round with a grid/island problem. Pretty standard stuff but the follow-up pressure to optimize was real.
  • Given an n x n binary matrix, you can flip at most one 0 to a 1. What is the maximum possible island area you can achieve? Islands are groups of 1s connected in four directions.

“My first instinct was just BFS every cell and try flipping each zero, which works but is way too slow for a 500x500 grid.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta Research Scientist coding round, basically a Number of Islands variant with some twist the interviewer layered on top. Standard graph traversal stuff but the add-on is what they're really testing.
  • Given a binary grid where 1s represent land and 0s represent water, count the number of distinct islands. An island is a group of land cells connected in four directions. The interviewer then adds a follow-up variant on top of the base problem.

“I went with DFS first because it's the quickest to write under pressure, got through the base case fine.”

View Post

Meta·Technical Program Manager·Onsite - System Design / Architecture

Jun 2026
Had a system design/architecture round at Meta for a TPM role. One question, pretty open-ended, and I walked away feeling like I could have gone deeper on the tradeoffs.
  • Describe a time you were involved in designing system architecture. What components did you work with and what was your specific role?

“I picked a project where I was more of a coordinator than a true architect and I think that hurt me.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Did a technical phone screen for a SWE role at Meta. Just the one coding problem, nothing too wild, but the edge case handling is where it gets interesting.
  • Given a string, determine whether it can be made into a palindrome by removing at most one character.

“Classic problem but the off-by-one logic when you find the first mismatch trips people up.”

View Post