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.5% 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,263 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,263 Glassdoor interviews include:
Phone interview: 39%
One on one interview: 24%
Skills test: 15%
Presentation: 8%
Background check: 4%
Personality test: 3%
Group panel interview: 3%
IQ intelligence test: 2%
Drug test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Meta (San Jose, CA) in May 2019
Interview
Phone call with recruiter, phone technical screen followed by on site technical interview. Overall a fast process and recruiters were also fast in scheduling and responding. Company culture is very nice. Employees seemed happy.
Interview questions [1]
Question 1
Tech phone screen was general tech conversation of technologies worked on, projects and past work experience and telling me about the work and culture at Sage Intacct. The interviewer was very sweet and polite.
On Site:
All Questions were Leetcode HARD level questions variations, being copy pasted or typed exactly from Leetcode HackerRank by looking at screen.
1 was a tricky variation of the number of islands question from LeetCode, one was a super hard DP problem similar to coins problem of Leetcode. I mentioned to the interveiwer that although a DP solution is available, I am not comfortable with DP and hence doing the iterative version, he reacted in a very confused way as to 'why DP/what DP'. After I gave the full solution on the board, the interviewer didn't seem interested in discussing the approach or anything else. He just wanted me to write the same code from the board on HackerRank coding screen and submit it. Obviously, in the last 12-14 min, I couldn't complete this question at all.
This was followed by a system design question about online collaborative editing tool.
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.
Generic LeetCode-style questions, many tagged as Meta, so extensive preparation is required to perform well in the technical interview. The experience varies significantly - some interviewers provide hints and guidance, while others expect candidates to solve problems independently with minimal assistance.