I was referred by a friend and started with a phone interview which didn't last more than 10 minutes due to some issues on the interviewer's side. I was told I had to go through a different recruitment team and that they would contact me. Two months later, the friend that referred me asked about my status, and I was again contacted by the same person as before. He seemed confused since he believed we had spoken the previous month, when it had been almost exactly two. He also believed we had gone over a practice question to prepare for a technical interview, which certainly did not happen. This call ended with me set up for a technical interview for a position I was horribly underqualified for, but I needed interview practice, so I went along with it. I then received an email with tips for Facebook technical interviews, which I thought was a great help at the time. I was told to practice with a certain collaborative code website, so I set up an account and began practicing.
When the technical interview started, I was told to open a different website, which was fine. The question wasn't too difficult in hindsight, but either I was confused or it wasn't explained properly, because it took some back and forth before I could solve the problem. I got the n^2 solution quickly enough, but the linear solution took me longer than I'd care to admit. It was a fairly simple array problem.
What part of Facebook's infrastructure interests you?
What would you like to work on?
The following metrics were computed from 1 interview experience for the Meta Software Engineering, Infrastructure Engineering role in San Francisco, California.
Meta's interview process for their Software Engineering, Infrastructure Engineering roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Meta's Software Engineering, Infrastructure Engineering interview process in San Francisco, California.