I applied through a recruiter. The process took 4 weeks. I interviewed at Meta in Nov 2018
Interview
I had a phone interview and then a video chat coding challenge. I use CoderPad on my laptop and someone is also video chatting with me and can see what I code. It was using SQL. He first asked me, using a dataset, how I would define an "active user". After I gave my definition, he asked me to create the metric using SQL. Unfortunately for me, I gave a complicated way of defining an active user instead of just saying "someone who clicked 5 times". It's as if they ask you to run a mile, then after the mile, ask you to beat that time by running a second mile. Why not just evaluate the time you run the mile in? It made no sense to me
Interview questions [1]
Question 1
How would you define an active user using this dataset?
Conversation with recruiter in email. Technical screening round where they ask about SQL and product sense. Onsite-Loop with four rounds. They ask about SQL, Product Sense, Statistics, Behavioural questions. The difficulty is average.
The technical round kicked off with a design question about A/B testing for Facebook Reels, which I found engaging. Then, I tackled a SQL query on user comments and how to account for novelty effects in ongoing experiments. Thankfully, I had prepared with the company-specific questions on PracHub, and it made a real difference in my confidence. The entire process felt smooth, and after some behavioral questions, I received an offer that I happily accepted.
Interview questions [3]
Question 1
Design an A/B test for a Facebook Reels ranking change and describe how you would interpret the results
Total 7 rounds: first round for resume screening, second for technical screening, then for on-site virtual with 4 interviews back to back, then hiring manager round after team matching and then salary negotiation with HR
Interview questions [1]
Question 1
Meta’s evaluation rubrics focus heavily on "Product Thinking over Fancy Math". Interviewers want to see if you can operate like a product owner with an analytical mindset, navigating messy scenarios affecting billions of users