3 ms·
These interview practices are probably in part because of the huge number of applicants trying to get into Meta, which allows them to rachet up the difficulty t
by supriyo-biswas 2y ago
These interview practices are probably in part because of the huge number of applicants trying to get into Meta, which allows them to rachet up the difficulty to the highest level.
My assumption based on some interview experience articles[1][2] is that there's an internal arms race between the recruiting and engineering at Meta where candidates are not forwarded for the interview process until they feel sufficiently prepared, often giving them months (in any other company, I feel this would be a big red flag), and interviewers expecting the equivalent of Djikstra or Knuth to join their team, regardless of what the team actually does. (I assume not everyone writes distributed system or database implementations from scratch at Meta.)
[1] https://medium.com/@rohitverma_87831/my-interview-experience-at-meta-ad7eb22dd220 https://medium.com/@rohitverma_87831/my-interview-experience...
[2] https://leetcode.com/discuss/interview-experience/5132569/Meta-E5-Infra-Engineer-or-New-York-or-YOE%3A-8-or-Reject/ https://leetcode.com/discuss/interview-experience/5132569/Me...
- blsapologist42 2y agoAs a former interviewer at Meta who did hundreds of technical interviews, I can tell you that the people that I hardly expected "Djikstra or Knuth". Honestly I gave pretty reasonable questions that were similar to the types of things I would do in my work (with some modifications to work as an interview question). And still the majority of people didn't do great. It's even worse at the "screen" stage, where I've had people that, e.g. didn't know what "function" means or couldn't write a loop to find the max number in an array.