# Meta Engineering Manager Interview Experience

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/experiences/meta-facebook-engineering-manager-interview-d11d0b
Source observed: 2026-11-04T23:34:28.134Z
Last checked: 2026-11-04T23:34:28.134+00:00
Indexed: 2026-11-06T17:22:58.656+00:00

---

# Meta Engineering Manager Interview Experience

We are Aced, formerly Exponent. This page contains a verified United States interview experience submitted by a Meta engineering manager candidate and associated with our **Meta Engineering Manager (EM) Interview Guide**. The guide includes an expert guide, 6 interview experiences, 98 questions, and resumes:

- [Expert guide](https://www.aced.io/guides/meta-engineering-manager-interview)
- [Interview experiences](https://www.aced.io/guides/meta-engineering-manager-interview/experiences)
- [Questions](https://www.aced.io/guides/meta-engineering-manager-interview/questions)
- [Resumes](https://www.aced.io/guides/meta-engineering-manager-interview/resumes)

## Experience details

- **Company:** Meta
- **Role:** Engineering Manager (EM)
- **Location:** United States
- **Verification:** Verified
- **Result:** Rejected
- **Submitted:** 7 months ago
- **Interview date:** 10 months ago
- **Timespan:** 1 month
- **Difficulty:** Difficult
- **Interview rounds:** 8 questions across 5 rounds

> I was really confident of getting an offer, but they told me I scored higher on the management side and failed coding and product design. What surprised me most was hearing the product design feedback was structured so the recruiter couldn't really challenge it.

## Interview process

The candidate first completed a product design screening round and then entered the full loop. The full loop included coding, another product design round, a project retrospective, and a people management round. The technical rounds were highly self-led: Meta provided a board or editor and expected the candidate to drive the discussion with limited prompting.

The candidate was told that many engineering manager candidates score higher on the technical side and lower on the management side. In this case, the result was the opposite. The candidate failed the coding round and the full-loop product design round, despite feeling that the full-loop product design answer was more comprehensive than the screening answer and leaving the interviews confident about receiving an offer.

The listed process categories are:

- Phone interview
- Technical interview
- Other
- Final round

## Interview rounds

### Phone interview — 1 question

The screening lasted **45 minutes** and used a shared board. The candidate drove a Twitter-like design end to end while the interviewer mainly asked why particular choices were made and how the system would scale.

**Question types:** [Product Design](https://www.aced.io/questions?type=product-design), [System Design](https://www.aced.io/questions?type=system-design), and [Technical](https://www.aced.io/questions?type=technical).

**Specific questions:**

1. [Design a system similar to Twitter.](https://www.aced.io/questions/2701?interview=meta-facebook-engineering-manager-interview-d11d0b)
2. Why did you make those design choices?
3. How would your system function if it had to scale to hundreds of millions or potentially a billion users?

The candidate began with clarifying questions, explained the main components and tradeoffs on the board, defended design choices when challenged, and discussed scaling to hundreds of millions or potentially a billion users.

### Technical interview (1) — 2 questions

The accessible preview identifies this as a technical interview but does not include its full question set in the source markdown.

The rendered interview content describes a **45-minute** session with a senior interviewer. Questions were mostly open-ended, with a short follow-up near the end and substantial pushback on tradeoffs. The listed question was:

- How would you improve a product you use every day for a new market?

The candidate picked a segment first, sized it, compared three options, and selected one option and its success metric.

### Technical interview (2)

The rendered content repeats the same available description: a **45-minute** session with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and substantial pushback on tradeoffs. The available question was:

- How would you improve a product you use every day for a new market?

The candidate picked a segment first, sized it, compared three options, and selected one option and its success metric.

### Other

The available description is another **45-minute** session with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and substantial pushback on tradeoffs. The available question was:

- How would you improve a product you use every day for a new market?

The candidate picked a segment first, sized it, compared three options, and selected one option and its success metric.

### Final round

The available description is a **45-minute** session with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and substantial pushback on tradeoffs. The available question was:

- How would you improve a product you use every day for a new market?

The candidate picked a segment first, sized it, compared three options, and selected one option and its success metric. The same question-and-answer pair appears repeatedly in the rendered content for this round.

## Interview tips

Practice out loud with a timer, keep a framework ready for every round, and ask the recruiter what each interviewer focuses on so you can tailor your examples.

## Company culture

The candidate described interviewers as collaborative and said they kept nudging toward the user. The team appeared to value structured thinking over polish, and interviewers left time for questions at the end.

## Practice and membership

The public preview invites candidates to [practice this loop](https://www.aced.io/questions/2701/design-system-like-youtube?interview=meta-facebook-engineering-manager-interview-d11d0b). We also provide access to more than 1.8k interview experiences through membership. [Become a member](https://www.aced.io/upgrade?src=experience) or [share your experience](https://www.aced.io/questions/contribute?src=experience). A **24-hour trial** starts once a submitted experience is approved.

## More Meta interview experiences

- **Engineering Manager (M1)** — Meta, Apr 2026. Verified; 7 rounds and 7 questions. “Not all interviewers may be able to adequately ask the right questions to go in depth, but they are absolutely looking for you to provide that depth by yourself. Your examples should not be surface level, but show you actually lived through the situation.” [Read full interview](https://www.aced.io/experiences/meta-facebook-engineering-manager-interview-916dc8?returnPath=%2Fguides%2Fmeta-engineering-manager-interview%2Fexperiences)
- **Security Engineering Manager (M1)** — Meta, Dec 2025. Verified; 3 rounds and 10 questions. “I was a little complacent because I’m already ex-Meta, and the surprising feedback was that my project retrospective was only leaning toward hire because I answered a constructive feedback question like they were asking for praise. I cleared the loop, discussed numbers and joining date, and then the offer got put on hold because of the hiring freeze.” [Read full interview](https://www.aced.io/experiences/meta-facebook-engineering-manager-interview-2febf7?returnPath=%2Fguides%2Fmeta-engineering-manager-interview%2Fexperiences)
- **Engineering Manager** — Meta, Nov 2025. 1 round and 2 questions. “Fairly solid process. Recruiter was helpful with quick turnaround. Felt a little rushed during team match” [Read full interview](https://www.aced.io/experiences/meta-facebook-staff-engineering-manager-interview-53ddd3?returnPath=%2Fguides%2Fmeta-engineering-manager-interview%2Fexperiences)

[See all 6 Meta Engineering Manager interview experiences →](https://www.aced.io/guides/meta-engineering-manager-interview/experiences)

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fmeta-facebook-engineering-manager-interview-d11d0b&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fmeta-facebook-engineering-manager-interview-d11d0b). Opening a form does not execute a tool.