I uploaded my CV to their system and was contacted by a recruiter.
In the initial phone screen, we discussed my interests and strengths, and the recruiter got back to me about a group that sounded like a good fit.
Since I was local, I did the first technical interview directly on site. It took about 45 minutes. My interviewer was not directly associated with the group I discussed with the recruiter, but he did take my background into account when asking questions.
It went pretty well, and a couple of days later, they invited me back for a full day of interviews.
The full-day interviews were mostly general coding questions and one architecture session.
Although this time I was talking directly to people from the group where I saw a fit with my background and interests, unfortunately, the interviewers did not ask any related questions. They kept strictly to what I guess were Facebook-approved coding questions. These were very low-level, and I think I only performed moderately well.
The architecture session went much better and was almost related to my background.
After the full day of interviews, it was pretty clear that this was not a good fit. They confirmed that a couple of days later, and the interview process stopped there.
I think the most difficult part wasn't the coding questions themselves, but that they were the kind of questions where you have to recall a lot from basic computer science classes. These are things you tend to forget if you've already been working for a couple of years. But then again, that wasn't necessarily unexpected.
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.