J'ai postulé via un recruteur. J'ai passé un entretien chez Meta en avr. 2021
Entretien
Contacted by Recruiter - very friendly and helpful throughout the process. Followed by product screening which last 45 minutes and was conducted by a DS manager. Spent majority of the time trying to dissect one scenario, which felt odd to me. I get that they are trying to understand how you approach/solve a problem but it's almost unfair if the question/scenario they choose to give you is complex and requires much more thought regarding ultimate objective and product context than you can build in 30-35 minutes. It would've been nice to have some variety in questions, I wasn't expecting my entire interview performance to ride on one scenario-based question.
J'ai passé un entretien chez Meta (Menlo Park, CA)
Entretien
Started with a recruiter/screening round and then moved into the full loop. The full loop had four rounds focused on analytical execution, analytical reasoning, technical skills, and behavioral. SQL was a major part of the process, along with product metrics, experiments, stats, and communication. The process was structured but still challenging because the questions were open-ended and required clear thinking, not just memorized answers.
Recruiter screening then 1 hr technical screen on sql and business case. The interviews were focused heavily on product thinking: defining clear success metrics, interpreting metric trade-offs, and designing solid experiments. The SQL portion was straightforward but expected clean logic and structured thinking. The case rounds really test how well you connect metrics to real business impact.
I got a little caught off guard because I was expecting only 25% coding but it was like 75% SQL coding (5-6 questions related to a business case) followed by a full research design of an A/B experiment. All of this was expected to be complete in 40 minutes so you need to be able to work really fast.
Questions d'entretien [1]
Question 1
One SQL problem required calculating correlation from scratch using SQL, was not expecting that.