It was a typical Facebook interview with 2 phone screen rounds and then the onsite interviews. The phone interviews were both algorithm problems. The onsite rounds consisted of 2 coding, 1 system design and 2 behavioral+coding rounds. Lunch was included with an engineer and also a round with an engineering manager where I got the chance to ask as many questions about Facebook as I wanted without being evaluated. Questions in the coding round were not difficult (if you prepare well) and I was able to come up with the most efficient algorithm very quickly (later verified on the web) but - and here's the most important point - do not mess up the coding. You are expected to write perfect code, clean and bug-free. If you don't then you get axed. I didn't, so... What was disappointing is the fact that even though they say reaching the optimal solution is the most important thing and what they are evaluating is your thought process, they don't mean it. They want coders not engineers. Perfection is needed even if they tell you that it's not expected. Overall though I had a positive experience. All the people involved were very nice and smart. They did not make me feel unwelcome. I guess that's why people love working there.

The technical round hit me with a classic array manipulation problem: moving zeroes to the end without disrupting the order of non-zero elements. As I tackled it, I felt a wave of familiarity wash over me; I had just practiced a similar challenge on PracHub. The rest of the interview followed a straightforward path, with some easy behavioral questions sprinkled in. Overall, it felt very easy, but I wasn’t quite the right fit for what they needed, so I didn’t receive an offer.