The interview process was fairly simple. HR is pretty quick and responsive to emails. In the beginning, I received a call from HR, which included some technical screening (Linux, networking, etc.). Following this, I was scheduled for a coding interview.
Their coding interview is not overly challenging; it focuses on performance and efficiency (please be thorough with complexity analysis). HR provides you with proper preparation material.
During my coding interview, it appeared as though my interviewer was a bit impatient when I tried talking aloud my approach while programming. At times, I also had difficulty following him. I tried my best to keep up and clarify. Overall, I thought I had done well with the coding interview because one of the questions involved "battleship," which I clarified I was only familiar with, but I still managed to get something working as a solution.
I did hear back from HR; they decided not to proceed further as they had better candidates. I believe I did stutter and feel nervous at one point, which may have made the interviewer impatient. So, my advice is to be confident, clarify, and also pray that you find a patient interviewer.
Linux internals Networking Basics (HR Screening) Standard coding interview questions
The following metrics were computed from 155 interview experiences for the Meta Production Engineer role in United States.
Meta's interview process for their Production Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Meta's Production Engineer interview process in United States.