Software Engineer applicants have rated the interview process at Meta with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 82% positive. To compare, the company-average is 74.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 25 days to get hired, when considering 11 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 27 days.
Common stages of the interview process at Meta as a Software Engineer according to 11 Glassdoor interviews include:
Phone interview: 19%
One on one interview: 15%
Skills test: 15%
IQ intelligence test: 12%
Presentation: 12%
Personality test: 12%
Group panel interview: 8%
Other: 4%
Background check: 4%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 3+ months. I interviewed at Meta (San Francisco, CA) in Feb 2022
Interview
The recruiters are fantastic but the interviewers are downright unprofessional.
My first coding interviewer was stuffing his face with a donut but whatever.
I succeed to on-site/final rounds. Right from the start the behavioral interviewer is downright annoyed, rude, and clearly hating every minute where he has to be on interview duty. He made me feel small and a waste of his time, so after that interview was over I immediately emailed my recruiter politely asking to withdraw my application. I already have offers from another MAANG company, as well as great opportunities with cool fintech and gaming studios, so I wasn't going to put up with two back-to-back poor interviews.
Recruiter was sincere in apologizing over the phone and giving me a day to cool off before calling again to ask if I would reconsider and go through with a new final-round process. So I did.
This time, the first interview was technical product design. Not only is it poorly worded, but as I'm trying to grasp the overall "problem" and set up domain design so I can appropriately get into API design, the interview is rushing me through it and just wanting me to get to API without setting up my domain or asking other questions. And then - he is freaking sighing repeatedly while Im talking throughout the interview, as if what I am saying is seriously disappointing him or that he just doesn't want to be there.
I emailed my recruiter after that and, once again, pulled my application. These guys seemed overworked and stuck in an environment of toxic behavior. No thanks.
Interview questions [1]
Question 1
How would you design an API and domain objects for [problem]?
The process is straightforward and designed to help us get to know each other. It moves through a few stages at a comfortable pace, involves conversations with several team members, and focuses on making sure it's a good mutual fit.
I applied through a recruiter. I interviewed at Meta
Interview
Had an initial recuriter call and then scheduled a coding round with 2 leetcode questions. Practicing Meta-tagged leetcode questions would help prepare for this round. Interviewers expect clear communication and code.
Generic LeetCode-style questions, many tagged as Meta, so extensive preparation is required to perform well in the technical interview. The experience varies significantly - some interviewers provide hints and guidance, while others expect candidates to solve problems independently with minimal assistance.