Data Scientist applicants have rated the interview process at Meta with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 74.1% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Meta
Interview
The interview started with live coding exercises. Some technical questions were asked about statistical concepts. The next part was product development questions. Finally, it ended with questions about experimental design.
Interview questions [1]
Question 1
How would you explain a confidence interval to a non-technical audience?
I applied through a recruiter. The process took 2 months. I interviewed at Meta (Palo Alto, CA) in Nov 2017
Interview
Very similar to what others have mentioned.
-first call with recruiter, mainly going over your resume and having them explain the process. Afterwards he sent over prep material for the phone interviews and onsite interview. The material is really comprehensive and probably somewhat overkill, but if you review it all you will be prepared. The recruiter really really wants you to feel prepared as well, so use them as a resource! That was what stood out the most to me in the process, more than anywhere else they want you to feel ready.
-phone interview with shared screen coding with a data scientist. Basic sql, coding, and stats questions.
-another phone interview, very similar to the first.
-on site interview with a mix of open ended data science problems, coding questions, sql questions, behavioral questions
-follow up phone interview with only one subject that they felt they didn't ask enough about at the onsite
Interview questions [1]
Question 1
Tell me about a time when you received constructive criticism and how you handled it.
I applied through college or university. The process took 4 weeks. I interviewed at Meta in Nov 2017
Interview
The process starts with a 15 minute call with the recruiter that covers basic questions about your background and level of interest. It's nearly impossible to mess up this step. My recruiter was incredibly kind and courteous. The following interview is an ~1 hour video conference with a coding (SQL, Python, or R) question and analysis question focused on a proposed change to one of their products. This interview is conducted by a data scientist. Mine arrived late, wasn't very nice, and was kind of condescending. It seemed like they thought this was a waste of their time. I failed this interview step most likely because I don't have the requisite experience in defining KPIs. In all honesty, this position seems more like a "data analyst" position that they relabelled "scientist" in order to attract more applicants. In the analytics team, it seems like they are only performing descriptive and inferential statistics--not building predictive models. The next step would have been an on-site interview had I made it.
Interview questions [1]
Question 1
Given an event-level table of interactions between pairs of users (note that there aren't duplicates in one day for one pair of users), for each possible number of "people interacted with" find the count for that group in a given day (i.e. 10 people interacted with only one person, 20 with 2, etc.).