Software Developer applicants have rated the interview process at Meta with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 74.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 14 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 43 days.
Common stages of the interview process at Meta as a Software Developer according to 3 Glassdoor interviews include:
One on one interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
Pretty standard leetcode. Data structures and algorithms. Study up on them and you should have an easy time. Medium questions throughout. Small number of interview comparatively. Good luck and no stress
I applied through an employee referral. The process took 4 weeks. I interviewed at Meta in Sep 2024
Interview
I was contacted by a recruiter following up on a referral. The first phone call was just to go over my resume at a basic level. After the initial contact, I was transferred to a coordinator to schedule the tech screen.
Tech screen is with an engineer, and comprises two DSA-style questions, roughly medium difficulty. The week after the screen, I was informed I passed and was transferred to loop scheduling.
The loop for Software Engineer (Product) comprises 2 coding interviews, 1 Product Architecture (system design), and a behavioral session, each 45 minutes long. These were frequently rescheduled due to interviewer cancellations, and several times I had to move other companies' interviews around to accommodate these changes.
Overall, most of the interviewers, including the tech screen, were professional, polite, and engaged. But one coding interviewer was disinterested from the beginning. They ignored questions I asked for clarification and were responding to oncall pages during the interview. When I explained the algorithm I wanted to write, they agreed to them, but did not seem to follow the actual code at all, even though I walked through the example multiple times. In the end, they pointed out a special case I missed, which I had explicitly asked handling about early on.
In the second question, things appeared to go smoothly, until they asked me a followup question that required in-depth knowledge of language specific implementation details. When I started to explain my thinking, I started with "I don't exactly know how this is implemented in [language], but..." They interrupted me and condescendingly told me to "look it up later".
I just don't believe I could have done well with this interviewer no matter the content of the interview.
The interview was quite straightforward, mainly focusing on role-specific questions. It covered relevant skills and experience needed for the position, giving a clear understanding of expectations. Overall, it felt well-structured and aligned with the job requirements.
Interview questions [1]
Question 1
Describe some past experiences where you used a design pattern.