← Back to Directory

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

Jun 2026
Meta data scientist technical screen, one big SQL question that took up basically the whole session. The problem was more involved than I expected and I definitely fumbled some of the edge case handling under pressure.
  • Given session-level data, compare engagement between users who exclusively used the 'social' category versus those who exclusively used the 'game' category over a fixed 28-day window. Define two mutually exclusive cohorts, exclude mixed-category users and anyone with neither category, then compute per cohort: user count, median active days, share of users active 10+ days, and average minutes per active day. Write a single SQL query handling nulls and non-positive durations.

“This one took me a while to even parse correctly.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
SQL round at Meta for a DS role, two questions back to back. The schema was straightforward but the second question tripped me up more than I expected for something that looked like a simple percentage calculation.
  • Given a users-accounts-notifications schema, write a query that buckets users by how many accounts they have: exactly 2, exactly 3, or 4 or more. Return the bucket label and the count of users in each bucket.
  • Among users who have 2 or more accounts, what percentage have at least one unread notification across any of their accounts?

“Went with a CTE to count accounts per user first, then a CASE in the outer query to assign buckets, then GROUP BY that.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Phone screen at Meta for a SWE role. The warm-up was a classic string parsing problem with some light rewording, but the edge case grilling made it feel less routine than expected.
  • Given a string, determine whether it represents a valid number. A valid number can have an optional sign, an integer or decimal portion (with at least one digit in the mantissa), and an optional exponent indicated by 'e' or 'E' followed by an optional sign and a non-empty integer.

“I went with the three-flag scan approach (tracking whether I'd seen a digit, a dot, an exponent) instead of a full state machine, which felt cleaner to code quickly.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
PM interview at Meta with a single product design question focused on small and local businesses. Pretty open-ended, which sounds easy until you're actually in it.
  • As a PM at Meta, what product or feature would you build to better serve small or local businesses?

“I went straight to ads tooling because it felt safe, but partway through I realized I was basically describing something Meta already has.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed at Meta, got a question about calculating the time between two events. Pretty standard data/analytics problem but the details matter more than you'd think.
  • How would you calculate the time elapsed between two events in a dataset?

“Seemed straightforward at first.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta data science interview with a probability/statistics question that leans on the hypergeometric distribution. One question, fairly niche, not your typical SQL or A/B testing warmup.
  • There are 1,000 employees and 10 are randomly selected each round for a perk. On average, which round would you expect to be selected for the first time?

“I knew it smelled like a hypergeometric setup but blanked on the exact expected value formula mid-explanation.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta coding round, pretty standard algorithmic problem but the stack simulation tripped me up more than I expected for something that looks straightforward on paper.
  • Given logs of function calls on a single-threaded CPU, each log containing a function id, whether it's a start or end event, and a timestamp, compute the exclusive execution time for each function (excluding time spent in nested calls).

“Knew I needed a stack pretty quickly but fumbled the off-by-one stuff with the timestamps.”

View Post

Meta·Software Engineer·Technical Phone Screen

Jun 2026
Meta SWE coding round with a sliding window problem. Pretty standard stuff but worth knowing cold if you're prepping for this kind of interview.
  • Given an integer array and an integer k, compute the average of every contiguous subarray of length k and return all the averages as an array.

“Classic sliding window setup.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Meta product sense interview, got a design question about improving the doctor search and visit flow. Pretty open-ended, which I wasn't fully prepared for.
  • How would you design a better experience for finding a doctor and managing the visit process?

“I went straight to listing features and the interviewer kind of just waited.”

View Post

Meta·Data Scientist·Technical Phone Screen

Jun 2026
Meta DS interview with a product-flavored experiment design question about feed ranking. Pretty open-ended, which I wasn't fully prepared for.
  • You have evidence that users are more socially active when engaging with posts from people they know. Would you still increase the share of posts from strangers in their feed? Walk through how you'd evaluate and make that call.

“I spent the first two minutes just restating the problem back, which felt like stalling but actually helped me get my footing.”

View Post