← Back to Directory

Meta interview notes, page 119 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 coding round with a stateful BFS maze problem. The twist was managing key collection state alongside position, which made the standard visited-set approach fall apart pretty quickly.
  • Given a 2D maze with walls, a start, an exit, open cells, keys (a-f), and locked doors (A-F), find the minimum number of steps from start to exit. A door can only be passed if you're carrying the matching key. Return -1 if the exit is unreachable.

“My first instinct was plain BFS and I started coding it before really thinking about what 'visited' means here.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Brutal SQL gauntlet at Meta for a DS role. Four parts, all in one question, covering conversion rates, churn, cancellation CIs, and rolling window comparisons with timezone-aware logic throughout. Felt like a take-home disguised as a live session.
  • Given a schema with users (including timezone), app sessions, and orders, write SQL to compute daily conversion rate by city and platform for the last 7 days using user-local dates, where conversion rate is distinct users with at least one completed order that day divided by distinct users with at least one session that day. Days with no data should emit zeroes.
  • Flag city-platform pairs where the 7-day average conversion rate dropped by more than 30% compared to the preceding 7-day window, using user-local dates and without double-counting users across platforms.
  • Return a list of churned users as of today, defined as users who had at least one completed order in a specified historical window but zero completed orders in a more recent window, using their local timezone. Include their last order local date and days since last order.
  • For the last 14 local days, compute cancellation rate by city (cancelled orders divided by all orders) and return the top 3 cities by largest absolute increase versus the prior 14 days. Include 95% Wilson confidence intervals for each period.

“The timezone conversion part is what gets you.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta SWE coding round, one question the whole time: subarray sum equals k. Seemed straightforward at first but the negative numbers constraint is what separates the brute force people from everyone else.
  • Given an integer array and a target value k, count the number of contiguous subarrays whose elements sum to k. The array can contain negative numbers.

“My first instinct was the sliding window approach and I started explaining it before realizing negative numbers completely break that.”

View Post

Meta·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Meta, one question about cross-team overlap. Pretty standard stuff but the question has more depth than it looks on the surface.
  • Tell me about a time when your team and another team were both building similar solutions. What happened and how did it get resolved?

“I went in thinking this was just a conflict resolution question and kind of answered it that way, which was probably the wrong angle.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Did a product sense round at Meta centered on building a feature for natural disaster response. Pretty open-ended prompt with not a lot of scaffolding, which I wasn't fully prepared for.
  • How would you design a new feature to help people respond to natural disasters?

“I went straight to brainstorming features and kind of skipped the 'who are we actually building this for' step, which I regretted mid-answer.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Went through a technical phone screen at Meta for a SWE role, pretty short session focused on TypeScript experience.
  • Can you walk me through your experience with TypeScript?

“Blanked a bit on where to even start.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta coding screen, one question, two pointers. Pretty clean problem once you see the pattern but I overcomplicated my first instinct.
  • Given two strings, determine whether the second string could be the first string with some characters accidentally held down (long-pressed) on a keyboard.

“My first move was reaching for a frequency map which was completely wrong for this.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Interviewed for a Data Scientist role at Meta. One question, stats-heavy, the kind where you either have the intuition baked in or you're fumbling through it in real time.
  • How would you describe the distribution of comment counts across Facebook users? Sketch or explain the shape and justify why you chose it.

“I knew it was going to be right-skewed but I second-guessed myself on whether to say log-normal or power-law.”

View Post

Meta·Data Scientist·Onsite - Behavioral / Leadership

May 2026
Behavioral round for a Data Science role at Meta, centered on metric design under pressure. The question was pretty specific and had some teeth to it.
  • Tell me about a time you picked a simplified metric because you were short on time, and later got pushback that it wasn't rigorous enough. Walk me through why you made that call, how you handled the tradeoffs, and what you'd do differently.

“This one stung a little in hindsight.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta software engineering interview, just one coding round with two straightforward data structure operations. Nothing fancy, but it gets you thinking about edge cases fast.
  • Write two functions: one to add a record to a data store, and one to remove a record from it.

“Seemed simple at first and maybe it was.”

View Post