← Back to Directory

Meta interview notes, page 39 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·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at Meta with one product sense question that sounds breezy until you realize they want you to actually think about platform integration, not just describe an app you like.
  • What's your favorite app, and how would you build it into or on top of the Facebook platform?

“I picked an app I genuinely use and spent too long on the 'why I love it' part, which is not what they care about.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE coding round with two LeetCode-style problems. Nothing too exotic but the combination felt deliberate.
  • Given an array of weights, implement a function that randomly picks an index such that the probability of picking each index is proportional to its weight.
  • Given an integer array, return a new array where each element is the product of all other elements in the original array, without using division.

“Prefix sums plus binary search.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Meta system design round with two back-to-back prompts, both pretty meaty. No fluff questions, just two hours of whiteboarding distributed systems under pressure.
  • Design a distributed, durable queue or event-streaming service that supports high-throughput publishing, consumer groups with offset tracking, message replay within a retention window, partition-level ordering, replication, and failure recovery.
  • Design the request and matching flow for a ride-hailing service where a rider sees multiple interested drivers, picks one themselves, and the chosen driver must then confirm before the trip is assigned. Handle cancellations, timeouts, race conditions, and duplicate requests.

“This one I felt okay about until the backpressure piece came up.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Meta SWE coding round, one question the whole time. Pretty standard algorithmic problem but the constraint about not fully sorting the array is where things get interesting if you haven't thought about it before.
  • Given an array of integers and a value k, return the k-th largest element. You should do this without fully sorting the array.

“My first instinct was just sort and index, which obviously misses the point of the constraint.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta coding interview with a maze/grid navigation problem. The kind of question that sounds straightforward until you're actually implementing it live and second-guessing every recursive call.
  • You have two API functions for a mouse on a grid you can't see directly. One tells you if the mouse can move in a given direction without hitting a wall, the other actually moves the mouse and tells you if it found the cheese. The grid layout and cheese position are unknown. Write an algorithm to navigate the mouse to the cheese and track the path or step count.

“My first instinct was DFS with backtracking and I think that was right, but implementing it cleanly with the visited set tripped me up.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview with a product design question focused on building something for handymen. Short on details but the prompt itself is a decent one to prep for.
  • Design a product for handymen. What would you build and why?

“This is a fun one because handymen are a pretty underserved user group in tech.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Got a product strategy question at Meta for a PM role, basically one of those classic 'should these two products be separate or combined' setups. Pretty short session from what I can tell.
  • Should Uber Eats be a separate app from Uber Rides, or should they be combined into one?

“This looks deceptively simple but there's a lot to unpack.”

View Post

Meta·Software Engineer·Hiring Manager Screen

Apr 2026
Interviewed for a BA role at Meta and got hit with a classic revenue drop diagnostic question. Short round, felt more like a case screen than a full interview.
  • How would you walk leadership through a sudden, unexpected drop in revenue?

“I went straight to segmentation: is it one product, one region, one channel?”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE interview with a maze exploration problem that's basically BFS but wrapped in a weird API abstraction layer. The follow-up on edge cases and unit tests was where things got interesting.
  • You're given a black-box 2D maze interface with only local actions: move in a direction (returns success/fail), get current position, and check if you've found the cheese. Design an algorithm to reach the cheese in the fewest steps, minimizing redundant moves. Cover visited-state tracking, frontier management, termination, and complexity relative to reachable cells.
  • Propose unit tests for the maze exploration algorithm covering: obstacles at the start position, multiple cheeses, unreachable cheese, mazes with loops, unknown/unbounded grid size, and large open areas.

“My first instinct was to just say BFS and call it a day, but the tricky part is you can't teleport.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a data analyst role at Meta, got a product analytics question that seemed straightforward but had a lot of moving parts once I started talking through it.
  • You have product adoption data broken down by region. How do you figure out which regions had the most successful rollout, and what's driving the difference?

“I started by talking about raw adoption rates but quickly realized that's too surface-level.”

View Post