I applied through an employee referral. The process took 1 day. I interviewed at Meta
Interview
Phone: 3 rounds
On-site: several rounds
Culture: profession
Problems are neither hard nor tricky.
The biggest challenge is Offensive Chinese Interviewer.
If they show disregard of your question about the interview problem, don't be frustrated, keep asking what you want to know. If you give up asking, you may lose some important information that you should check with them at first. And when they are picky about your code, or when they indicate that there are bugs in your code, check it carefully, fix as much as you can. And then try to let them discuss the remaining bugs, even if you can't find any more, and no matter how dictatorial they are. Don't end up arguing with them on whether it's really a bug.
2
Other Software Engineer Interview Reviews for Meta
Took about a month altogether, which felt longer given the intensity of the process. Kicked off with a technical screening, followed by two rigorous coding interviews. The DSA question on binary tree vertical order traversal hit me hard at first, but then I recognized the prompt instantly — I had just worked through something similar on PracHub. The final round was focused on system design, and while I ended up receiving an offer, I ultimately declined it. Overall, a challenging experience that definitely sharpened my skills.
Overall, the process took a little over two weeks, which felt a bit longer than I anticipated. After a quick screening, I went through two technical rounds focusing on coding and DSA concepts. One of the questions was a classic palindrome check; mid-way through, I realized it was something I had practiced on PracHub just days earlier. The final step was a casual behavioral interview. I was relieved to get an offer shortly after, which I happily accepted.
Interview questions [1]
Question 1
Given a string, determine if it is a valid palindrome considering only alphanumeric characters and ignoring case.
I applied online. I interviewed at Meta (Menlo Park, CA)
Interview
It's honestly striaght from leetcode tagged
There are no surprises if you do tagged you would be good and do well.
System design is much harder. Would recommend using hello interview.
Interview questions [1]
Question 1
Design Twitter and consider if it was suddenly an extremely low latency env