Candidates describe a Meta Product Analyst process of a recruiter call, a 45-60 minute SQL and product-case screen, then a multi-interview loop focused on product metrics, A/B testing, SQL and behavioral questions.
$165K
Avg. Base Comp
$230K
Avg. Total Comp
2-5 rounds
Typical Rounds
5-13 weeks
Process Length
Candidates describe the Meta Product Analyst interview as a test of structured product reasoning more than of hard SQL. Several report a recruiter conversation, then a technical screen of 45 to 60 minutes that pairs a product case with SQL, and finally a loop of roughly four to five interviews. Reports on the loop vary: one candidate described two rounds after an email screen, while others described four or five interviews.
The SQL is most often described as approachable. Candidates mention joins, left joins, aggregates, percent-of-total calculations, CTEs, a second-highest-salary query and weekly retention cohorts, usually at an easy-to-medium level. One rejected candidate attributed a SQL mistake to fatigue after a long case, so pace yourself between the case and the query.
The product cases are where candidates say the difficulty lies. Prompts are tied to Meta surfaces, including Instagram Reels, Shops, ads and followers, Facebook Groups, Marketplace, group video calling and News Feed or Threads ranking. Candidates describe being asked to define a primary metric and guardrails, explain metric trade-offs, diagnose an engagement decline, and design an A/B test with a launch decision. One candidate on a growth analytics loop was asked why Facebook Group comments were falling and was pushed to go deeper on the customer journey. Afterward, they realized they had not considered outside competitors, so cover both internal and external causes.
Candidates stress communication. One who accepted an offer said more than half of the evaluation is how you frame and organize your reasoning, and another described stating assumptions aloud on an estimation question. Reported timelines range from about five weeks to about three months, and outcomes are mixed.
Synthesized from 16 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 | |
| Last Transaction | |
| Employee Salaries | |
| 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 | |
| Instagram TV Success | |
| Session Difference | |
| Group Success | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Amateur Performance | |
| Search Ratings | |
| P-value to a Layman | |
| Flight Records | |
| Losing Users | |
| Emails Opened | |
| Average Order Value |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call or email screen that covers your background, why you want Meta, and how the process works. One candidate said recruiters shared preparation material, and another noted behavioral questions can start here, so have a short story about your current role ready.
Candidates typically describe a single session that combines a product case with SQL, often in CoderPad. Reports mention two SQL questions at easy-to-medium level, such as joins, aggregates, CTEs or retention. Cases are tied to Meta products and ask for success metrics, trade-offs and sometimes an A/B test design.
Candidates report a loop of about four or five interviews, though one described two rounds. Reports mention a dedicated SQL interview, analytics or product-sense cases, A/B-testing and estimation questions, and a behavioral conversation about culture and past projects. One candidate said the recruiter named analytical execution, reasoning, technical skills and behavioral areas.
Candidates report waiting from a few days between stages to about three weeks for a rejection. Two explicit end-to-end durations were reported: about five weeks for one candidate and about three months for another who spaced out interviews while working full time. Outcomes include offers, a declined offer and several rejections.
