I applied through a recruiter. The process took 1 week. I interviewed at Meta (Menlo Park, CA) in Feb 2018
Interview
Contacted by a recruiter through Linkedin. The recruiter was very helpful and efficient. Great experience.
This is a phone interview. Despite of giving the two correct answers (one of them has the same complexity as the interviewer's answer), I still got a not-going-forward response. Looks like the interviewer will only ok the candidate when his or her answer is a 100% match with his. Does it sound fair?
I applied online. The process took 3 months. I interviewed at Meta (Menlo Park, CA) in Jun 2015
Interview
I applied online, and within a few weeks a recruiter followed up with me to do an initial screen. After the screening, I had a phone interview with a team lead for the performance and capacity engineering group. After that phone call, they decided to fly me out to Menlo Park for a full day of interviews.
I met with 6 people at Facebook's main campus. Each interview was about 45 minutes and had a different focus:
- Coding interview, where the goal is to come up with a solution as fast as possible (on a whiteboard).
- System design.
- Probability and statistics.
- Culture fit.
Everyone I met was very pleasant and friendly, and the recruiters were quite helpful throughout the process, almost acting as a sort of coach.
Less than a week after the on-site interview, the recruiter contacted me to tell me they would be moving forward with other candidates.
When I asked for feedback, I was told I didn't perform well enough on the coding exercise (though I did solve both problems, but perhaps I wasn't fast enough?).
Interview questions [1]
Question 1
Given a sorted set of numbers, find the first sequence of numbers that add up to a specified value.
I applied online. The process took 3 weeks. I interviewed at Meta (Menlo Park, CA) in Nov 2014
Interview
There was an initial phone call with the hiring manager to assess job fit, followed by a phone screen interview, and an all-day interview gauntlet on-site in Menlo Park. Despite things seeming like a good fit for my software and DBMS optimization skills during the phone discussions, it turned out that the group was interested in low-level hardware design issues (e.g., optimal cache-line sizing).