← Back to Directory

Meta interview notes, page 157 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

Jun 2026
Meta system design round for a software engineer role, single question but it sprawled into basically every distributed systems topic you can think of. Left feeling like I'd covered a lot of ground but not sure I went deep enough on any one piece.
  • Design a system that computes each user's top 10 most-listened-to songs, covering everything from event ingestion through to the API that serves the results.

“This thing kept expanding.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Meta system design round for a software engineering role, and they threw a full online auction platform at me. It was one of the more sprawling prompts I've seen, covering everything from bid concurrency to payment escrow to real-time latency targets. Left feeling like I covered maybe 70% of what they wanted.
  • Design an online auction platform supporting English-style auctions with reserve prices, bid increments, proxy bidding, soft-close mechanics, and an optional buy-it-now feature.
  • How would you design the PlaceBid API to handle concurrency and idempotency, and how do you prevent two bidders from simultaneously winning the same auction?
  • How would you implement real-time bid updates and push them to millions of concurrent watchers with p99 latency under 200ms?
  • How would you handle auction finalization at scale, including failure recovery if the close process crashes mid-execution?
  • What mechanisms would you put in place to prevent bid sniping and detect fraudulent bidding patterns?
  • Walk me through the payment and escrow flow after an auction closes, including how you'd handle a winning bidder who fails to pay.
  • How would you shard and partition this system to support 500,000 concurrent auctions, and how do you maintain bid ordering across partitions?
  • What key metrics and alerts would you define for this platform, and how would you ensure auditability of all bid and payment events?

“The scope of this thing hit me pretty fast.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta coding screen, debugging flavor. They gave me a broken maze solver and wanted me to fix it. Not the hardest problem but I definitely overthought the solution before landing on something obvious in hindsight.
  • You're given a maze-solving function that's too slow because it keeps revisiting the same cells. Find the bug and fix it.

“I spent way too long staring at the traversal logic trying to find some fancy structural issue.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Meta with a single product strategy question about expanding Notion into Europe. Not much to go on from the session itself but the question was meaty enough to chew on for a while.
  • How would you approach expanding Notion into the European market?

“This is the kind of question where you can go a dozen directions and that's kind of the problem.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round, one question, pretty classic but the in-place constraint is where things get interesting. Short session, nothing behavioral.
  • Given two sorted arrays where the first has extra space at the end to fit the second, merge them in-place so the result is sorted. For example, merging [1,2,5,7,0,0,0] and [3,4,6] should give [1,2,3,4,5,6,7].

“My first instinct was to start from the front and shift elements right, which is the obvious wrong move because you end up doing a ton of unnecessary work.”

View Post

Meta·Backend Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Meta for a backend role. Three questions, all conflict and delivery themed. Nothing technically surprising but the delivery one tripped me up more than I expected.
  • Tell me about a conflict you had at work and how you resolved it.
  • Describe a time you had to work with a difficult colleague or a strained working relationship. How did you handle it?
  • Tell me about a time you missed a deadline. What happened and what did you take away from it?

“I had a story ready for this but partway through I realized it made me sound more stubborn than collaborative.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta coding interview covering four problems, all with a 'k' theme or string manipulation angle. Pretty standard algorithmic stuff but the variety kept it interesting.
  • Given a singly linked list, find and return the k-th node from the end.
  • Given an integer array, return the k most frequently occurring elements.
  • Given a list of 2D points, return the k points closest to the origin.
  • Given a string where adjacent identical characters repeatedly collide and disappear (for example 'abbba' becomes 'aa' then becomes an empty string), return the final result after all collisions.

“Classic two-pointer setup.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Meta for a software engineering role, focused entirely on building a real-time live comments system at massive scale. The scope was broad and the follow-ups kept coming.
  • Design a real-time live comments system for a live video product, covering ingestion, fan-out to many concurrent viewers, comment ordering, and replay/history for late joiners.
  • How would you handle a stream that suddenly goes viral, where one video is getting orders of magnitude more traffic than typical?
  • How do you enforce rate limiting and moderation for comments in this system, especially at high throughput?

“This one sprawled fast.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round with a linked list problem. Pretty classic deep copy question but the random pointers make it messier than it looks at first glance.
  • Given a linked list where each node has a next pointer and a random pointer that can point to any node in the list, implement a deep copy of the entire list.

“The random pointers are what get you.”

View Post

Meta·Software Engineer·Onsite - Product Sense / Strategy

Jun 2026
Did a product design interview at Meta with a single hardware/software product question. Pretty open-ended, which I wasn't fully prepared for.
  • Design a smart lock.

“I jumped straight to features without really nailing down who the user was.”

View Post