← Back to Directory

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

May 2026
Meta data scientist interview, one meaty ML evaluation question that covered a lot of ground fast. The kind of question where you think you know the answer and then realize halfway through you've forgotten to mention half the important stuff.
  • How would you design an offline evaluation framework for a video harm classifier? Walk through your choice of metrics, how you'd handle class imbalance, how ground truth gets collected, how you'd pick a classification threshold given business costs, and any fairness checks you'd run.

“This question sprawls in ways that are easy to underestimate.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview focused entirely on FB Locals, a local business review product. Both questions came from the same scenario but hit very different angles, one defensive and one adversarial, which I wasn't really prepared for.
  • You're the PM for FB Locals, a product that lists reviews of local businesses. How would you approach authenticating reviews, and what would you build?
  • Now flip it: you're a small business in an emerging market and you're building a fake review operation targeting FB Locals. What do you build and what's your process?

“I went straight to verification signals like account age, purchase history, check-in data.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE coding round, one question, pretty standard stuff but the pressure is always real with that company.
  • Given an array of integers and an integer k, find the kth largest element in the array.

“Knew this one.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta product analytics interview, one question about A/B testing for a checkout feature with a specific constraint baked in. Short session, felt more like a screen than a full loop.
  • How would you analyze the results of an A/B test for one-click checkout when that feature is only available for a single payment method?

“The constraint is the whole point of the question and I almost glossed over it.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta infrastructure engineer screen, one coding question, pretty standard algorithmic stuff. Nothing surprising about the format but the problem itself has a subtle trick that I didn't fully nail on the first pass.
  • Given an integer array that may include negative numbers and an integer k, find the total count of contiguous subarrays whose elements sum to exactly k.

“I jumped straight to the brute force O(n²) approach and the interviewer let me run with it for a bit before nudging me toward something better.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta coding round, tree problem that looked familiar until it wasn't. The twist on the classic consecutive sequence question tripped me up more than I expected.
  • Given the root of a binary tree, find the longest strictly increasing top-down path (each child's value must be greater than its parent's) and return the actual sequence of node values, not just the length.

“I'd seen the length version before so I felt pretty good at first.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

May 2026
Meta SWE coding round, one problem the whole session. It looked like a CRUD exercise at first glance but the locking semantics kept layering on and by the end I was juggling five different query types with edge cases I hadn't thought through.
  • Design and implement an in-memory key-record database that supports field-level CRUD operations and an exclusive per-record locking mechanism, processing a sequence of typed string queries and returning their outputs.

“Spent the first few minutes thinking it was basically just a nested hashmap problem, which it mostly is, but then the locking rules started stacking up.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE coding round, one question, graph stuff. Not the worst session I've had there but definitely made me think harder than I expected about cycle detection.
  • Given a list of courses and their prerequisites, determine whether it's possible to complete all courses without getting stuck in a circular dependency.

“Classic topological sort / cycle detection problem.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Meta for a software engineer role. The whole thing was a deep dive into designing a food/grocery delivery marketplace, and they really pushed on the specifics rather than letting you stay high-level.
  • Design an on-demand local delivery marketplace that supports customers browsing merchants, placing orders, merchants preparing orders, couriers accepting and completing deliveries, and real-time tracking with notifications.
  • How would you design shopping cart persistence so that a cart survives app closes, device switches, and network outages, including handling anonymous versus logged-in users and conflict resolution?
  • How would you handle continuous GPS updates from couriers, including ingestion at scale, storing location history, fanning out to customers and dispatch systems, rate limiting, and privacy considerations?
  • Walk through the full order lifecycle state machine, including how services communicate across state transitions and how you prevent invalid or out-of-order state changes.
  • How would you design the system to handle traffic spikes during peak meal times, covering APIs, caching, queuing, failure handling, and observability?

“Big open-ended prompt to start.”

View Post

Meta·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Meta for a software engineer role. Just one question but they really dug into it.
  • Tell me about a project you worked on that failed or fell short of its goals. What were you trying to accomplish, what went wrong, what did you actually do, and what did you take away from it?

“The failure part is easy to talk about but I fumbled the 'what did you do specifically' section.”

View Post