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 50% positive. To compare, the company-average is 59% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 32 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 32 days.
Common stages of the interview process at Meta as a Software Engineer according to 6 Glassdoor interviews include:
Phone interview: 43%
Skills test: 29%
One on one interview: 29%
Here are the most commonly searched roles for interview reports -
The recruiter contacted me and set up a one-hour phone screen interview. It included two behavioral questions and two coding problems. Overall, the interview went well. I had difficulty with the tree problem during the interview. I'll try again next year.
I applied through a recruiter. The process took 4 weeks. I interviewed at Meta (Seattle, WA) in Jul 2024
Interview
Prior to a coding interview, they give you access to a preparation hub. It has a bunch of videos from the author of "Cracking the Coding Interview," which are extremely poorly done. They can be meandering and aren't edited well at all. They play in low-resolution with no option for higher quality, so you often can't even read the code in them. The video player itself is very buggy too, often skipping back to an earlier portion while you're watching. Not much quality control there; perhaps they should hire someone to fix it, though I guess they have little incentive to.
Had a 1 hour interview with 30 mins of standard soft questions, and 25 mins of a coding exercise. It's the standard "coding challenge" thing where if you've memorized data structures, complexity and Big O notation, or even the actual problem which is on Leetcode under "Meta," you'll likely pass. I was able to implement a solution that worked, and realized only later that I had been a little off on stating the time complexity, which likely meant I didn't pass (just my guess). Suggesting the right data structure that could have led to a faster solution also might have helped.
Ultimately, the coding challenge part of these interviews is mostly a test of if you've studied data structures and/or Leetcode problems, and remember them well enough to regurgitate during an interview. Not much to do with actually building software.
Interview questions [1]
Question 1
One of the Leetcode coding problems tagged with Meta that was further down the list in frequency.
Standard FAANG process. 1 call with recruiter. 1 coding interview with an engineer. 5 hour final interview. 2 coding interviews, 1 system design and 1 behavioral/leadership interview. all ~ 50 minutes each with break in between
Interview questions [1]
Question 1
Explain a conflict you dealt with in your team and how did you go about solving it.