← Back to Directory

Meta interview notes, page 29 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·Technical Phone Screen

Apr 2026
SQL round for a Product Analyst role at Meta. Three questions, all variations on the same calls/users schema, progressively trickier. Nothing brutal but the third one tripped me up a bit.
  • Given a calls table with a pickup flag and call type, write a query returning the total number of calls and the number of picked-up calls broken down by call type.
  • For a given country, compute the pickup rate (as a percentage) for calls placed by senders from that country. You need to join the calls table to a users table to get the sender's country.
  • What percentage of distinct callers have made at least one video call AND at least one voice call? The denominator should be all distinct senders in the calls table.

“Pretty standard aggregation warmup.”

View Post

Meta·Data Scientist·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Meta for a data scientist role. The question was a beast, basically a full negotiation case study wrapped in a conflict scenario, and I was not ready for how deep they wanted me to go.
  • Walk through a real cross-team conflict where incentives were misaligned and time was short. Map out each stakeholder's goals and fallback position, then describe the negotiation plan you'd build with data, the meeting agenda you'd actually run, how you'd decide when to escalate, how you'd keep the relationship intact if the other team kept blocking you, and how you'd measure success beyond just shipping the thing.

“This is not a behavioral question, it's a case study pretending to be one.”

View Post

Meta·Data Scientist·Technical Phone Screen

Apr 2026
Meta data scientist interview with a SQL question focused on content safety metrics. Pretty straightforward setup but the specific angle they were going for took me a second to figure out.
  • Given a table of videos with a harmful content flag and a table of views with timestamps, write a SQL query that calculates the daily percentage of views that were on harmful videos.

“I knew I needed a join and a group by date, but I fumbled the aggregation syntax for a minute.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Did a system design round at Meta for a software engineer role, got asked to design a distributed messaging system along the lines of Kafka. Not a lot of context to share beyond the question itself, but it's the kind of thing that can go sideways fast if you haven't thought through partitioning and consumer group semantics before walking in.
  • Design a distributed queue service similar to a Kafka-style messaging system.

“This is the kind of question where you can talk for 45 minutes and still feel like you barely scratched the surface.”

View Post

Meta·Data Scientist·Technical Phone Screen

Apr 2026
Meta DS interview focused entirely on spam detection for friend requests, which sounds scoped but actually sprawls into labeling strategy, model design, and business tradeoffs. A lot to cover in one session.
  • How would you define a 'spammy' friend request on a social platform, and what signals or features would you engineer to detect them?
  • Walk me through how you'd build a classification model to flag spammy friend requests.
  • If you have no labeled data to start with, how do you get labels for training a spam detection model?
  • Once the model is deployed, how would you use it to actually improve the user experience, not just flag spam internally?
  • How do you decide on the right precision-recall tradeoff for a spam detection system, and how do you monitor it over time?

“I started with obvious stuff like request volume per hour and acceptance rate, but the follow-up pushed me to go deeper.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Meta software engineer interview with three coding problems, two graph/tree questions and one string manipulation. Pretty standard algorithmic round, nothing too surprising.
  • Given a string with parentheses, remove the minimum number of characters to make it valid.
  • In a binary grid, you can flip one 0 to a 1. Find the size of the largest island you can form after the flip.
  • Return the values visible from the right side of a binary tree, level by level.

“Stack-based approach, track indices of unmatched parens and remove them at the end.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Meta system design round focused on building a video platform at YouTube/Netflix scale. Pretty deep dive into the full pipeline from upload to playback, and they clearly wanted you to sweat the details on transcoding and streaming.
  • Design a large-scale video platform similar to YouTube or Netflix, covering upload, transcoding, and streaming.
  • How would you handle resumable video uploads and storing playback progress for users?
  • How would you design the streaming layer to achieve low startup latency at scale?
  • Walk through how a platform like Netflix ingests a pre-existing content catalog versus how YouTube handles user uploads.

“I started with the upload path and worked forward, which felt natural but I think I spent too long on chunked/resumable uploads before getting to the more interesting stuff.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview with a product design question about improving the layover experience. Pretty open-ended, which I wasn't fully prepared for.
  • Design a Facebook product that improves the experience of being stuck at an airport during a layover.

“I spent the first minute trying to figure out why Facebook specifically would care about layovers, which probably wasn't the best use of time.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Meta for a software engineer role. The question was a full end-to-end design of a distributed job scheduler, cron-style but fault-tolerant and scalable. Pretty meaty for a single session.
  • Design a distributed job scheduler that supports one-time, immediate, and recurring jobs, runs them on a scalable worker fleet, and handles fault tolerance, retries, and at-least-once (or exactly-once) execution guarantees end-to-end.

“This one sprawls in every direction.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta coding interview that went deeper than I expected. Started with a maze solver and then they kept adding constraints until it got genuinely tricky.
  • You have a maze solver. Extend it to support directional doors, where each door only allows passage from one specific side. How do you model and traverse these correctly?
  • What happens when a door's allowed direction points directly into an adjacent wall? How do you make sure your solver blocks that path correctly instead of producing a broken step?

“I got the basic idea pretty fast, treat each door as a directed edge rather than a bidirectional one.”

View Post