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 a recruiter. I interviewed at Meta
Interview
Recruiter was very friendly and accommodating. They seemed like they really cared about getting the interview scheduled. First interview was a phone call about 15-20 mins, just a get to know you and see if you're a good fit for the company. After that they schedule the other technical interviews which is about 45 mins and consists of a coding session.
I applied through a recruiter. The process took 2 weeks. I interviewed at Meta (Dublino, Dublino) in Feb 2016
Interview
First, there was a phone screen. I was asked the usual stuff about my experience and plans. The phone screen included some basic Linux and networks related questions.
The next phone interview was about coding without compilation. It was mostly about text manipulation methods.
The last phone interview was about Linux and networks.
Interview questions [1]
Question 1
Describe in detail on the kernel level how signals from terminal user reach processes.
I applied through an employee referral. The process took 3 weeks. I interviewed at Meta (Dublino, Dublino) in Aug 2016
Interview
The whole process included two phone screens and a five-interview onsite - all 45 mins.
The first phone screen was all about coding - two problems to solve on a coderpad shared document.
The second, conversely, was unix systems internal. The interviewer asked about a project from my resume and we delved into the systems part from there.
The onsite was composed by five interviews:
- Systems Design: how to design a very abstract system. The problem start very broad and generic (e.g. - design a pubsub system) and it needs to be straightened down to details during the interviews (storage & bandwidth calculation; distributed consensus and network partition tolerance; ddos and bot protection and mitigation).
- Coding: similar to the first phone screen;
- Systems: again, similar to the second phone screen - also including systems troubleshooting (e.g.: You receive a report that a system is unresponsive, what do you do?)
- Network: similar to systems design, but on network stacks knowledge (e.g.: what's the first packet that your laptop sends out when it boots?)
- Soft skills: SBI questions about your past work experience.
Overall the interview was average difficulty and fun to perform.
Interview questions [1]
Question 1
Design a system that stores and retrieves images for Facebook