I was looking for a change, and luckily, a recruiter reached out on LinkedIn. It started with the standard recruiter screen, understanding my DevOps background, etc.
The first phone round focused on Linux troubleshooting and coding.
The next round involved more Linux and coding, along with system design and a networking round, as the team consists of network production engineers. Questions covered standard Linux troubleshooting, memory to CPU to disk I/O, and an in-depth understanding of system concepts (threads, virtual memory, MMU, signals, file systems).
There were also quite a few debugging questions, so be very prepared.
I used LeetCode and HackerRank, along with a couple of mocks on Prepfully for the PE topics and Interviewing.io for coding. The mocks did help a lot to be precisely prepared for what was coming.
It's been about a month here at Meta, and it has been a great experience so far.
Write code to create a randomized Minesweeper board on every iteration.
The following metrics were computed from 46 interview experiences for the Meta Production Engineer role in Menlo Park, California.
Meta's interview process for their Production Engineer roles in Menlo Park, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Meta's Production Engineer interview process in Menlo Park, California.