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
The entire process usually takes 3–8 weeks, depending on scheduling and the specific role. Coding interviews heavily emphasize common DSA topics such as arrays, strings, trees, graphs, BFS/DFS, heaps, hash maps, and dynamic programming. System design becomes increasingly important for E4+ positions.
Interview questions [1]
Question 1
Given an array of integers and a target value, return the indices of two numbers that add up to the target
Unexpectedly, the first question in the technical round felt familiar. It was about finding a subset of strings with unique character concatenation — same problem I had worked through on PracHub a few days earlier. The interview included a recruiter screen followed by a rigorous pair of technical interviews where I tackled data structures and algorithms alongside system design concepts. After successfully answering a few more challenging DSA questions, I received an offer. The entire experience was intense but ultimately rewarding, and I happily accepted the position.
Interview questions [1]
Question 1
Given an array of strings, pick a subset whose concatenation contains no duplicate characters, and return the maximum possible length of that concatenation.
Standard cookie cutter interview with a coding interview, a system design interview and culture interview. The coding part is basically leetcode. The system design is what you can find on many youtube videos. The culture one is more tricky as they want to see that you fit Meta's culture, not that you were doing great at your existing company. So skills like dealing with conflict without calling in managers is sought after.
Interview questions [1]
Question 1
coding: I forgot, sorry
system design: design ticketmaster
culture: talk about past project; when you disagreed with a peer; how I resolved dissagreements, etc.
