I recently completed a full interview sequence with Facebook and thought it would be useful to recap it all for the next candidates coming down the pipeline. The way your interviewing experience starts is with a technical phone screen which lasts for about an hour. If you pass that you'll be invited out to Menlo Park. My interviewing day started at 9:45 a.m. and officially finished at 2 p.m. (but I didn't actually leave until closer to 3 p.m.). The recruiters are very upfront about what happens in the interview -- the initial "jedi" session which is a combination culture-fit and a supposed "easy" coding question, two "ninja" sessions which are in-depth coding / algorithm exercises (which I've recapped below), and one "pirate" session which is an architecture & design session. In terms of difficulty, I felt that the questions were relatively fair. They weren't as relentlessly challenging & tricky as what I've encountered at a traditional Google interview. but none of them were a particularly easy walk through the park. My own personal performance was probably negatively impacted by the stuffiness of the tiny interview room (of course adjusting the thermostat didn't seem to make a difference) and my general nerves (which are always in panic mode every time I'm doing these hard core technical screenings). On the flip side, I was really impressed with the working environment for employees, such as thoughtful touches such as all bathrooms being stocked with thoughtful & useful items (toothbrushes & paste, feminine care items, etc.), The campus is on the shores of San Francisco Bay, so depending on the weather (or the drought) you might be getting a view of water or of a marshy field. I have a feeling that commute times to campus can be frustratingly long, depending on where you live in the Bay Area. If you are able to handle whatever commute you end up having to do, the split campus *IS* a gorgeous and inspiring place. I say "split campus" because there's two different Facebook campuses on both sides of Highway 84. The older campus is on the East side, and the reason it feels like direct copy of the Downtown Disney mall in Anaheim is because it was done that way on purpose. The newer West building is a massive showpiece designed by Frank Gehry, and after my 5 hour interview party was over with, I was able to do a 10-15 minute walk around the beautiful rooftop gardens there with the recruiter. Weirdly enough, aside from a "how do you think you did?" follow-up from one of the recruiters a couple days after the interviewing day, I never heard anything back from anyone. In other words, it's been over a month and I never got the official rejection e-mail or phone call. My guess is the recruiters either lost track of me (which seems strange because they were so on top of arrangements prior to the interview) or they extended offers to one wave of candidates and let other "runner-up" candidates dangle while the first wave made decisions. That was really the only process hiccup along the way. Hopefully my experience flunking the Facebook interview will help you to prepare to pass your interviewing day. If you find any of the information in my interview review helpful, please let me know by voting "Yes" on the "Helpful?" question below (this helps to motivate me to be as detailed as possible).

Pretty standard interview process for FAANG/MANGA companies. Initial call with a recruiter, preliminary coding interview, on-site that spanned two days (because I asked) and a follow-up interview. The on-site interview consisted of 3 coding interviews, 1 behavioral, and 1 system design interview.