

Updated by Meta candidates

Product Experience Analyst (IC6) Interview Experience
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.
- Recruiter screen
- Phone interview
- Final round
Interview tips
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.
Questions asked
Overview
My 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.
Question types asked
Specific questions asked
Given a product problem, what metrics would you come up with, how would you measure them, and why do they matter here?
Why are those the right metrics for this specific situation?
I 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.
Get full access with a membership, or share your experience to try it free.
