← Back to Directory

Meta interview notes, page 7 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·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview with a single open-ended product design prompt. Not much to go on from the session itself, but the question was the kind that sounds breezy until you're actually in it.
  • Design a product for art lovers.

“I went straight to a marketplace idea and kind of regretted it halfway through.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta coding screen, one algorithm question, pretty standard stuff but the simplicity of it made me second-guess myself the whole time.
  • Given a sorted array of integers, find the smallest missing element.

“Looked easy and that made me nervous.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Quick Meta ML engineer interview with a single coding-style question. Nothing wild, but it was a bit of a curveball given the role.
  • Given two words, write a function to determine whether they are sorted in lexicographic order.

“Felt weirdly simple for an ML role.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta product sense question, just the one. Short and deceptively simple on the surface but I definitely fumbled the landing.
  • How would you explain digital advertising to your grandmother?

“I went straight into an analogy about newspaper ads and lost the thread pretty fast.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta coding screen, pretty straightforward. They asked me to sort an array and explain the time complexity, which felt almost too simple but I still managed to fumble the Big O explanation a bit.
  • Sort an integer array and analyze the time and space complexity of your solution.

“Wrote the sort fine but then kind of stumbled when explaining the Big O.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Meta PM interview with a single product design question focused on education. Not much else to go on, but it was the kind of open-ended prompt that can go sideways fast if you don't anchor yourself early.
  • Design an educational product for Meta.

“Wide open prompt and I spent probably too long trying to figure out which user segment to pick before just committing to something.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Went through a product sense round at Meta, single question about grocery shopping. Pretty open-ended, which I wasn't fully prepared for.
  • How would you improve the grocery shopping experience?

“I went straight to the app and forgot to ask who we're even designing for.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed at Meta, got a coding question around array manipulation. Not much to report, pretty standard algorithmic problem.
  • Given two arrays, find the difference between them (elements present in one but not the other).

“Pretty bread-and-butter stuff.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta Research Scientist interview with a system design coding question around a priority-based ticket management system. Pretty involved for what felt like a single round, lots of back-and-forth on design tradeoffs.
  • Design a ticket management class that supports adding tickets, updating existing tickets in-place, and retrieving the next highest-priority ticket. Priority is determined by severity first, then most recent timestamp as a tiebreaker.

“I went straight to a max-heap and they seemed fine with that, but then they asked how I'd handle updates and I kind of stumbled.”

View Post

Meta·Software Engineer·Technical Phone Screen

Apr 2026
Meta SWE interview with a single technical question on hash maps. Pretty standard stuff but worth knowing cold if you're going in.
  • How do hash maps work?

“Thought I had this but midway through explaining collision resolution I started second-guessing myself on open addressing vs chaining.”

View Post