Onsite Interviews
There were a total of 4 interviews: 2 coding, 1 behavioral, and 1 system design.
Three interviews went well, but one coding interview went poorly. I was asked an easy-average question which I answered initially, but with some issues. Normally, when this happens, the interviewer helps you finalize the correct solution first and then asks you to code. However, my interviewer asked me to code directly, believing he misunderstood my solution and thought it was correct.
When I was about 60% of the way through coding, he and I both found the issue. He then asked me to describe the solution from the beginning again. In the end, I completed the code, but because of my initial coding attempt, I ran out of time and didn't have the opportunity to answer the second question.
I am very disappointed with how the situation unfolded. If I had been given two more minutes initially, instead of being asked to code directly, I would have solved the problem and had time to answer the second question as well.
I haven't received the result yet but am marking this as No Offer.
I can't share details because of an NDA, but the questions were easy to average in string and tree.
The following metrics were computed from 1 interview experience for the Meta Software Enginnner role in London, United Kingdom.
Meta's interview process for their Software Enginnner roles in London, the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Meta's Software Enginnner interview process in London, United Kingdom.