I applied through a recruiter. The process took 2 weeks. I interviewed at Meta in July 2012
Interview
The process was fast and challenging. Phone interview, then remote technical interview with live coding through a web code share site. After passing those rounds I was invited to onsite interview in Menlo Park. The onsite interview involved 4 different people, with a lunch break. I am in my mid 30's in age, and I must say I felt like the old guy at the club. My interviewers were all younger than me, and had a palpable air of superiority. I felt like I nailed each of the interviews, but was not extended an offer with "You struggled on one of the interviews" as the only explanation. Its hard for me shake the thought that it was more work culture than work skill that prevented me from receiving an offer. All in all, no complaints. It was a fun and challenging experience and I ended up with a better job in the long run.
20
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.