Meta Product Experience Analyst (IC6) Interview Experience
Meta · Staff · Data Analyst
The internal tooling and the data is incredible. When I was there last year, they had their own Meta AI wired into the most commonly used databases, so I could reference tables and column names and just prompt it to give me the query I needed.
Interview process
My Meta process was a little more extensive than the standard one because they were trying to figure out whether I fit a manager or IC path, and I ended up landing on the IC track at IC6. I had the usual recruiter screen first, then a combined SQL and product sense screen that was very tied to real Meta-style business problems instead of generic analytics questions. My onsite ran over two days and included stats, experimentation, behavioral, a hiring manager round, another SQL round, and a hybrid product and metrics round that felt pretty specific to how Meta thinks. The whole thing was very product-heavy, and even the SQL questions were wrapped in engagement, ads, or product measurement contexts. I got the offer, joined with a team already lined up, and still had to go through bootcamp to learn Meta’s internal tools and how they wanted analysis done.
Interview rounds · 8
- 1
Recruiter screen
BehavioralI had a pretty standard recruiter screen, maybe 15 to 20 minutes, and it mostly felt like they were just checking that I could clearly talk about my background and the kind of work I do.
Q1. Can you speak to the kind of work you do?
How they answeredI kept this pretty high level and talked through the analytics work I had been doing and whether it lined up with what they needed. It did not feel technical at all. It felt more like they wanted to confirm I could communicate clearly and make sense for the process.
- 2
Phone screen
SQLAnalyticalProduct StrategyMy first real screen was a 45 to 60 minute SQL and product sense combo, and in my case those two parts were pretty intertwined instead of being totally separate blocks.
Q1. If we're sending emails to customers, how would you think about engagement with that?
How they answeredI started with simple engagement metrics like open rate and clickthrough rate, then translated that into what I would need in the data to measure those cleanly. The interviewer clearly cared about speed, but he was collaborative and not trying to time-gate me. We spent a little longer getting to the right answer and still got through everything.
Follow-up questions- What metrics would you actually care about?
- How would that show up in the data and how would you code for it?
- 3
Final / onsite round
Statistics & ExperimentationAnalyticalConceptMy onsite was spread across two days, and one of the rounds was a stats round that was more about how I define and justify metrics than about pure AB testing.
Q1. Given a product problem, what metrics would you come up with, how would you measure them, and why do they matter here?
How they answeredI treated it as a metric design problem. I talked through what I would measure, why each metric mattered to the problem in front of me, and how I would actually track it. The point of the round felt less like math trivia and more like whether I could connect a product question to a sensible measurement plan.
Follow-up questions- Why are those the right metrics for this specific situation?
- 4
Final / onsite round
Statistics & ExperimentationAnalyticalThe experimentation round was more structured, and they were very clearly looking for whether I actually understood experiment design instead of just memorizing a checklist.
Q1. How do we determine if X is better than Y?
How they answeredI did not jump straight into an experiment. I first set the objectives, talked about what the company was trying to do, how users interacted with the product, and what success would mean. Then I laid out the hypothesis and experiment step by step. When they asked about stratified sampling, I explained splitting a sample into balanced groups so you can test multiple variants with matched test and control cells. That follow-up was there to see if I really understood it.
Follow-up questions- What are the high level objectives and goals first?
- Why did you take that approach versus another one?
- How would you think about stratified sampling here?
- 5
Final / onsite round
BehavioralCross-FunctionalThe behavioral round felt pretty in line with Meta overall, where they cared about ownership, clear communication, and especially how well I work with PMs, engineers, and other partners.
- 6
Final / onsite round
BehavioralAnalyticalCross-FunctionalMy hiring manager round was a little more dynamic than usual because he pulled in a practical question that felt like something he was actively dealing with, instead of sticking rigidly to a question bank.
Q1. Here is something I’m seeing right now. How would you think about it?
How they answeredI treated it like a practical problem-solving conversation instead of trying to hunt for some perfect canned answer. The question was not meant to be insanely hard. It was more about whether I could structure a messy situation, think about it in a sensible way, and show how I would approach it on the job.
- 7
Final / onsite round
SQLData AnalysisAnalyticalI had another SQL round onsite, and this one was still product/business grounded but a bit more applied and concrete than the first screen.
Q1. We have a dataset of advertisers, their spend patterns, and the kinds of ads they spent money on. Build an analysis table to show how much each advertiser spent across the year, maybe segmented by a dimension in the data.
How they answeredI built it as a straightforward aggregation problem. I would total spend by advertiser across the year, then break it out by one of the available dimensions in the dataset, like the kind of ads they were buying. It was very practical. You did not need internal Meta jargon, but you did need to understand that advertisers and ad spend are core to the business.
- 8
Final / onsite round
Product StrategyAnalyticalExecutionThe weirdest onsite round was a hybrid product sense round that started broad on a Meta product and then kept narrowing into scope, metrics, and target setting.
Q1. For a product like Instagram, what exactly are we analyzing, what metrics matter, and how would you think about setting a target?
How they answeredI first narrowed the scope because you cannot answer a question like that if you do not know whether it is about the whole product or one slice of it. Then I laid out primary metrics like daily active users for growth, engagement metrics like shares, reposts, or DMs, and guardrails like app crashes. The round was really about whether I could make sense of how the product functions day to day.
Follow-up questions- Are we talking about a feature, the whole platform, or a sub-screen?
- Which of your metrics are actually good or not good?
- What guardrails would you watch?
Tips from the candidate
I would spend five minutes on each major Meta product or feature and think through the user journey and the end result that product is trying to drive. For product sense and experimentation, I would not rush into frameworks just because I know the six steps by heart. I would first make sure I really understand what the company is trying to do, how users interact with the product today, and what success actually means. I would also practice live SQL enough that the anxiety part does not throw me off. And when I get to the interviewer Q&A, I would ask much deeper team questions, like what the biggest pain point is, not just what projects they are working on.
Company culture
My read on Meta is that they are extremely product-centric and they care a lot about speed, but good interviewers there will still collaborate with you if they think you are getting to the right answer. When I was around the process, they were already condensing data analyst and data scientist profiles and trying to streamline the loops, so I would expect some of the older extra rounds to get folded together unless you are interviewing at a higher level. Once you are in, the company feels very segmented, where each team owns a small piece of the kingdom, and that is why they care so much about collaboration and product judgment. The internal tooling was honestly some of the best I have seen anywhere, and that definitely shapes both the work and the way they expect you to think in interviews.