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 -
It was a slow, tedious, and not well thought out process. Everything you've heard, on both ends of the spectrum, is true about them - but they deviate towards the no bueno end of the spectrum. And they ghost you, or take so long to reject you you have found another job or moved on
Interview questions [1]
Question 1
They ask about your history and background, they do a deeper dive into your technical expertise and ensure you understand the tradeoffs between approaches, leetcode questions, etc etc
I took part in the first round of a Meta interview process before the role got filled in by someone else. The interview was domain-focused and conducted by a member of the team for which Meta was hiring. They didn't ask Leet Code, but to parse some CSV in Python and extract the right data; then they asked about system-level debugging, also relevant to the role. They were friendly and easy to talk to.
Interview questions [1]
Question 1
Parse CSV in Python, questions about system-level debugging.
I applied through a recruiter. I interviewed at Meta in Apr 2025
Interview
Performed phone screen interview, asked two medium difficulty LeetCodes. Then did 2 more coding interviews (2 mediums, 2 hards ), 1 behavioral, and 2 system design for the on-site (online).
Interview questions [1]
Question 1
Mix of medium/hard Leetcode problems, then commonly asked system design questions (Ticketmaster/API)