Developer applicants have rated the interview process at Meta with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 74.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Developer roles take an average of 14 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 43 days.
Common stages of the interview process at Meta as a Developer according to 3 Glassdoor interviews include:
One on one interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
2 step process - started with a phone screen. Most of time on the phone screen was taken by a programming challenge, which was done through one of those online code editors. Passed it to get an on-site interview. Your interview continues so long as you're doing well. At then end, you get a tour of the facebook campus before being showed out.
Interview questions [1]
Question 1
Can't answer due to NDA, although it's nothing unexpected. Algorithmic problems and whiteboard coding. Try to keep whiteboard coding as eat and organized as possible, and speak out load when you're writing.
I applied online. The process took 2 months. I interviewed at Meta (Palo Alto, CA) in Jul 2011
Interview
Phone screen, Excel test, phone interview, skype interviews, 30 page assignment, flew out for on-site interviews, more phone interviews, flew out again for on-site interviews.
They put me through the ringer before they hired me. But the questions were relevant and the people I met were great. This was back in their Palo Alto offices though.
Interview questions [1]
Question 1
Pre-IPO, they asked me to write a paper on the valuation of Facebook. They also asked me what I thought the greatest technological advancement was in the past 20 years.
I applied online. The process took 6 months. I interviewed at Meta (Menlo Park, CA) in Nov 2012
Interview
Had brief phone conversation with interviewer initially, who scheduled a technical interview with an engineer working at Facebook HQ.
The second technical interview was fairly relaxed, I was asked to solve two problems using collabedit.com, firstly, finding all the anagrams in an array of strings, secondly, finding the number of ways a given score could be reached for a game with 3 different ways of scoring (e.g. 3, 5 and 10 points).
After the phone interview I was offered an onsite interview in at Menlo Park (travel expenses paid for). The interview day involved 4 back to back interviews with different engineers. The questions varied in complexity and required answers to be given on a white board. Those I can remember was implementing combinations(n, k), printing a binary tree L-R, and implementing a comparator function to sort files based on a certain naming convention.
I found it difficult to make any personal connections with my interviewers, they all seemed rushed and uninterested in striking up conversation - it was not an enjoyable experience. Indeed, my first interviewer was clearly more interested in what he was working on as he arrived ~20minutes late.
Interview questions [1]
Question 1
Providing an algorithm for combinations(n, k), not because of it's complexity, just because it took my the majority of the interview to understand that this was the problem I was solving - it was not made very clear at all.