Developer applicants have rated the interview process at Meta with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 38% positive. To compare, the company-average is 58% positive. This is according to Glassdoor user ratings.
Candidates applying for Developer roles take an average of 26 days to get hired, when considering 8 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 Developer according to 8 Glassdoor interviews include:
Phone interview: 38%
One on one interview: 25%
Skills test: 25%
Group panel interview: 13%
Here are the most commonly searched roles for interview reports -
Recruiter call was pretty standard, first round was 2 Meta tagged LC mediums in 45 minutes. On-site was 2 coding sessions of 2 LC mediums, a system design interview and a behavioral interview with an engineering manager.
Interview questions [1]
Question 1
How do you answer if someone asks how long a deliverable or project will take?
The entire process usually takes 3–8 weeks, depending on scheduling and the specific role. Coding interviews heavily emphasize common DSA topics such as arrays, strings, trees, graphs, BFS/DFS, heaps, hash maps, and dynamic programming. System design becomes increasingly important for E4+ positions.
Interview questions [1]
Question 1
Given an array of integers and a target value, return the indices of two numbers that add up to the target
Standard cookie cutter interview with a coding interview, a system design interview and culture interview. The coding part is basically leetcode. The system design is what you can find on many youtube videos. The culture one is more tricky as they want to see that you fit Meta's culture, not that you were doing great at your existing company. So skills like dealing with conflict without calling in managers is sought after.
Interview questions [1]
Question 1
coding: I forgot, sorry
system design: design ticketmaster
culture: talk about past project; when you disagreed with a peer; how I resolved dissagreements, etc.