Phone Screen.
The recruiter spent a lot of time, so that seems nice. However, here is a small red flag: they pitched the role as "you can land anywhere," but then, in another call a month later, basically said, "you work in Boston or NYC, or there's not much chance of being hired." This didn't align well with me, as I want to have an impact in other areas of the company.
I completed the tech screen, which was pretty easy. Then, they ghosted me after I asked questions about finding a team to work on that wasn't the one they already had in mind.
In addition to ghosting me, the recruiter made me leave a note post-interview to get my feedback. So, they made me give feedback but wouldn't provide any. It felt very one-sided in their recruiting practices.
The interviewer was good, human, and personable at the end, while remaining professional throughout the evaluation.
There is no team matching; it's a charade. If you're like me, not Ivy League or in the top 5%, you'll likely be pegged for a given role, probably a team they're having difficulty staffing.
Count indices in a 2D array (LC easy).
Write an algorithm to calculate runtime given a stack trace as input (LC medium).
The following metrics were computed from 1,861 interview experiences for the Meta Software Engineer role in United States.
Meta's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Meta's Software Engineer interview process in United States.