The interview process consisted of three stages:

• A phone screen with the recruiter
• A technical screen (candidate's choice of phone or on-site)
• An on-site interview

The recruiter was very professional and helpful, describing the process and the engineering culture at Facebook. They were very flexible in scheduling both the phone screen and the on-site interview.

The initial phone screen was a standard technical phone screen, with the difficulty dialed up slightly. The solutions allowed were constrained, typically requiring constant space. After I presented my solution, we discussed its complexity.

The on-site interview was very similar. The interviews were heavily computer science-focused. The questions asked relied on the knowledge of the properties of many data structures, including ones that are less often used. I can't recall any technical trivia questions being asked; all the questions surrounded a problem that required coding an implementation on the whiteboard. Parallelism and threads were also covered. I gave my answers in Python, and except for one interviewer who asked for a solution using Java, all were accommodating. There was also one design and architecture review, which was different and a lot of fun. I was asked to design a system for a current feature of Facebook. The interviewers were great to interact with.

I had a couple of offers that were expiring, and they said they would be able to provide a decision quickly. However, there was an offsite, which delayed the decision by a few days. I withdrew my candidacy when I accepted another offer. To put it in context, my other offers were expiring within 72 hours of the on-site interview, so it was a tall order, and it's to their credit that they tried.

I left very impressed. When I'm looking for a position in the future, I'll definitely check them out.