I had chosen to go onsite for the Facebook recruiting process, so I interviewed at the Menlo Park HQ office. For the first fifteen-ish minutes, their engineer asked me about my background and some interesting problems I had worked on with Android, etc.
Then, he asked me a LeetCode medium question based on trees. I'm the sort of person who likes to take the time to understand the problem better, talk about possible approaches, and agree on a solution. However, in this case, the interviewer seemed like he just wanted a solution as quickly as possible. I took about 30 minutes to code and to test the edge cases. The code was perfect, and I was figuring out edge cases along the way by testing, but the interviewer just kept interrupting me, giving me hints and edge cases. I hated that.
He then proceeded to ask me a second question – a variation of a LeetCode medium question that can be solved in linear time by using a "trick." If you try to normally solve this problem the first time, you're not going to solve it optimally or take some time to think about it (which is what happened to me). I told the interviewer the solution and started to code, but could not finish the problem.
Needless to say, the next day I got a reject.
If you're going to do a phone interview at Facebook, this is what I have noticed (and feedback from friends who went through the same):
This is not a company that cares about how intelligent you are, but how fast you can spit out code.
2 Leetcode Mediums
The following metrics were computed from 359 interview experiences for the Meta Software Engineer role in Menlo Park, California.
Meta's interview process for their Software Engineer roles in Menlo Park, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Meta's Software Engineer interview process in Menlo Park, California.