Overall, it's an AWESOME experience. My friend referred me to and a recruiter reached out to me within a week on January 18th. They initially scheduled a phone screen on January 23rd but I was told I could skip the phone screen on January 22nd. They did not tell me the reason why but I'm very sure it's because of the strong internal referral from my ex-coworker who is also my good friend. The onsite interview was scheduled for January 30th. The onsite interview was five sessions - Two coding interviews, two career discussion + coding interviews and one system design interview. The system design interview was very interesting. This is my first time doing system design interviews because they are targeting me as E4. The interviewer asked me to design a domain-specific system but I didn't have any specific experience in that field. He was cool with that and he was able to make the question general enough so that I was able to build my solution and show off my system design skills. One master tips for system design interview was to do a mock interview with your friend. The Facebook recruiter also sent out useful information on how to prepare for system design interviews, which was also super helpful. If I have to name one thing I didn't like that much was two career discussion + coding session. It was a little bit too much since the career discussion part took almost 40 minutes so I end up speaking for 80 mins non-stop which was super tiring. Honestly, I think one career discussion + coding session is enough already. There is really no point to having two there. The 5 minutes coding was also a rush that there is no time for me to walk through my code. One of the interviewers said "you don't have to explain to me" when I was doing the coding part, which was a head-scratcher. I'm an interviewer as well and the big part of the technical interview is to expect candidates to communicate well. Two coding interviews went well. The first interviewer thought I did too quick and we end up solving three questions in one interview. I don't know if he suspected that I already saw the questions (which I did not) so he had to ask two additional questions. The second interviewer asked a relatively more complex question than the first interviewer but it was just a practical question so as long as you are comfortable with algorithms and data structures, you are good. They apparently were disallowed to ask brain teasers. I also got an additional exploratory chat that I requested with a manager from WhatsApp who walked me out of the MPK 12 building. My recruiter friend touched base with me three days later (February 2nd, Friday) and told me that my overall feedback looks good (sounds intentionally vague) and we are moving to the two approval meetings on next Monday and Tuesday. I was informed that my offer is approved on Tuesday afternoon. My recruiter friend then helped me to schedule calls with different teams' manager. I got very interested in talking with a director in Instagram which I'm a super fan of. After series of phone calls, my recruiter called again and spent an hour to help me get my questions answered. The discussion was very transparent and smooth. We also talked about a lot of topics including career development, team selection, and the offer competition process because by that time I also got an offer from Google. I actually made the final decision before the final offer numbers came out. Of course, I did not tell them my final decision until offer competition was finished because I want to get more if possible. The main factors that drove me to choose Facebook were ... 1) The impact drove culture. Note that I do not think this culture would fit everyone but it should fit me very well because I am passionate about impacting and leading people around me. I'm kind of ambitious personality in terms of my career so impactful and competitive working environment is my catalyst. 2) The ultimate flexibility of team mobility. Their boot camp program ensures that you are working in a team that you are happy with (at least for mid term) and you are encouraged to switch team if you are unhappy after a certain period of time. They also have a program called HackerMonth (I might misspell) that allows you to try to work in another team for a month every year. 3) Great recruiting experience. Choosing between Google and Facebook was VERY hard and one of the factors that drove me towards Facebook was their recruiting experience. The recruiter was super engaging and extremely responsive. She even responded on Sunday night. Recruiting experience might highly depend on the specific recruiter you get, though. I'd definitely recommend engineers who are passionate to build to try Facebook. It's a unique experience that I felt so grateful to have.

Generic LeetCode-style questions, many tagged as Meta, so extensive preparation is required to perform well in the technical interview. The experience varies significantly - some interviewers provide hints and guidance, while others expect candidates to solve problems independently with minimal assistance.