Meta software-engineer candidates report coding-led screens and loops that can add system design, behavioral discussions, and senior-level matching. Prepare to communicate tradeoffs while solving under time pressure.
$201K
Avg. Base Comp
$347K
Avg. Total Comp
4-6 rounds
Typical Rounds
4-5 weeks
Process Length
Meta Software Engineer interviews in these reports are consistently coding-heavy, but the exact loop varies by level and candidate. Several candidates describe an initial recruiter or qualification conversation followed by a technical screen; one current senior-candidate report instead begins with level matching for E6/E7 eligibility. That conversation focused on concrete “tell me when” examples, technical decisions, and leadership as an IC team lead.
For coding, candidates report one or two live problems and a need to explain their approach, edge cases, and complexity. Recent examples include finding the top N frequent URLs using counting and a priority queue, and locating a hidden 1x3 ship on an N×N grid from hit feedback. Other supplied reports mention arrays, strings, trees, graphs, linked lists, binary search trees, dynamic programming, and greedy problems. Practice narrating a simple baseline, then making the optimization and its tradeoffs explicit rather than coding silently.
Later loops may include system design and behavioral interviews. Reported design prompts include ad-click aggregation and a scalable API for a high-traffic application, with discussion of scale, data flow, and engineering tradeoffs. Behavioral conversations probe projects, teamwork, conflict, ownership, collaboration, and impact. One report also describes an AI-assisted coding round, but that should be treated as a possible variation rather than a universal stage. Senior candidates may encounter level-focused discussion before or alongside technical interviews, and the supplied evidence does not establish one fixed format or duration.
Synthesized from 58 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Meta process.
only two rounds so far: one is the level matching to decide whether I am eligible for E6/E7 position, and the second round is the coding round where they asked two leetcode medium tasks, maybe the 2nd one was easy: the ships on the map and the least number of shots to make to hit a ship.
Questions asked: For the level matching: "tell me when" stories, asked to remember the real cases. About the decision made on the technical depth, about the people management even though I am IC but a team lead.
For the coding round:
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Meta
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Comments Histogram | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Largest Salary by Department | |
| Top 3 Users | |
| Recurring Character | |
| Scrambled Tickets | |
| Liked Pages | |
| Twenty Variants | |
| Find the First Non-Repeating Character in a String | |
| Find Bigrams | |
| One Element Removed | |
| Session Difference | |
| Last Transaction | |
| Detecting ECG Tachycardia Runs | |
| Threaded Comments | |
| Friendship Timeline | |
| Size of Joins | |
| The Brackets Problem | |
| P-value to a Layman | |
| Level Of Rain Water In 2D Terrain | |
| Get Top N Frequent Words | |
| Flight Records | |
| Emails Opened |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an early recruiter or qualification discussion about background, role fit, or experience. One current E6/E7-oriented report describes a separate level-matching conversation using real examples of technical decisions and IC team leadership; this may not apply to every software-engineering candidate.
Candidates report LeetCode-style coding screens, sometimes with two questions in a short session. Examples include top-N frequency counting with a map and priority queue, hidden-ship search on a grid, LRU cache, trees, graphs, dynamic programming, heaps, and queues. Explain assumptions, complexity, edge cases, and a dry run.
Several candidates describe further coding interviews in the full loop. Depending on the report, these may emphasize fast implementation, optimization, or debugging and modifying an existing codebase. Some candidates also report AI-assisted coding; treat that as a possible variation rather than a universal stage.
Candidates who reported design rounds describe prompts such as ad-click aggregation, a scalable API, Messenger, or a scheduler. Prepare to state a workable design first, then discuss scale, data flow, APIs, storage, failure cases, and tradeoffs as the interviewer probes.
Candidates report behavioral conversations about projects, ownership, teamwork, conflict, ambiguity, and deadlines. Some describe a resume or project deep dive, while senior candidates may need examples that show technical judgment and leadership without formal people management.
