I applied through a recruiter. The process took 2 weeks. I interviewed at Meta in Jul 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
Got a referral through a friend who worked at Meta, which sped up the entire process. After a casual initial chat, I went through a technical interview where I faced a DSA question about validating palindromes. The interviewer was friendly but rigorous. During prep, I had spent time with the coding challenges on PracHub, and it was funny to see a similar palindrome question pop up. Overall, I received an offer, but ultimately decided to decline it after careful consideration.
Interview questions [1]
Question 1
Given a string s, return true if it can be a palindrome after deleting at most one character (Valid Palindrome II).
Recruiter call was pretty standard, first round was 2 Meta tagged LC mediums in 45 minutes. On-site was 2 coding sessions of 2 LC mediums, a system design interview and a behavioral interview with an engineering manager.
Interview questions [1]
Question 1
How do you answer if someone asks how long a deliverable or project will take?
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