The hiring process was quite smooth. You operate through a recruiter who acts as your aid. Mine was friendly and quick to respond to many of my questions, and kept me updated on the whole process.
The initial stage involved a brief phone meeting with the recruiter. She asked me a few straightforward questions, presumably to assess my competence, and then arranged a call with an engineer at Facebook.
On the call, we spoke for a while. The engineer explained the company culture, asked some "softball" questions about my resume, and then posed technical questions. I was asked to write code in a shared editor from my computer. These were basic CS-200 algorithms questions.
A few days later, I was invited to Facebook HQ and met with about half a dozen people, including my recruiter. She took me to lunch at the cafe, and then I proceeded through a number of interviews. Most of these involved coding questions that I had to write on a whiteboard, similar to the CS-200 algorithm style questions. One part of the interview that was enjoyable was a more architectural question, where I designed a system for serving a news feed.
A couple of days later, I received an offer over the phone from my recruiter. A full packet arrived in the mail a few days after that.
There was one coding question I had to answer that was particularly difficult. I was given a big chunk of Objective C code and asked to find the bugs in it.
It was a bit like "Where's Waldo" where there's more than one Waldo, but they don't tell you how many Waldos there really are.
I found a bunch of bugs but was nervous I didn't find them all.
The following metrics were computed from 14 interview experiences for the Meta Engineering Manager role in Menlo Park, California.
Meta's interview process for their Engineering Manager roles in Menlo Park, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Meta's Engineering Manager interview process in Menlo Park, California.