The process begins with a single phone screen, moving to a virtual onsite if inclined. The virtual onsite includes questions about how to manage your teams, how to resolve disputes among engineers, coding questions, and systems design questions.
Frustratingly, I was rejected without any details. When I pressed the recruiter for information on any functional gaps identified so I could improve, they said I failed the systems design and coding rounds. Where it gets interesting is that in both of those rounds, I completed the prompts and confirmed with my interviewers that the solution was functional and solved for edge cases. Both interviewers offered verbal confirmation to me at that time, only to fail me out later.
All in all, I was left with the impression that Meta/Facebook interviews people to try to get them to fail, giving misleading feedback, red herrings, and withholding details. This is counter to my own philosophy (as a hiring manager myself with over 300 interviews performed) where I try to ensure that the candidate succeeds, while still challenging them to demonstrate their competency. I'm actively advising my peers to avoid interviewing with Meta because of my negative experience.
Count the quantity of unique occurrences of numbers in a one-dimensional array of numbers.
Design a simple version of the Facebook news feed.
Design a system to push localized strings to the Facebook app.
The following metrics were computed from 23 interview experiences for the Meta Software Engineering Manager role in United States.
Meta's interview process for their Software Engineering Manager roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Meta's Software Engineering Manager interview process in United States.