Meta Product Analyst interview typically runs 4 to 5 rounds: recruiter screen, technical screen, product sense, SQL, and final loop. Timeline is about 3 months; the process is structured but can vary by interviewer.
$142K
Avg. Base Comp
$241K
Avg. Total Comp
3-5
Typical Rounds
2-4 weeks
Process Length
We’ve seen Meta lean hard into metric diagnosis over broad ideation. Multiple candidates described questions that were tightly scoped and rooted in a specific product behavior, like “Why are comments within Facebook Groups dying?” or college-aged Instagram users. That pattern matters: the interviewers weren’t satisfied with a single explanation or a polished framework. They kept pushing for deeper customer-journey reasoning, and in one case the candidate only realized afterward that they had missed the external competitive angle entirely — Reddit, Discord, and Twitter communities were part of the story Meta seemed to want.
A recurring theme is that Meta cares about whether you can move fluidly from data to product judgment without treating them as separate exercises. One candidate noted that the SQL portion and product sense were tied to the same tables and scenario, and another said the case study kept drilling until they got stuck. The strongest experiences were the ones where candidates stayed structured while handling ambiguity, especially when interviewers introduced follow-ups like “in fact I meant...” or probed contamination in an A/B test. That tells us Meta is looking for people who can stay precise under pressure, clarify assumptions quickly, and reason about why a metric moved — not just list possible causes.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Meta process.
The interview process had three phases: a recruiter call, a technical interview, and the final interview loop.
The technical round was a mix of product sense and SQL. Going in, I expected a fairly standard SQL-heavy interview, but what surprised me was that it started with a product case study. The case revolved around a hypothetical product called Instagram Shop, where the goal was to improve customer retention. The interviewer drove the discussion by asking questions while I walked through my thinking.
I started by defining the success metric, then segmented customers, identified the key pain point for the segment I chose, and finally recommended product features to address that pain point. I felt quite confident during this part because it was structured and conversational. The only place I fell short was brainstorming feature ideas. The recruiter had suggested coming up with 7–10 recommendations, but I could only generate six before running out of ideas.
After the case study came the SQL competency check. The questions themselves were straightforward—mostly joins, aggregate functions, and basic data manipulation. I solved two problems live in CoderPad, where the queries were executed against sample data. This is where I started sweating a bit. I was mentally drained from the case study, and on one of the questions I forgot to use DISTINCT, which caused duplicate rows and an incorrect output. Looking back, it wasn't a difficult mistake, but it was one that came from fatigue rather than a lack of SQL knowledge.
Overall, I walked out feeling good about the product sense portion but less confident about the SQL section because of that avoidable error.
Questions asked: Case prompt- Increase customer retention for Instagram Shop. SQL- 2 questions. Basic aggregate and join function testing. I don't remember the exact questions. The second question was supposed to calculate a percentage of the total, something like % of customers who ordered with an offer code.
Try to be calm while doing SQL, questions are very easy, just need some focus.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Meta
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Comments Histogram | |
| Empty Neighborhoods | |
| Last Transaction | |
| Employee Salaries | |
| Button AB Test | |
| Project Budget Error | |
| Decreasing Comments | |
| Impression Reach | |
| Bank Fraud Model | |
| Identifying User Sessions | |
| Experiment Validity | |
| WAU vs Open Rates | |
| Liked Pages | |
| Network Experiment Design | |
| 500 Cards | |
| Instagram TV Success | |
| Session Difference | |
| Group Success | |
| Random SQL Sample | |
| Amateur Performance | |
| Like Tracker | |
| Search Ratings | |
| Weighted Keys | |
| P-value to a Layman | |
| Flight Records | |
| Losing Users | |
| Emails Opened | |
| Largest Salary by Department | |
| Swipe Precision |
Synthesized from candidate reports. Individual experiences may vary.
An initial phone call with a recruiter to discuss your background, current role, and motivation for Meta. In some cases this screen is fairly casual, but it can still include behavioral depth and discussion of how you measure success in your work.
A live video interview with a data scientist or product analytics interviewer that combines SQL with product case questions. Candidates reported medium-to-hard SQL questions, often involving joins, filters, group bys, or ratio calculations, followed by a product sense or product growth case tied to Meta surfaces like Instagram or Facebook Groups.
A full interview loop made up of multiple back-to-back rounds. The loop typically includes product sense and product growth analytics discussions, with interviewers probing deeply into metric diagnosis, customer journeys, A/B testing, and ambiguity in behavioral examples.