The whole process took about two months.
It started with a 30-minute recruiter call, then a 90-minute online assessment with four questions. I didn’t have time to finish all four, but somehow passed that round. The next step was a technical screening with a LeetCode-style question, and then the final onsite loop:
After that, they scheduled a behavioral follow-up, saying I didn’t show a strong enough signal for “Navigating Ambiguity” and “Driving Results” in the previous interview. I did the follow-up, but then got rejected. The only feedback I got was that they found a “technical gap” in my knowledge — no details at all.
Still not sure what that means. If there was a technical issue, why make me do a behavioral follow-up instead of addressing it earlier? Felt like a waste of time.
LeetCode Meta tagged questions, e.g.:
System Design was similar to designing LeetCode, but focusing more on online contests.
The following metrics were computed from 347 interview experiences for the Meta Software Engineer role in Menlo Park, California.
Meta's interview process for their Software Engineer roles in Menlo Park, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Meta's Software Engineer interview process in Menlo Park, California.