Meta Software Engineer Interview Questions
2254+ questions from real Meta Software Engineer interviews, reported by candidates.
Round Types
Top Topics
Questions
Meta Phone Screen
2 Questions and asked to run test cases for both 1. https://leetcode.com/problems/kth-largest-element-in-an-array/ 2. https://leetcode.com/problems/valid-palindrome-ii/ Lot of follow ups for the 1st question around time complexity
Meta Phone Screen
Just had a phone screen with META for SWE (not sure what level) in the US First question was https://leetcode.com/problems/buildings-with-an-ocean-view/description/ Second question was https://leetcode.com/problems/top-k-frequent-elements/ I solved the first question pretty easily. But...
Meta Phone Screen
Intro, 2 LC Question, 2 Behavioral Question https://leetcode.com/problems/k-closest-points-to-origin/ https://leetcode.com/problems/nested-list-weight-sum/ Some optimization question - Time complexity, Space Complexity Tips : It is a game of luck and lot of practice. 1) you need to...
Meta Phone Screen
Russian Interviewer who was not at all audible. He didn\'t even resolve this issue inspite of multiple requests & said he didn\'t have a mic or a headphone. He gave...
Meta Phone Screen
Asked these 2 questions. 1. https://leetcode.com/problems/valid-palindrome/ Follow up 1: if a specific charset needs to be matched (a,e,z) and exclude anything else. How would you do it? (Use a hashset for...
Meta phone screen
It\'s time to give back to the community. I had my phone screen today. I was asked an array variation of https://leetcode.com/problems/random-pick-index/description/ and https://leetcode.com/problems/find-median-from-data-stream/description/
Meta phone screen
Question 1: Implement a simple HashMap/Dict (note: there are different ways to implement hashmap, you can choose any) and implement the GET function which is expected to return a List<Friend...
Meta E4 Phone Screen
Question 1: https://leetcode.com/problems/find-common-characters/description/ Question 2: https://leetcode.com/problems/recover-a-tree-from-preorder-traversal/description/ I have solved the first one totally, and second question given the method and wrote the code but time is up while in middle of verification...
Facebook Phone Interview
2 questions: Q 1: 1. Daily public transportation pass costs $2. 7 days pass costs $6. Monthly (30 days) public transportation pass costs $22. given a sorted array[int] (31 > arr.length >= 0) where...
Facebook Phone Interview
Question: Given a list of intergers and a number (say total), find how many ways by adding \'+\', \'-\' or nothing can make the total number. Example: List : 1, 2, 3 Total :...
Facebook Phone Interview
I got asked these following two questions - https://leetcode.com/problems/basic-calculator-ii/ - https://leetcode.com/problems/binary-tree-vertical-order-traversal/ Hope this helps someone :) .
Facebook Phone Interview
Contributing to make this a stronger community. Please consider the same if you are benifitted from leetcode. Interviewer was friendly. Overall good expereince. Q1. Design Problem: Design ordereddict I gave simple solution...
Facebook Phone Interview
Question 1: https://leetcode.com/problems/balance-a-binary-search-tree/ Solve Question 1 but ran out of time so I didn\'t do Question 2... so prob an reject.. Good luck!
Facebook Phone Interview
Position : E4 It was a quick 45 min interview where the interviewer and I introduced eachother in 5 mins and 20 mins for both the questions. Questions 1: Variation of...
Facebook Phone Interview
Had a FB phone interview last week and these were the questions I got: 1) Variation of https://leetcode.com/problems/first-bad-version/ 2) Variation of https://leetcode.com/problems/subarray-sum-equals-k/
Meta | Phone Screen
Just had my phone screen. These are the questions asked 1. TicTacToe (Modify move to get the result).https://leetcode.com/problems/design-tic-tac-toe/description/?envType=company&envId=facebook&favoriteSlug=facebook-thirty-days 2. Minimum remove to get valid Parantheses. I could not the answer the first question...
August 1st: Headhunter invitation August 12th: Store interview (one easy, one medium-high frequency question) August 13th: Arranged in Anse September 12th: Anse (four medium-high frequency questions,
Meta Screening
Time to give back to the community. 1. Basic Calculator II (only + and *) sign. 2. Plan a round trip between 2 cities with minimum flight cost Given 2 arrays -...
Meta | Phonescreen
Remove consecutive characters similar to 1D candy crush. 1. abbba --> empty 2. abb ---> [a] 3. b ---> [b] 4. aabbba -->empty. I wrote stack solution but getting result "a" for 4th...
Meta Screening
https://leetcode.com/problems/k-closest-points-to-origin/ https://leetcode.com/problems/minimum-remove-to-make-valid-parentheses/
What Meta Looks for in Software Engineer Interviews
Meta Software Engineer interviews are calibrated against the level and scope expected of the role. Across 2254+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.
The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.
How To Use This Question Set
Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in Meta Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Meta's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.
Round-by-Round Expectations
Meta Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.
Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.
Common Interview Mistakes At This Combination
Reports tagged "no hire" at Meta Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.
Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of Meta Software Engineer interview retrospectives on LeakCode.
See All 2254 Meta Software Engineer Questions
Full question text, answer context, and frequency data for subscribers.
Get Access