The process is somewhat lengthy. There was an initial phone interview, followed by a scheduled coding interview, which led to a final lengthy (5 hour) multi-interview set. The interview questions are highly technical. If you're solid on computer science fundamentals and/or enjoy solving complex, convoluted questions, you will probably do well. The questions I was given were frustrating for me, as my engineering strengths lie in larger architectural areas. I was given no questions about architecture or anything - my questions were all in the same format: "Given this input, create a function that results in this output." These kinds of questions, in my opinion, are not very useful in finding engineers that are flexible thinkers. They are really good at finding engineers that are extremely technical. All of the scenarios pitched for these interviews were the kind of situation that - if it ever did happen in real life - would be a one-time solution. As someone who has interviewed several people, I would never given this kind of question to interviewees because it tells me nothing about the way they will work on a real-world project. I don't need to now if they can write a function that muxes a string and an array of style tags into HTML, because even if they do, they will only have to do it once. That sort of problem is a short-term issue. It's way more important to know how they will approach a multi-faceted issue. All engineers can brute-force their way through a utility function, and all experienced engineers can detect and fix issues in utility functions. That's 5% of the work they do. The other 95% is focused on planning and designing. So that's my feedback. I've interviewed with Facebook twice and felt the same way both times. If you think of yourself as more of a design-oriented architect type, I don't know if this is the job for you. If they ask again, I'll decline.