FB contacted me to ask me to chat with them about their PE role.
I contacted them a few years ago and said that the interview process was too aimed at junior engineers for me. They assured me they had changed the initial tech questions, but they were about the same.
These questions would be a cakewalk for someone who just finished their BA degree, but silly for someone who is 10-15 years into their career and mostly focused on automation. There were no questions about coding, automation, writing SQL queries, or configuration management; they were all on Linux basics or networking.
They turned me down on the call for the position and suggested I spend less time automating and more time focusing on stuff far below my skill level. A complete waste of my time, and mildly insulting.
They really need a second set of much harder questions for more senior engineers.
Where is the DNS file located?
What signal do you send to a service to end it?
What type of record resolves URLs to IP records?
Under ps, what are three states a service can be in?
Of the 5-6 states you can find under ps, which two take up system memory?
If 0 is STDIN and 1 is STDOUT, what is 2?
The following metrics were computed from 2 interview experiences for the Meta Production Engineering role in Seattle, Washington.
Meta's interview process for their Production Engineering roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Meta's Production Engineering interview process in Seattle, Washington.