Developer applicants have rated the interview process at Meta with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 74.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Developer roles take an average of 14 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Meta overall takes an average of 43 days.
Common stages of the interview process at Meta as a Developer according to 3 Glassdoor interviews include:
Skills test: 50%
One on one interview: 50%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Meta (Menlo Park, CA)
Interview
Had 4 loop rounds with 2 DSA, 1 behavioral and 1 HLD. Got strong hire in 3 except HLD so had to redo HLD. Cleared the redo round. But did not go to team matching due to STEM-OPT visa. The company has a policy that they don't hire on STEM. Although my result is valid for an year. This felt like a bummer.
I applied online. I interviewed at Meta (New York, NY) in Jan 2024
Interview
Interview process was rigorous but fair, emphasizing data structures, algorithms, and system design. Interviewers were professional, collaborative, and focused on problem solving, communication, and coding clarity throughout the entire experience.
I applied through a recruiter. I interviewed at Meta (Menlo Park, CA) in Jan 2026
Interview
got a dm from a meta recruiter on linkedin. process was super fast. initial recruiter screen was the usual - background and checking alignment on level (e4/e5). then a technical phone screen with two lc style coding questions, mostly mediums around arrays and strings.
the onsite was 4 rounds total. first was a coding round (traditional ds/algo stuff), then sys design where i had to design a real-time collaborative editor - really had to watch out for concurrency and scaling - they keep talking about it. third was leadership & drive, mostly situational stuff like handling conflict or project tradeoffs. the most interesting one was the new ai-assisted coding round. it's not like leetcode - you’re working in a real codebase with multiple files and an ai sidebar. had to build a feature into an existing structure and honestly, it’s tricky because you have to critique the ai output and not just blindly copy it lol. i was a bit shaky on the system design and how to actually 'collab' with the ai without looking like i was cheating, so i did a few mocks on prepfully with a meta swe. that helped a ton with my structure and how to pipeline my thoughts while the ai was generating code so i didn't just sit there idle. got the offer 2 weeks later, team seems great so far!
Interview questions [1]
Question 1
Given an array of strings, write a function to return all strings that are anagrams.