← Back to Directory

Meta interview notes, page 91 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·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Meta for a Data Scientist role, focused on inclusiveness. Pretty standard stuff but the follow-up probes caught me off guard more than the main question did.
  • Tell me about a time you did something to make your team or workplace more inclusive. What was the situation, what did you do, and what changed as a result?

“I had a story ready but fumbled the 'measurable impact' part.”

View Post

Meta·Software Engineer·Recruiter / HR Screen

May 2026
Interviewed for a product designer role at Meta, just the one question about strengths so I'm guessing this was early in the process.
  • What are your strengths as a designer?

“Blanked a little on this.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview focused entirely on Meta Pay, covering metric definition, feature prioritization, and a metric debugging scenario. The questions were layered and interconnected, which I didn't fully appreciate until I was already mid-answer on the second part.
  • How would you define success for Meta Pay as a product?
  • If you could only ship one feature this year for Meta Pay, would you build bill splitting or a donations feature? Walk me through your reasoning.
  • Your north star metric is flat, but cost per transaction has dropped. How do you debug this?
  • What guardrail metric would make you stop scaling Meta Pay?
  • How would you detect if payment volume growth is being driven by fraud rather than real user adoption?
  • Which surface would you launch your chosen feature on first, and why?

“I started with payment volume and the interviewer just stared at me.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview with a single product design question focused on healthcare. Pretty open-ended, which sounds fun until you're actually in it.
  • Design a healthcare product for Meta.

“This is the kind of question where the blank canvas is the hard part.”

View Post

Meta·Data Scientist·Technical Phone Screen

May 2026
Had a technical screen for a Data Scientist role at Meta focused on their internal bot-detection system called DOT. The whole session was basically one meaty scenario question about how you'd approach identifying malicious duplicate content at scale.
  • You're working on a bot-detection tool that needs to catch malicious duplicated content. What models or algorithms would you consider, and what's your reasoning for each?

“I started with text hashing since it's cheap and obvious for near-exact duplicates, then moved into TF-IDF cosine similarity for fuzzier matches.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta software engineer coding round with two problems back to back. Tree traversal and then a classic array problem. Nothing too shocking but the combo kept me on my toes.
  • Given a binary tree, return the values of nodes visible from the right side, top to bottom.
  • Given an integer array, find all unique triplets that sum to zero.

“Level-order traversal, take the last node at each level.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview with a single product design question around parenting. Pretty open-ended, which sounds freeing until you're actually sitting there trying to figure out where to start.
  • Design a product for parenting.

“The scope on this one is almost too wide.”

View Post

Meta·Product Manager·Onsite - Product Sense / Strategy

May 2026
Meta PM interview focused on Instagram Stories. Just one question but it was a meaty one about goal-setting for the team. Not a lot of context shared so hard to say how it went.
  • You're the PM for Instagram Stories. How would you define and set goals for your team?

“This tripped me up more than I expected.”

View Post

Meta·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Meta for a software engineer role. The problem was building a price tracking service at scale, the kind of thing that sounds straightforward until you're 20 minutes in and realizing you've said nothing concrete about deduplication or alert fanout.
  • Design a large-scale product price tracking service where users submit product URLs, view historical price data, and get notified when prices drop below a target threshold.

“I started with URL ingestion and spent probably too long on canonicalization before the interviewer nudged me toward the crawling layer.”

View Post

Meta·Software Engineer·Technical Phone Screen

May 2026
Meta data engineer interview with a visualization-focused question that felt more like a product analytics exercise than anything I expected from a DE role. Just the one question from what was shared, but it had some depth to it.
  • Pick a streaming metric like daily active viewers or average watch duration and walk through at least two ways you'd visualize it. Explain why each visualization works for the stakeholders receiving it.

“I went with average watch duration and pitched a time-series line chart first, which felt safe.”

View Post