Software Engineer applicants have rated the interview process at Meta with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 56% positive. To compare, the company-average is 56.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 27 days to get hired, when considering 2,264 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 31 days.
Common stages of the interview process at Meta as a Software Engineer according to 2,264 Glassdoor interviews include:
Phone interview: 39%
One on one interview: 24%
Skills test: 15%
Presentation: 8%
Background check: 4%
Group panel interview: 3%
Personality test: 3%
IQ intelligence test: 2%
Drug test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 6 weeks. I interviewed at Meta in May 2019
Interview
Recruiter reached out to me on LinkedIn. After a chat about my interests and experienced, we set up a phone screen.
Phone screen was as described by the recruiter. It was 45 minutes long. After being called, we jumped right into two coding questions that were on the easier side of Leetcode medium. There were 5 minutes for questions at the end.
After that, I was invited on-site and given about a month to study. The recruiter gave me a bunch of prep materials and the interviews basically went as described. The coding questions were all about Leetcode medium level, some harder than others. Like the phone interview, you do have to finish both questions optimally in 40 minutes.
My tip for preparing for the on-site is to focus on medium level questions and just get really good at solving them quickly. Time how long it takes you to solve a new problem and keep going until you get under 20 minutes consistently. Also check for any optimizations before you say you’re done.
Interview questions [1]
Question 1
Signed NDA so can’t disclose specific questions. Study Facebook tagged Leetcode questions. While not all of them were on there, they focused on similar topics.
Looking back, I'm glad I tackled the interview at Meta, even though I ultimately declined the offer. The process included a couple of technical rounds after an initial behavioral interview. I faced questions like implementing an LRU cache and traversing a binary tree. The kicker was when I realized the Kth largest element question was a twist on one I had recently practiced on PracHub. Overall, it was a solid experience with a fair level of difficulty, and I learned a lot along the way.
The process is straightforward and designed to help us get to know each other. It moves through a few stages at a comfortable pace, involves conversations with several team members, and focuses on making sure it's a good mutual fit.
I applied through a recruiter. I interviewed at Meta
Interview
Had an initial recuriter call and then scheduled a coding round with 2 leetcode questions. Practicing Meta-tagged leetcode questions would help prepare for this round. Interviewers expect clear communication and code.