Production Engineer applicants have rated the interview process at Meta with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 44% positive. This is according to Glassdoor user ratings.
Candidates applying for Production Engineer roles take an average of 30 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 36 days.
Common stages of the interview process at Meta as a Production Engineer according to 1 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied through college or university. I interviewed at Meta (Seattle, WA) in Mar 2019
Interview
First part is a 20 question multiple-choice quiz that you have to complete in 18 minutes. The quiz covers basic linux commands, operating systems concepts, and networking. Very basic questions.
Then its a 45 min algorithm interview over phone, with coder pad. Pretty easy questions. I got goat Latin and dinosaur CSV parsing question.
The second interview is also over the phone and is an open-ended discussion with the interviewer. He/she asks questions about operating systems and debugging Linux systems. They go deeper and deeper into concepts until you don't know what is going on. Study Operating Systems fundamentals and tools to debug Linux systems (top, vmstat, dstat, sys trace, etc.).
I applied through an employee referral. The process took 4 weeks. I interviewed at Meta (Palo Alto, CA) in Sep 2019
Interview
One round coding phone screen asking about your resume, one coding problem and follow up.
One round system phone screen, which focused on basic OS concepts like memory management.
Onsite(coding, behavior, system, coding)
I applied through a recruiter. The process took 5 weeks. I interviewed at Meta (Londra, Inghilterra) in Jul 2019
Interview
3 phone interviews:
- first one was a screaning quiz in 30 minutes... questions about linux, networks, coding
- second one was a coding interview via BlueJeans and/or phone
- third one was a Linux interview via BlueJeans and/or phone
- fourth was the onsite interview where I had other 5 interviews as usual