I was submitted as an employee referral, so this may have been quicker than some other folks' experience. The first talk with a recruiter to the offer was about 10 days. The recruiting team was very on the ball.
Had one talk with a recruiter about my background, a technical phone screen (as with many companies, writing actual code over a shared-document web page), and a half day on site of in-person interviews. The interviews on site included:
Interviewers were down to earth rather than having the attitude I'd expect of some of the large "hot" companies. The two coding problems involved fairly standard (if potentially fiddly) string or graph manipulations. One required recursion (or a fairly complicated stack structure), while the other was easier iteratively. I was asked to re-implement it using recursion in the remaining time. As with pretty well everywhere, expect to also give a big-O estimate of the run time and find some failure cases (or at least explain where you're already handling it).
The design interview question was tailored to some specialized work I've done, and this particular question is probably not representative of most groups. As I understand it, everyone gets some level of design interview, and it's usually roughly some form of "how would you build this part of an app like ours for our scale."
I got my offer a few days after interviewing. Overall, a very positive experience.
The most unexpected question was the design problem; the most difficult was one of the technical questions, which was to implement a subset of regular expressions.
The following metrics were computed from 44 interview experiences for the Meta Senior Software Engineer role in Menlo Park, California.
Meta's interview process for their Senior Software Engineer roles in Menlo Park, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Meta's Senior Software Engineer interview process in Menlo Park, California.