← Back to Directory

Meta interview notes, page 190 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

Jun 2026
Meta SWE coding round, one problem, bitmask stuff. Pretty clean problem once you see the trick but I wasn't sure I explained the complexity well enough in the moment.
  • Given a target string and a list of candidate strings, return the candidates whose set of distinct characters is entirely contained within the distinct character set of the target string.

“The key move is encoding each string as a bitmask over the alphabet, then checking if the candidate's bits are all present in the target's bits using bitwise AND against the complement.”

View Post

Meta·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Meta ML Engineer interview where they had me go deep on a resume project. Not a surface-level chat, they wanted to poke at every single decision I made.
  • Walk me through a project on your resume in depth, including the model architecture, dataset, training procedure, and how you evaluated the final results.

“This sounds manageable until they start pulling on every thread.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta PM interview with a metrics investigation question about Meta AI usage patterns across two different Instagram surfaces. Pretty classic product analytics framing but the dual-surface angle made it trickier than it sounds.
  • Meta AI usage in Instagram DMs is increasing, but usage via the Instagram Discover page search bar is declining at the same time. How do you investigate this?

“The two-surface setup is what makes this question interesting and also what tripped me up at first.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta product interview, focused entirely on monetization strategy for Facebook Dating. One question, pretty open-ended, but the ads vs. subscription angle made it more interesting than a generic monetization prompt.
  • How would you approach monetizing Facebook Dating, and would you lean toward advertising or a subscription model?

“I went with subscriptions first because ads felt too risky in a dating context where user trust is already fragile.”

View Post

Meta·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Meta for a SWE role, just the one question about influencing teammates. Pretty standard stuff but it's the kind of question that trips you up if you haven't thought through a real example beforehand.
  • Tell me about a time you had to persuade your teammates to go along with something you proposed.

“I had an example ready but it felt thin halfway through telling it.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta coding screen, pretty much what you'd expect. One algorithm question and they wanted the optimal solution, not just something that works.
  • Given an array of integers and a target value, return the indices of the two numbers that sum to the target.

“Classic problem but I still fumbled the explanation a bit.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Meta for a video conferencing product, focused on metrics definition. One question, pretty scoped, but it pushed me to think harder about what 'success' actually means for a comms product versus something like a feed.
  • You're a PM at Meta launching a new video conferencing product. How would you define success metrics for it?

“I went straight to engagement metrics and kind of forgot to set up the problem first.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
A Meta DS interview that was basically one giant experiment design question about an account switcher feature. Dense, multi-part, and the kind of thing where you realize halfway through that you've been answering the wrong sub-question for five minutes.
  • You're proposing a feature that pins accounts with unread notifications to the top of the account switcher for users who own multiple accounts. Walk through how you'd design an A/B test for this, including the unit of randomization and how you'd prevent contamination across accounts belonging to the same person.
  • What would you choose as the single primary success metric (OEC) for this experiment, and what 3 to 5 secondary or diagnostic metrics would you track alongside it? For each, define the exact numerator, denominator, and attribution window.
  • What guardrails would you set for this experiment, and at what thresholds would you pause or stop the test?
  • How would you handle users who gain or lose accounts during the experiment window, and how would you address novelty effects in your analysis?
  • Walk through your power analysis for this experiment. What are your baseline assumptions, MDE, variance reduction approach, and how long would you need to run this to hit 80% power at alpha 0.05?
  • How would you define 'visit', 'dwell time', and 'unread resolved' for logging purposes, and how would you handle cross-device attribution when users switch between web and mobile?
  • The test shows a +40% lift in switch CTR to pinned accounts, but dwell time on the switched-to account is under 5 seconds, there's no significant lift in reply rate or unread resolution, and bounce-back to the previous account within 10 seconds is up 3%. Is this a success? What do you do next?

“This is where I lost some time.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a security analyst role at Meta, just one question from what I can tell. Pretty open-ended and scenario-based, the kind of thing that sounds straightforward but really depends on how structured your thinking is under pressure.
  • You're in the middle of a security incident and you don't know how to remediate it. Walk me through how you'd figure out what to do.

“I fumbled the opener a bit because I started listing tools before I even talked about scoping the incident.”

View Post

Meta·Software Engineer·Onsite - Product Sense / Strategy

Jun 2026
Meta PM interview, one question about Newsfeed product decisions. Pretty focused case, no behavioral fluff, just straight into a product tradeoff.
  • You're the PM for Facebook Newsfeed. How would you decide between auto-playing videos versus requiring a click to play?

“I went straight to user impact and kind of forgot to anchor on what Meta actually cares about, which is engagement and time spent.”

View Post