← Back to Directory

Meta interview notes, page 172 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·Onsite - Behavioral / Leadership

Jun 2026
Prepped for a Meta Data Scientist behavioral loop and the main ask was a long-form story about pushing back on bad metrics under deadline pressure, plus the usual self-intro and company questions. Felt more like a values audit than a technical screen.
  • Tell me about a time you pushed back on stakeholders to protect the integrity of an analysis when you were under deadline pressure. Walk me through the situation, what you were trying to accomplish, what you actually did, and what came of it.
  • What are your main strengths and your biggest weakness right now?
  • Why Meta specifically, and why this team?
  • How would you describe Meta's mission in your own words?
  • What questions do you have for us?

“This was the centerpiece question and I spent probably 80% of my prep time on it.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Meta SWE interview using an AI-assisted coding environment where you're given a broken maze solver and asked to fix and extend it across four progressively harder subproblems. Interesting format, not a typical leetcode grind.
  • The maze solver's print function is producing incorrect output. Find and fix the bug.
  • The BFS implementation in the maze solver doesn't track visited cells. Fix it so the solver doesn't loop infinitely.
  • Extend the maze solver to support two new directional cell types that act as one-way passages.
  • Further extend the maze solver to handle keys and locks, where certain paths are only accessible if the solver has picked up the right key.

“Warmup task but I still fumbled around longer than I should have.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta coding screen, one algorithmic problem about array equilibrium. Pretty focused session, no fluff.
  • Given an array of integers, find an index where the sum of all elements to its left equals the sum of all elements to its right.

“My first instinct was to brute force it with two nested loops and I actually started explaining that before catching myself.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Meta system design round for a software engineer role. One big open-ended question about building a coding platform at scale, which sounds straightforward until you realize how many moving parts they actually want you to cover.
  • Design a coding platform like LeetCode that supports large-scale code execution and a live global leaderboard. Cover how you'd handle test case storage, orchestrate code execution, make the message queue fault tolerant, and scale the whole thing.

“I started with the leaderboard because it felt like the flashiest part and I figured I'd impress them.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta DS interview focused on a single meaty product analytics case about an AI ad creation feature. No fluff, just one long question that kept branching into harder sub-problems the more you answered.
  • How would you evaluate whether Meta's AI-assisted ad creation feature should launch, covering success metrics, experiment design, incremental impact versus cannibalization, and key risks like selection bias and auction interference?

“This one sprawled in a way I wasn't ready for.”

View Post

Meta·Product Manager·Onsite - Multi Round

Jun 2026
Meta PM loop, three questions that all had some version of 'tell me about a time you did something hard and learned something.' The big data question was the one that tripped me up the most.
  • Walk me through the most technically complex project you've led and what makes you proud of it.
  • Describe a situation where you used large-scale data or experimentation to drive a major product decision.
  • Tell me about a product failure you were involved in and what you took away from it.

“I had a good story ready but fumbled the 'why proud' part.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Meta MLE interview with a tree traversal problem that had a few possible variants depending on how the interviewer wanted to push it. Pretty standard algorithmic round but the edge case discussion is where things got interesting.
  • Given the root of a binary tree, return the node values visible from the right side of the tree, ordered top to bottom. A follow-up variant may ask you to fall back to the leftmost node when no right child exists, or return both left and right views.

“I went with BFS and grabbed the last node at each level, which works cleanly.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineer / ML intern role at Meta, two algorithmic questions back to back. Both were graph/grid problems which I should have been more prepared for.
  • Given an undirected, connected, acyclic graph (a tree) with n nodes and n-1 edges, find the length of the longest path between any two nodes. Describe your algorithm and analyze its time and space complexity.
  • You have an n x n grid where 0 is a free cell and 1 is an obstacle. Starting from the top-left corner, find the shortest path to the bottom-right corner using BFS. Then, as a follow-up, describe how you would enumerate ALL simple paths and discuss the complexity and practical limits of doing so.

“This is the classic tree diameter problem.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta PM interview, one question about measuring the success of Instagram's verified badge feature. Not much else to go on but it's a solid metrics question that made me realize I hadn't thought carefully about what 'success' even means for a trust signal.
  • How would you measure whether Instagram's blue verified checkmark feature is successful?

“I started with user trust and engagement metrics and felt pretty good about it, but then realized I was basically just listing numbers without a clear north star.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round, one question the whole session. Classic array problem but the two-pointer angle is easy to miss if you're not warmed up.
  • Given an array of heights representing vertical lines, find two lines that form a container with the x-axis holding the maximum amount of water. Return that maximum volume.

“Started with brute force because I panicked a little and wanted to show I understood the problem.”

View Post