Interview process
The bar for leetcode was lower for PE rather SWE, but there was 2 rounds on SRE debugging and Linux debugging.
- Phone interview
- Technical interview
Interview rounds
4 questions across 2 roundsPhone interview
1 questionQuestion types asked
Specific questions asked
Question on reading an excel file
Technical interview
3 questionsQuestion types asked
Specific questions asked
Debugging round of a database inode issue
Interview tips
I would do only meta tagged questions if you dont feel confident in leetcode, otherwise majority of prep would be learning on Linux internals and debugging.
Company culture
Non-that many layoffs for PE compared to SWEs. There were 2 kinds of PE A) You join a team full time B) You hop between times every few months
Get full access with a membership, or share your experience to try it free.
More Meta interview experiences

“Very rigorous. Interviewers were in a rush. I believe it’s crucial to get a feel of what you should expect during the interview and what kinds of signals you need to give. So I strongly recommend scheduling mock interviews with peers or, much more preferably, actual google or Facebook employees. ”

“What caught me off guard was that one of the coding rounds was not generic LeetCode at all. It was AI coding, with things like sparse matrix times vector multiplication and k-nearest neighbor search, and they still wanted multiple questions under pressure.”