Candidates applying for Data Science roles take an average of 60 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 32 days.
Common stages of the interview process at Meta as a Data Science according to 1 Glassdoor interviews include:
One on one interview: 33%
Presentation: 33%
Phone interview: 33%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Meta
Interview
I was told that the technical phone interview would be about 45 minutes, and would cover basic math/probabilities, product analytics, and coding. We never did any math questions though.
The interview itself was a pretty pleasant experience, and my interactions with Facebook recruiters/interviewers have been friendly and informative. I always had the impression that they wanted me to do well.
Interview questions [1]
Question 1
There was an open-ended analytics question: What is a Facebook product that you'd be interested in working on, and how would you use analytics?
And another more specific question: We've introduced this particular new feature (it was something about friend recommendations). How should we determine whether to keep it or not?
The coding question could be done in Python, SQL, or R. It was a straightforward problem that involved calculating the friend acceptance rate over time. The table consisted of events (friend request or acceptance), date, and user id's.
I applied through a recruiter. I interviewed at Meta
Interview
A recruited reached out to me and I had a call with her. This was followed by a technical screening with a data science manager. The last step was a full round of interviews onsite.
Interview questions [1]
Question 1
They asked SQL questions, probability and product analysis
I applied through a recruiter. I interviewed at Meta in May 2017
Interview
Recruiter conversation and phone screen, one phone screen via video call.
At first I was pleased because the recruiter sent a detailed preparation guide and I had a few weeks to prepare. I spent some time preparing nearly every day, making sure I was well versed in R, which was the language that I requested for the phone screen.
The recruiter emphasized that product sense was important, so I spent time thinking and reading about metrics necessary to evaluate products and how that may be applied to Facebook.
In the end, I think I would have been better off without the interview preparation guide, as it turned out to be completely misleading.
The interview contained no probability questions, even though that was mentioned as part of it, and no product sense questions. There was only one fairly straightforward data engineering type question.
The rest was simply SQL questions, even though I had requested R as the language. I was able to use R to answer the SQL question, and then for the second follow-up questions switched to SQL, but really the type of question would be best answered with SQL.
The interview guide said that if you requested R, then they would be testing dplyr/apply functions, but that wasn't really true.
The SQL question was not straightforward, but fairly challenging. I was thrown off because I was expecting a data analysis question using R, and I was a bit nervous under pressure. I was able to answer the questions, but not without stumbling a bit.
The whole process was frustrating because I write fairly complex SQL questions often as part of my job, and have never had a query I couldn't figure out. But under the pressure of the interview, I didn't perform spectacularly. I wish I had not spent time on the other parts of the interview prep and just focused on SQL, and I probably would have been more successful. So beware the prep guide may lead you astray.
Interview questions [1]
Question 1
SQL question
One basic data engineering related question