← Back to Directory

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

Jun 2026
Meta DS interview focused entirely on content moderation analytics, specifically around report validity and detecting bad actors who spam the reporting system. Two SQL-heavy questions, both with a product reasoning layer underneath.
  • What share of reported users have received at least one valid report? Walk through how you'd define the numerator and denominator and handle any deduplication.
  • How would you identify users who are abusing the reporting feature by filing false reports? Describe the metrics you'd use and write SQL to surface them.

“I jumped straight into writing SQL before fully locking down the definitions, which was a mistake.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Coding round at Meta for a software engineer role. One question, BFS-based tree problem, nothing too wild but definitely requires knowing your traversal patterns cold.
  • Given a binary tree, return its nodes grouped by vertical column, ordered from leftmost to rightmost.

“Went with BFS and tracked column indices in a map alongside the node values.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta product sense interview, one question about designing a financial planning tool on Facebook. Pretty open-ended, which I didn't fully appreciate until I was already mid-answer going in the wrong direction.
  • How would you design a financial planning product on Facebook?

“I jumped straight into features, which was a mistake.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta PM interview with a product sense question about onboarding design tradeoffs. Single question, no extra context on outcome or round structure.
  • You're a PM at Facebook. How would you decide whether to remove the profile photo step from the onboarding flow?

“This one tripped me up a bit because it sounds like a simple yes/no but it really isn't.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round, one algorithm question that looked simple on the surface but they wanted the full treatment: proof of correctness, complexity analysis, and a follow-up about returning the actual indices.
  • Given an array of daily stock prices, find the maximum profit from at most one buy-sell transaction where the buy must occur before the sell. Return 0 if no profit is possible. Solve it in O(n) time and O(1) space, explain your algorithm, prove its correctness, and analyze the complexity. Bonus: return the actual buy and sell day indices.

“I knew this problem cold, or thought I did.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta DS interview with a classic ads revenue diagnostic scenario. One meaty case question about triage and root cause analysis, framed as a real exec briefing situation.
  • Global ads revenue dropped significantly last week. Walk through how you'd diagnose what caused it.

“This is the kind of question where if you just say 'check the dashboard' you're already losing.”

View Post

Meta·Machine Learning Engineer·Onsite - Coding / Algorithms

Jun 2026
Meta ML engineer interview with a set of data structures questions that covered a pretty wide range, from basic array manipulation to grid pathfinding to streaming data design. Nothing wildly unexpected but the depth expected on each one was real.
  • Given two sorted integer lists, merge them into a single sorted array. Then for a target value x, return the index of the first element greater than or equal to x (lower bound) and the index of the first element strictly greater than x (upper bound). Discuss time and space complexity, and handle duplicates and empty inputs.
  • Implement a function that finds the minimum value in an array. Discuss different approaches and edge cases for both sorted and unsorted inputs.
  • Given a 2D grid of open cells and walls, and a starting cell, find a path to any open cell on the boundary of the grid. Return the path as a list of coordinates. Discuss BFS vs DFS, path reconstruction, and complexity.
  • Design a class that tracks a stream of numbers and returns the average of the last k values after each new value is inserted. Updates and queries should be amortized O(1), and you need to define behavior when fewer than k elements have been seen so far.

“This felt like two questions stitched together.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Meta system design round focused entirely on a food ordering and delivery platform. It went deeper than I expected, covering basically every layer from data modeling to courier dispatch logic.
  • Design an end-to-end food ordering and delivery system.
  • How would you model the data for this system, and how does order state transition from placed to delivered?
  • What's your strategy for matching couriers to orders, and how do you estimate delivery time?
  • Where are the single points of failure in this architecture, and how do you address them?
  • How would you scale and partition this system under high load?

“I started with requirement clarification which felt good, asked about the main actors (customer, restaurant, courier), payment flow, scale expectations.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Product analytics case for a DS role at Meta, focused entirely on measuring a Group Call feature. Pretty intense depth required across metrics, retention math, and experimentation. No behavioral questions from what I remember, just this one big case that kept branching.
  • What is the product goal for a Group Call feature, and what north-star metric would you use to measure it?
  • Propose a full set of success metrics covering adoption, engagement, and call quality for the Group Call feature.
  • How do you define user retention for this feature, and what's the distinction between overall app retention, Group Call feature retention, and retention broken down by call creators versus invited participants?
  • Walk through how you'd define and calculate 7-day and 28-day retention for Group Call users, including exact formulas, cohort definitions, and when each window is more useful.
  • How would you think about the tradeoff between short-term metric gains and long-term user experience for Group Call changes?
  • If you were running an experiment on a Group Call improvement, what would your primary metric be, what guardrail metrics would you set, and how would you handle network effects or interference between users?
  • What user segmentations would you examine before deciding whether to launch a Group Call change?

“I went with something like 'weekly active group callers' and the interviewer pushed back asking whether that captures quality or just volume.”

View Post

Meta·Software Engineer·Hiring Manager Screen

Jun 2026
Went through a Meta interview that had at least one behavioral question about managing underperformers. Short on details but it's the kind of question that trips people up if they haven't actually had to do it.
  • Have you ever had to let someone go due to low performance? Walk me through what happened.

“This one requires a real story and I think a lot of people either don't have one or try to borrow someone else's.”

View Post