← Back to Directory

Meta interview notes, page 200 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, new agentic format they seem to be testing out. Went in feeling pretty confident since I'd built similar stuff at work, but the interview went sideways in ways I didn't expect.
  • Design an agent system that automatically investigates and resolves support tickets.

“I came in with a plan: triage agent feeds into an investigate agent feeds into a resolve agent, clean pipeline.”

View Post

Meta·Product Designer·Onsite - Product Sense / Strategy

Jun 2026
Meta product design interview, one question about building a grocery delivery experience for COVID. Pretty open-ended, which I wasn't fully prepared for.
  • Design a grocery and essentials delivery app or experience for use during COVID.

“I went straight into features and had to backtrack when I realized I hadn't defined who the user even was.”

View Post

Meta·Product Manager·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Meta, just one question but they really want you to dig into your personal contribution and emotional investment, not just describe what the project did.
  • What project are you most proud of, and why? They want you to go beyond describing the project and explain your specific role in driving it and what makes you personally proud of it.

“I started describing the project itself and about two sentences in I could tell I was losing the thread.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Meta ML Engineer interview focused on a classification problem around harmful item detection. I came prepared, delivered everything I had, but the interviewers seemed checked out the whole time and barely asked follow-ups. Hard to read how it went when you're basically talking into a void.
  • Design a machine learning system to detect harmful items.

“I had a whole prepared answer for this and went through all of it.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Did a coding round for an MLE role at Meta, two questions back to back. Both were string manipulation problems which I wasn't expecting given the role, felt more like a standard SWE screen than anything ML-specific.
  • Given two strings, determine whether they are exactly one edit apart, where an edit is a single insert, delete, or replace operation.
  • Given a word and an abbreviation string, determine whether the abbreviation is valid. Numbers in the abbreviation skip that many characters, letters must match directly, and leading zeros are not allowed.

“The tricky part is handling the length difference case cleanly.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta PM interview with a single product design question about building a betting or auction platform for auction houses. Pretty open-ended, which I wasn't fully prepared for.
  • Design a betting and auction platform for auction houses. Walk through your product thinking.

“I went straight to user personas and that probably cost me the first few minutes.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE interview that extended an in-memory payment system with scheduled payments and cancellation. The problem kept growing with each follow-up, which I wasn't fully prepared for.
  • You have an existing in-memory payment system with immediate transfers and a top-N leaderboard. Extend it to support scheduled payments that execute after a delay, and allow cancellation before they run.
  • When should funds be reserved for a scheduled payment: at schedule time or at execution time? What are the trade-offs?
  • How do you make the cancellation operation idempotent, and how do you handle a cancel-vs-execute race condition?
  • Implement a runner that processes all due payments in chronological order and returns a string summary of which payments executed.
  • How do executed scheduled payments integrate with the existing top-N spenders leaderboard, and how do you ensure the balance update and leaderboard update are atomic?
  • What is the time and space complexity of schedulePayment, cancel, and the due-payment runner?

“This looked manageable at first but kept branching.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Meta virtual onsite coding round, got a tree traversal problem that was close to a well-known leetcode but with a twist thrown in. Nothing too wild but the variation kept me on my toes.
  • Given a binary tree, return the values of the nodes visible from the right side, from top to bottom. The problem had a slight variation from the standard version.

“Knew the base problem cold so I jumped straight to BFS level-order traversal and grabbed the last node at each level.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
A technical screen for a Data Scientist role at Meta focused entirely on one dense experimentation question set inside WhatsApp's Calling org. The whole thing was a single scenario about designing an A/B test for an adaptive codec feature, but it had about eight sub-problems packed into it. Left feeling like I answered the broad strokes but fumbled some of the math under pressure.
  • You're joining WhatsApp's Calling team. A PM wants to test an adaptive codec that should reduce call drops on unstable networks. Design a full A/B test: choose and justify your randomization unit given two-sided exposure and interference, define your primary and guardrail metrics precisely, specify the exposure logic (does the feature activate only when both sides are treated or just the caller?), outline a ramp plan with spillover checks, handle non-independence from repeat callers and seasonality, do a power calculation back-of-envelope given a 3.2% baseline drop rate and 8% relative reduction target, compute the design effect using a caller-level ICC of 0.10, estimate unique callers per arm needed, and state your estimand and estimator including how you'd diagnose interference across treatment arms.

“This was basically a take-home crammed into a live call.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta PM interview with a product design question about building something for hobbyists. Pretty open-ended, which sounds fun until you're actually in it.
  • You're a PM at Meta. Design a product for a hobbyist community (e.g. gardening).

“I spent way too long picking the hobby.”

View Post