Meta·Product Manager·Onsite - Product Sense / Strategy
- How would you define and measure success for Meta's AI-powered messaging features?
“This took me a second to scope properly.”
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
“This took me a second to scope properly.”
“My first instinct was just Dijkstra from A and call it a day.”
“I started with a plain dict mapping category to a list of prices and sorted on checkout.”
“I picked a product I actually use every day thinking that'd make it easier, and it sort of backfired because I spent too long in the 'I love this product' phase instead of getting to the competitive angle.”
“I spent the first minute trying to figure out why Meta would even care about volunteering, which was actually the right instinct but I didn't lean into it enough.”
“I went straight to the adoption flow and probably spent too long on search filters before they nudged me toward the actual user problem.”
“The core logic clicked pretty fast but I fumbled explaining the tie-breaking rules.”
“The scope of this thing is genuinely wild.”
“The age bucketing tripped me up first.”
“I knew it was a Bayes problem the second I heard it but still fumbled the setup.”