Meta Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 3,293 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Meta.
Meta
Software Engineer
Staff Difficult Positive experience No offer 6 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding System Design Behavioral
initial call with recruiter - coding round with an interviewer - 2 leetcode mediums - loop -> 2 coding interviews -> 2 system design interviews -> 1 behaviour interview. Interviews were positive. Even when I forgot how to do KMP, the interviewer was trying to be helpful.
Confirmed questions2 questions
- LeetCode problem where I needed to use KMP.
- Heap and queue focused questions.
Meta
Software Engineer
Mid Average Negative experience No offer 1 round
Interview process
Onsite Offer
Interview formats
Technical Coding
I recently interviewed for a Software Engineer role. The technical interviewers were professional, but the recruiting process was one of the most inefficient and deceptive experiences I’ve had in the industry. 1. Misleading and "Ghost-Rejection" Emailing Style: Two days after the full loop interview, the recruiter sent an email titled "Thank You for Your Time Today!" packed with overly enthusiastic language ("huge thank you," "enthusiasm," "here for you every step of the way"). For any experienced candidate, this reads like a "soft" rejection template, yet it was used just to tell me to wait for their result. It came across as a deliberate attempt to manipulate the candidate’s expectations instead of giving a clear, professional status update. 2. Pointless Sync Call for a 30-Second Rejection: Even though they had the result ready by Friday, the recruiter insisted on setting up a formal "sync call" for the following Tuesday morning. I had to rearrange my own work schedule and reserve a private room at my current office, only for the recruiter to spend 30 seconds reading a generic rejection script. When I shared feedback that this could—and should—have been handled over email to respect everyone’s time, the recruiter doubled down, saying they wanted to "show gratitude." There is no gratitude in wasting a candidate’s productive working hours for an update that fits into two sentences. 3. The Outcome: After all this "high-touch" (really: high-friction) communication, it ended in a standard 12-month cool-off period. Advice to Management Efficiency is a core value at Meta, but it is clearly missing in the recruiting department. Stop forcing "sync calls" for rejections. It is not "personal"; it is disruptive. If you have a decision on Friday, send the email on Friday. Respect candidates’ working hours and their professional time.
Confirmed questions1 question
- Typical leetcode-style coding question, with AI tools allowed in one of the interviews.
Meta
Software Engineer
Senior Difficult Positive experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Onsite
Interview formats
Behavioral Technical Coding System Design Group
Recruiter first reached out, then I had a chat with the hiring manager, a technical screening, and after that panel interviews with more coding, plus two system design rounds. The coding questions were medium difficulty Leetcode-style. Since I’m interviewing for the reality team, the system design questions weren’t the usual fullstack/distributed systems ones. They were more focused on headsets user experience and standalone system design. Overall I had a good experience with the team, and the recruiter was especially helpful at the beginning.
Confirmed questions1 question
- How would you design a device for playing Tetris?
Meta Software Engineer Interview Questions
Quoted word for word from Meta interview reports.
“Given a node reference in a connected undirected graph, create and return a deep copy (clone) of that graph.”
Read reports →“Given an integer array nums and an integer k, find the length of the longest contiguous subarray whose elements sum up exactly to k. If there is no such subarray, return 0.”
Read reports →“Given an array of strings, implement a function that returns all the strings that are anagrams.”
Read reports →“find the min subarray where there are 2 numbers and their differenece is equal or more then k”
Read reports →“Design a rate limiter class that supports up to N requests per user per minute.”
Read report →“For a list of items on a webpage, some with large images and long text, how can we make it load faster and be more user-friendly?”
Read report →“What is the big o of the algorithm and how could you make it better”
Read report →“Hey folks, are all the APIs mentioned here coming from the Egress coral service? If yes, what usecases are the APIs under management/rpc/ actually powering?”
Read report →“How to implement a median filter without them actually calling it a median filter... seriously. They tried to be deliberately tricky by badly describing it without ever naming it.”
Read report →Formats, difficulty and experience
Across all 3,293 Meta interview reports.