Meta Product Analyst candidates commonly report a recruiter conversation, a timed product-and-SQL screen, and a multi-interview final loop focused on metrics, experimentation, analytical reasoning, and behavioral communication.
$170K
Avg. Base Comp
$240K
Avg. Total Comp
3 rounds
Typical Rounds
5-12 weeks
Process Length
Meta Product Analyst interviews reported here repeatedly combine product judgment with practical analytics. Candidates describe a recruiter conversation followed by a roughly 45- to 60-minute technical screen that pairs SQL with an open-ended product case. In those cases, interviewers asked candidates to define success for Meta products, investigate engagement changes, or assess a potential feature. The useful habit is to start with the product goal and users, then name a primary metric, relevant guardrails, and the analysis needed to interpret a movement.
SQL is usually part of the same evaluation as product thinking, not a separate exercise. Reported questions included joins, left joins, aggregations, percentage or ratio calculations, and a second-highest-salary query. Several candidates characterized the SQL as approachable to medium difficulty, but the timed switch from case discussion to live querying created pressure. Explain your logic and validate assumptions as you work.
Final loops varied across reports, with four or five interviews commonly described. Candidates report analytical-execution, reasoning, technical, behavioral, and product-focused conversations; some loops included dedicated SQL and analytics-case sessions. Experimentation is a recurring theme: be ready to describe an A/B test, launch criteria, trade-offs, and possible network effects or contamination. The exact sequence varies by candidate, so treat the reported format as preparation direction rather than a fixed itinerary.
Synthesized from 14 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 most memorable part of my technical round was being asked how I would measure the success of Instagram Reels, since I had practiced a very similar product-sense prompt beforehand. The discussion was relaxed, but the questions covered a broad Product Analyst toolkit. I explained which metrics I would use to evaluate Reels, then moved into a straightforward SQL exercise: writing a query to return the second-highest salary from an employees table. The final portion focused on designing an A/B test for a new News Feed ranking model, including how I would evaluate its impact.
The overall process followed a standard phone screen and then a one-hour video interview combining case-style and SQL questions. The interviewers were pleasant, and the difficulty was decently hard mainly because I had to switch between product judgment, SQL, and experimentation in a short span. A related engagement-style case involved thinking through how to increase engagements per post in Facebook Groups, so I would expect the product questions to center on Meta surfaces and engagement metrics.
I received an offer but ultimately declined it. My main advice is to practice framing success metrics for products like Reels and Facebook Groups, and be ready to connect those metrics to a clean A/B-test design for ranking changes. Also make sure basic SQL questions, including second-highest-salary patterns, feel automatic.
Prep tip from this candidate
Practice product cases about measuring or increasing engagement on Meta products, then connect your metric choices to an A/B test for a ranking-model change. Make sure you can write the second-highest-salary SQL query without spending much of the one-hour video round on it.
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 | |
| Employee Salaries | |
| Last Transaction | |
| Subscription Overlap | |
| Button AB Test | |
| Project Budget Error | |
| Decreasing Comments | |
| Impression Reach | |
| Bank Fraud Model | |
| Experiment Validity | |
| Identifying User Sessions | |
| WAU vs Open Rates | |
| Liked Pages | |
| Network Experiment Design | |
| 500 Cards | |
| Session Difference | |
| Instagram TV Success | |
| Group Success | |
| Like Tracker | |
| Random SQL Sample | |
| Amateur Performance | |
| Weighted Keys | |
| Search Ratings | |
| P-value to a Layman | |
| Flight Records | |
| Emails Opened | |
| Losing Users | |
| Largest Salary by Department |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter phone or video conversation covering their background, motivation for Meta, and what they seek in the role. Some recruiters also shared process or preparation information before the technical stage.
Candidates commonly report a timed screen combining live SQL with a product or business case. Reported work includes joins, aggregations, ratios, and product-metrics questions such as evaluating engagement, retention, or a feature decision.
Reported loops vary, but candidates describe multiple sessions across analytics cases, SQL or technical skills, analytical reasoning, behavioral discussion, and product sense. Experiment design, metric trade-offs, and clear communication recur across those accounts.
