← Back to Directory

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

May 2026
Meta SWE interview with a maze traversal problem. Pretty classic DFS setup but the constraint of only having two methods to work with made it more interesting than your typical graph question.
  • A mouse needs to find cheese in a maze. You're given only two methods: one to check if the current position has cheese, and one to move to an adjacent position. Design an algorithm using depth-first search to navigate the maze.

“The constraint that you can't see the full maze upfront is what makes this tricky.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE coding round, one question about custom alphabet ordering. Pretty focused session, no fluff.
  • You're given a custom alphabet ordering and an array of strings. Write a function that checks whether the array is sorted lexicographically according to that custom ordering, returning true or false.

“My first instinct was to build a lookup map from character to its rank in the custom alphabet, then compare adjacent strings pairwise.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta data engineer technical screen done in CoderPad's Python project mode. You get a README with two messy data sources and a business question, and you have to write a function that joins them, handles every documented data quality issue, and returns a summary dict. More like a mini take-home crammed into a live session.
  • Given two data sources from different upstream systems with known schema inconsistencies, missing records, and orphaned foreign keys, implement a function that joins and processes them to return a summary dictionary answering the stated business question.

“The README lays out the known issues which sounds helpful until you realize you have to handle all of them and comment on each decision.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Meta DS interview centered on a single meaty ML system design question about restaurant recommendations in a social feed. No behavioral rounds mentioned, just the one technical deep dive. Felt like they wanted to see how you'd think end-to-end rather than just spit out model names.
  • Design a recommendation system that surfaces relevant local restaurant pages to users in their news feed (organic, not ads). Walk through your data sources, feature choices, model architecture, real-time ranking, and how you'd evaluate the system offline and online.

“This is a big question and I underestimated how far they'd want me to go.”

View Post

Meta·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Did a product design interview at Meta and got asked about advocacy within the design process. Pretty short but it made me think harder than I expected.
  • Tell me about a feature you pushed to keep in a product and why you believed in it.

“This one tripped me up a bit.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE interview with a pretty meaty coding/design hybrid question around a payment tracking system. One question but it had a lot of layers and I felt like I was peeling an onion the whole time.
  • Design and implement a function that returns the top N accounts by total outgoing payments, combining both immediate and scheduled payments. The function should support efficient online updates after every payment, and you should explain tie-breaking behavior, complexity, and how account deletions or merges would affect the ranking.

“I got the basic heap idea out pretty fast but then they kept pulling on threads.”

View Post

Meta·Software Engineer·Onsite - Coding / Algorithms

May 2026
Meta SWE coding round with at least two algorithm problems, both requiring time and space complexity discussion. Not much detail shared beyond that.
  • Solve a coding problem (likely a LeetCode-style algorithm question) and analyze its time and space complexity.

“The original post references this as the second coding question and doesn't give much away about what it actually was.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

May 2026
Meta system design round, one question about building a jobs product from scratch. Sparse on details but it's the kind of open-ended thing that can go a lot of directions depending on what the interviewer wants to dig into.
  • Design a jobs marketplace feature for Facebook, covering how users post, discover, and apply for jobs on the platform.

“This one sprawls fast.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta product sense interview, one question about designing something for Covid-19. Pretty open-ended and I wasn't totally sure where they wanted me to go with it.
  • Design a Facebook product to help address the Covid-19 pandemic.

“I jumped straight into features and the interviewer kind of just stared at me for a second.”

View Post

Meta·Software Engineer·Online Assessment (OA)

May 2026
Straightforward Meta SWE coding question, basically just string concatenation with a space. Not much to say about the experience itself since the problem was pretty minimal.
  • Write a function that takes two name strings and returns them combined into a single full name string.

“Yeah this is just first_name + ' ' + last_name.”

View Post