← Back to Directory

Meta interview notes, page 58 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·Machine Learning Engineer·Technical Phone Screen

May 2026
Meta ML Engineer interview with a combinatorics-style coding problem. Pretty focused session, just the one question but they pushed on edge cases and efficiency.
  • You're given a table of cards with integer values. Each round, you can pick any three cards that sum to 15. Design a strategy to maximize the number of valid rounds you can complete.

“My first instinct was greedy and it was wrong, or at least incomplete.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Meta DS interview with a meaty A/B testing case about rolling out a new payment method. The tricky part wasn't designing the experiment, it was handling the conflicting metrics at the end.
  • Design an A/B experiment to evaluate whether a new payment method should be launched nationwide. If conversion rate goes up but average order value drops, how do you reconcile those two signals and present a recommendation to the product team?

“The experiment design part I felt okay about.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta coding screen for a software engineer role, one algorithmic question on expression evaluation. Pretty focused session, no fluff.
  • Given a string representing a valid arithmetic expression with non-negative integers and the operators +, -, *, / separated by spaces, evaluate it and return the integer result. Integer division should truncate toward zero. No parentheses, but operator precedence must be respected.

“The precedence part is what trips people up.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Meta DS interview with a meaty product analytics case built around a social shopping platform. The whole thing was one long scenario about comment rates on group posts, but it had a bunch of sub-questions layered in, so it felt more like a 40-minute conversation than a single prompt.
  • What data would you look at first to diagnose why posts on a social shopping platform aren't getting comments, and how would you structure your analysis step by step?
  • Map out the user journey funnel for commenting on a post. What are the key drop-off points, and which user segments would be most meaningful to analyze?
  • Brainstorm at least ten tactics to increase the comment rate on posts, then rank them by priority and explain your reasoning.
  • Pick one of your proposed tactics and design an A/B test to measure its impact on comment rate.
  • If your experiment shows increased post impressions but no lift in comments, how do you interpret that and what do you do next?

“I started with volume stuff, like how many posts get zero comments vs at least one, then tried to break it down by post age and category.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Meta data scientist SQL round, two questions both centered on a voice calling feature. Nothing too wild conceptually but the window logic and dual-role counting tripped me up more than I expected.
  • Given a table of call events, compute the percentage of distinct callers who made at least 20 calls in the last 7 days. A caller is defined strictly by the caller_user_id column. Output the analysis date and the percentage as a double.
  • For GB daily active users on the analysis date, what percentage had at least 50 total calls (as caller plus recipient) in the last 7 days? The denominator is GB users active on the analysis date in the daily_active_users table.

“Pretty clean once you pin down the analysis date.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

May 2026
Meta ML Engineer interview with a grid-based coding problem that looked straightforward but had enough depth to keep me on my toes for a while. Two parts to implement plus complexity analysis and a discussion about recursion limits on large inputs.
  • Given an m x n character grid and a target character, implement a function that returns the size of the 4-directionally connected region containing a given cell if that cell matches the target character, and 0 otherwise.
  • Using the same grid setup, implement a function that counts all distinct 4-directionally connected regions of a given character across the entire grid.
  • Analyze the time and space complexity of your solution, and explain how you'd handle recursion depth limit issues for worst-case grid inputs.

“Pretty standard flood-fill territory but I overthought the base case.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta coding screen, got a tree problem that looked easy until I started second-guessing my traversal choice mid-interview.
  • Given a binary tree, return the values of the nodes visible from the right side, ordered top to bottom.

“I went with BFS and grabbed the last node at each level.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Meta for a software engineer role. The whole session was basically one big leaderboard problem, which sounds contained until you realize how many directions it can go.
  • Design a leaderboard system for a multiplayer game that supports a global top-10, a friends-filtered top-10, real-time score updates, and optional rank queries at scale.

“I jumped straight to Redis sorted sets which felt right, and they didn't push back on that.”

View Post

Meta·Software Engineer·Online Assessment (OA)

May 2026
Meta SWE online assessment, one big coding problem the whole time. It was a custom in-memory database design with CRUD plus lock/unlock behavior, and the edge cases were way more annoying than the core idea.
  • Design and implement an in-memory database that supports record-level CRUD operations (create, read, update, delete fields) as well as locking and unlocking records, where writes to a locked record should be rejected.

“The core structure wasn't bad, two hashmaps and you're mostly there.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta product sense interview focused on a pretty meaty News Feed redesign scenario. Three follow-up layers to the same problem, which I wasn't expecting.
  • Meta is considering splitting the News Feed into two separate feeds: one for friends and family content, and one for media and commercial content. What metrics would you use to validate whether this is a good decision?
  • What are the weaknesses or blind spots in the metrics you just proposed?
  • If you were choosing a market to launch this feature in first to minimize risk, which would you pick and why?

“This took me a minute to scope properly.”

View Post