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. I interviewed at Meta
Interview
Was reached by recruiter and invited to online interview. The interview took about 90 minutes, got 2 problems to solve. The first one was easy leetcode level, the second one was medium level task about graph traversing. The interviewer was nice and helpful, gave me a few tips. I didn't write the working code to the second problem, just verbally described the solution which was probably not the most efficient one. Even though I didn't manage to solve the second problem completely I was invited on stage interview. There were 2 coding interviews, 1 system design and 1 behavioral interviews. Coding problems were easy and medium level leetcode tasks on recursion, strings manipulations and arrays. Was managed to solve 3 out of 4 coding tasks. The system design was quite abstract, I had to build a system doing some certain tasks. From my experience you need to have some experience in similar tasks and/or prepare well for system design, this interview was the hardest for me. As a result I was rejected with a feedback that I didn't pass system design and one of coding interviews. In general experience was very positive and useful. Coding tasks were easier then I expected even though I didn't solve one of them. I would also suggest to pay more attention to preparation for system/app design interview.
Interview questions [1]
Question 1
Easy/medium level leetcode questions on recursion, strings manipulation.
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.