The first part was an online multiple-choice test. The questions were about Linux bash commands and basic networks, with 20 questions in 18 minutes. This time should be enough if you know something, otherwise, just guess – good luck!
One week later, I was invited to a coding video interview. The interviewer jumped directly into coding questions without asking any behavioral or CV/resume questions. Two questions were asked: one "warm-up" and one "real stuff". Both were fairly easy – just relax, but do remember to explain your thought process.
I received a reply very quickly (1 or 2 days) after the coding interview, saying I had passed it. There was a final system interview scheduled in less than one week.
The system interview was very open-ended and, for me, it was tough. The interviewer again did not ask any other questions but started with a very easy Linux bash question. Then he dug into every detail of my answer and asked OS or bash questions about that detail until I got confused. They are trying to find out how much you know about systems. The second part of this interview was about system troubleshooting, which was also very open-ended. The interviewer would give me a scenario, and I would have to find out and solve the problem.
I received a rejection very quickly.
LeetCode Easy Coding Problems
Random System Questions
The following metrics were computed from 13 interview experiences for the Meta Production Engineer role in London, United Kingdom.
Meta's interview process for their Production Engineer roles in London, the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Meta's Production Engineer interview process in London, United Kingdom.