Candidates describe the Meta Engineering Manager interview as a mix of people-management stories, system or product design, and in some loops a coding round. Experiences range from a short phone screen to a five-round onsite.
$228K
Avg. Base Comp
$533K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidate reports for the Meta Engineering Manager role vary a lot, so prepare for a range rather than one fixed loop. One candidate who came in through a referral described a recruiter screen, a roughly 45-minute call with another engineering manager, and then five back-to-back onsite rounds that ended in an offer. Another report was a single short phone call about years of experience, tools and teams managed, which ended in a rejection citing years of experience.
The people and cross-functional round stands out. The candidate who received an offer called it the hardest, with questions about handling underperformers and keeping difficult stakeholders aligned. Another candidate was asked about conflict, a team member whose performance was slipping, and developing people over time. A third remembered being asked how many direct managers they had managed. Have specific stories and numbers ready, not general descriptions of teams you were adjacent to.
Technical expectations also appear. Reported prompts include designing a real-time commenting system, tweaking the news feed and measuring the change, a project retrospective on a hard technical project, and one LeetCode-medium-style coding problem. One candidate who did not receive an offer found the product architecture portion rushed, with about 30 to 35 minutes to reach a complete design, so practice committing to a simple end-to-end shape early. One candidate also reported being ghosted after several positive rounds, so track your own follow-ups.
Synthesized from 5 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.
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
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Decreasing Comments | |
| Find the Missing Number | |
| Find Bigrams | |
| Scrambled Tickets | |
| Get Top N Frequent Words | |
| Fill None Values | |
| Recurring Character | |
| Close Friends Story | |
| Good Grades and Favorite Colors | |
| WAU vs Open Rates | |
| Find the First Non-Repeating Character in a String | |
| Instagram TV Success | |
| Group Success | |
| Friendship Timeline | |
| One Element Removed | |
| Threaded Comments | |
| Post Composer Drop | |
| Demand Metrics | |
| Minimum Absolute Distance | |
| The Brackets Problem | |
| Amateur Performance | |
| Targeted sum | |
| Losing Users | |
| Level Of Rain Water In 2D Terrain | |
| Promoting Instagram | |
| Stories Feature Change | |
| Fill Rate Drop | |
| Increase Search Ads | |
| Nearest Common Ancestor |
Synthesized from candidate reports. Individual experiences may vary.
One candidate who received an offer described an initial recruiter conversation about their background and why they wanted Meta. It also checked whether they understood that the role means managing engineers across crafts, supporting their growth and working cross-functionally. Another candidate described a short phone call centered on years of experience, tools and teams managed. That call led to a rejection on experience level.
One candidate who received an offer described a roughly 45-minute call with another engineering manager covering people management, technical design and motivation. It was not a trick-question round, but interviewers wanted specific examples and clear leadership signals, which may set the tone for later rounds.
Candidates report design-style rounds. Prompts included a real-time commenting system with a focus on scaling and metrics, how to tweak the news feed and measure success, and a product architecture exercise. One candidate felt the 30 to 35 minutes was too short to finish even a basic design, so pacing may matter.
One onsite report included a deep dive into a technically hard project the candidate drove, covering tradeoffs and scaling decisions. The same loop had one coding round at LeetCode-medium level, such as product of array except self. Other candidates did not mention coding, so its presence may vary.
Several candidates describe a leadership-focused conversation. Reported questions covered handling underperformers, keeping difficult stakeholders aligned, conflict management and developing people over time. The candidate who received an offer called this the hardest round and credited mock interviews on these questions for helping.
