Meta Software Engineer Interview Experiences & Questions
34 candidates share their Meta Software Engineer interviews: each round, the questions asked and the outcome. Latest: Aug 2026.
What to expect · Meta Software Engineer
Based on 34 real interviews
The Meta Software Engineer interview process
Most common round types: Coding (16), Behavioral (10), System Design (9), Technical (5), Data Structures & Algorithms (5), Project Discussion (1).
Real Meta Software Engineer interview questions
- Implement find your way through a maze
- Implement vertical order traversal of a binary tree.
- Can you walk me through your experience and the projects you've been working on?
- Is this a valid palindrome?
- Tell me about yourself.
- Construct a binary search tree from its preorder traversal.
- Tell me about a time you had conflict at work.
- Vertical level order traversal of a binary tree.
- Explain the solution for Leetcode problem 1010: Pairs of Songs With Total Durations Divisible by 60.
- Implement x to the power of n without using any built-in library.
- Design the ticket reservation part of a Ticketmaster-like system for a big drop where lots of people reserve tickets at the same time.
- Solve this maze traversal problem and use the AI tools however you normally would.
- General Fit and background
- Implement a card game with classes like car/card and player, including functionality like shuffling and assigning cards to players.
- What kind of role do you want to interview for?
- Design an online chess game.
- Tell me about a time you made a mistake.
- Design a Facebook-like comments system that supports real-time commenting at very large scale.
- Why do you want to work at Meta?
- Find a minimum element, basically a variation of the peak element problem.
- Design a file system.
- Tell me about the project you're most proud of.
- What is the project you are most proud of?
- Solve a sliding window problem based on character frequencies inside a window.
- Design Chess.com
- Tell me about a time you had conflict with another team member or your manager. What did you do?
- Tell me about a time you had a conflict with someone. How did you resolve it and what did you learn?
- Tell me about working across multiple projects and juggling priorities.
- How would you build TinyURL?
- Given a graph traversal problem, return the integer for the longest path.
- Tell me about your past experience.
- Codesignal GCA
- Solve a problem similar to Minimum Cost to Connect Sticks using a priority queue.
- Why are you looking for a new role?
- I can't remember
- Build an entire class/object with different functionalities, and optimize one of the operations with binary search.
- Make calculator string parser for just additions and multiplications
- Solve a hard graph problem that involved topological sort.
- Build a Calculator
- How do you begin your work when you receive a new task or project?
Showing 40 of 111 questions. Open any experience for every question and how the candidate answered.
All 34 Meta Software Engineer interview experiences
“The interview was a standard FAANG type of interview, where the recruiter screen talked about resume and behavioral questions, and the first coding round was a non-AI traditional leetcode question.”
“The process was pretty rigorous, mainly because the bar at E6 felt more about scope and judgement than just solving the questions. Recruiter was clear and helpful. The coding rounds went ok, but I…”
“The interview went smoothly overall. 1 round of phone screen followed by the full loop of 4 rounds packed in a day. 2 coding 1 behavior 1 system design.”
“The process was smooth, general interview skills, prepare well to discuss you solution before coding / jumping to the optimized solution”
“Meta is still leetcode heavy and medium to hard questions should be expected. Since it's leetcode style interview you can predict the out come and also prepare easily. What didn't go well - For the…”
“The interview began with a brief self-introduction, followed by two questions: Most challenging project. What do you want to work on at Meta? The discussion lasted exactly 15 minutes. The…”
“Overall, the interview process was pretty straightforward and well organized. The interviewers were friendly and gave me a good opportunity to talk through my experience and approach to problems.…”
“Overall, I felt that the interview went well. I was able to clearly explain my experiences, discuss the projects I have worked on, and connect them to why I was interested in the position. I was…”
“The Overall Interview ProcessStep 1: Online Assessment (OA): A 60-90 minute screening on platforms like Codility or HackerRank, often featuring 2 LeetCode Medium coding questions and sometimes logic…”
“There’s a new AI coding section I haven’t seen before. They still want to test my coding skill, so I first implement by myself, then use AI as a code reviewer for readability and missing test cases.”
“In the age of AI, I could feel the interviewer adding little follow-up questions just to make sure I actually understood the problem, because if you were using AI tools, there’d be a lag. Even…”
“I had done really poorly on the easy coding question, but I still got through to the next round, which was really surprising. Then in behavioral, the interviewer said, "that does not sound like a…”
“The process started with a recruiter screening testing some behavioral questions and some technical questions she read from a question bank. Then, I did a coding interview online. Finally, a 4…”
“The process was very straightforward. In both technical rounds, I was asked questions from the top 50 Meta tagged LC questions list. Behavioral was also very standard.”
“I think I was one of the first people to take Meta’s AI round, and the models I had were really bad, like ChatGPT mini. I tried asking for test cases and it would just spit out something completely…”
“It was hard. Two medium leet code in 45 minutes and you're alright. System Design needs lots of practice and quick explanations.”
“It was a pretty standard interview. Didn’t have a single behavioral and everything was based on the technical, didn’t do perfectly, but still got the offer”
“The technical rounds were generally well structured and covered both coding and system design. I performed well in most of the technical discussions, but I found the system design round more…”
“- everyone was super nice - questions were like leet code but with a twist - time complexity always asked”
“It went well it was clear on what to expect and the recruiters do prime you well from the start. They will let you know what to expect and prep required per stage. Usually there was enough time and…”
“Leetcode was doable based on the LC premium curated list, questions were similar. Culture round required thorough prep of examples for similar questions”
“My interview process started with a CodeSignal GCF online assessment that had four sections with increasing difficulty. The earlier sections were more straightforward and focused on implementation…”
“Practice leetcode fundamentals (graph, tree), practice system design fundamentals, speaking/thinking out loud, being able to explain full flow of what happens from when user/request is received to…”
“It went pretty well. The interviewers were very nice, so it was easy to talk through my behavioral stories without putting on a super professional act. Coding challenges were mostly medium leetcode…”
“Initially considered for IC6 but performed poorly in the system design so got down-leveled to IC5. For IC6 consider how your system interacts with other systems.”
“The whole process was smooth for me, prepared well from meta tagged leetcode questions and for system design hello interview was more than enough”
“The overall interview process with Meta was structured and fairly fast-paced. The interviews focused on technical problem-solving, system design, and behavioral questions, with an emphasis on…”
“It mostly went well. I was thrown off by the fact that a lot of the focus in the system design rounds was on the product and UX side, only to discover it was product architecture later and that…”
“Coding focussed with focus on leetcode style problems. The design prompts are simple and abstract like design netflix or design instagram, etc. It is upto you to drive design discussion and this…”
“The process was what was expected and they were quick in scheduling and re-scheduling as needed. All questions were ones I had seen before via LC tagged.”
“Technical questions move fast, dont trip on edge cases. 2 questions in 60 min slot, with multiple followups. Code quickly. With 10 min of intro and questions theres not much time.”
“It was an extremely smooth process, though team matching was rough. Questions didn't need to be 100% right interestingly, as one of the rounds I didn't finish.”
“Along the interview process, I think the recruiter reached out and she was very friendly. Things were smooth. I think I had multiple rounds and overall the interview process was great.”
“It was overall a smooth experience. Be prepared to wait for 2 weeks to schedule interviews due to lack of interviewers.”
More: all Meta interviews · Software Engineer interviews at every company
Frequently asked questions
How many rounds are in the Meta Software Engineer interview?
Candidates report a typical 3 rounds, usually including a recruiter screen, online assessment, phone screen, take-home assignment.
How hard is the Meta Software Engineer interview?
Candidates rate it 3.2/5 on average (medium), across 34 interviews.
How long does the Meta Software Engineer hiring process take?
About 4 weeks from first contact to decision, based on reported timelines.
What percentage of Meta Software Engineer candidates get an offer?
61% of candidates with a final result got an offer (17 of 28).
What does the Meta Software Engineer interview focus on?
The most common round types are Coding, Behavioral, System Design, Technical.