# Meta Security Engineering Manager (M1) 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-2febf7
Source observed: 2026-11-04T22:59:43.662Z
Last checked: 2026-11-04T22:59:43.662+00:00
Indexed: 2026-11-06T23:32:24.36+00:00

---

# Meta Security Engineering Manager (M1) Interview Experience

We publish interview preparation resources through Aced, formerly Exponent. This entry is a verified interview experience for a **Meta Security Engineering Manager (M1)** role in the United Kingdom. It was submitted seven months ago, with an interview date listed as a year ago, a one-month timespan, and moderate difficulty.

![Meta logo](https://exponent-static.s3.amazonaws.com/company_logos/meta.png)

## Outcome and summary

- **Result:** Waiting
- **Location:** United Kingdom
- **Verification:** Verified
- **Interview date:** a year ago
- **Timespan:** 1 month
- **Difficulty:** Moderate

The candidate was already a former Meta employee and initially cleared the loop for another Meta engineering-manager role. While waiting for team matching, Meta opened an M1 security role and requested additional interviews for that position. The candidate cleared the loop, discussed numbers and a joining date, and then the offer was put on hold because of a hiring freeze.

The candidate said the project retrospective was initially only leaning toward hire because a constructive-feedback question was answered as if it were asking for praise. People management and project retrospective required the most careful mapping of examples to the intended signals.

## Interview process

The security path consisted of:

1. Recruiter screen
2. Two technical screens
3. A six-round final loop covering:
   - Security system design
   - Security depth
   - Coding
   - Career motivation
   - People management
   - Project retrospective

The candidate found the coding fairly easy and the design rounds highly framework-driven. The technical rounds were not the most difficult part; people management and project retrospective received more probing because examples needed to map cleanly to the evaluation signal.

The broad round labels were **Recruiter screen**, **Phone interview**, and **Final round**.

## Interview rounds

The experience lists 11 questions across three rounds. Some later content is available only to members.

### Recruiter screen

The recruiter call focused on fit and red flags rather than compensation. The candidate was not asked about money. The discussion centered on whether Meta matched the candidate’s preferred way of working.

**Question type:** [Behavioral](https://www.aced.io/questions?type=behavioral)

**Questions asked:**

- [Why do you want to join Meta, and what actually motivates you about it?](https://www.aced.io/questions/3243?interview=meta-facebook-engineering-manager-interview-2febf7)
- How do you work in ambiguity and with a lot of cross-team collaboration?
- What projects have you done that show transferable skills for this role?

The candidate framed the response around intrinsic motivation rather than perks or compensation, emphasizing fast-moving ambiguous environments, cross-team work, and projects demonstrating transferable management and technical judgment. The recruiter appeared to be screening for obvious red flags and cultural fit.

### Phone interview

The accessible interview text describes a 45-minute session with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and substantial pushback on tradeoffs.

Question:

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

The candidate’s approach was to select a segment first, size it, compare three options, then choose one option and define its success metric.

### Final round

The accessible interview text describes 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 same product-improvement question and approach are shown in the accessible content:

- How would you improve a product you use every day for a new market?
- Select a segment first, size it, compare three options, then choose one option and its success metric.

The page also recommends practicing aloud with a timer, keeping a framework ready for every round, and asking the recruiter what each interviewer focuses on so examples can be tailored.

## Interviewer and team observations

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

## Access and practice

We make more than 1.8k interview experiences available to members, with new experiences added weekly. The full experience can be accessed through [Become a member](https://www.aced.io/upgrade?src=experience). Candidates can also [Share your experience](https://www.aced.io/questions/contribute?src=experience); the 24-hour trial starts once a submission is approved.

You can [Practice this loop](https://www.aced.io/questions/3243/why-work-at-meta?interview=meta-facebook-engineering-manager-interview-2febf7).

## Meta Engineering Manager resources

- [Meta Engineering Manager (EM) Interview Guide](https://www.aced.io/guides/meta-engineering-manager-interview)
- [Interview experiences](https://www.aced.io/guides/meta-engineering-manager-interview/experiences) — listed as 6 experiences
- [Questions](https://www.aced.io/guides/meta-engineering-manager-interview/questions) — listed as 98 questions
- [Resumes](https://www.aced.io/guides/meta-engineering-manager-interview/resumes)
- [Back to all experiences](https://www.aced.io/guides/meta-engineering-manager-interview/experiences)

## More Meta interview experiences

- **Engineering Manager (M1), Meta — Apr 2026; verified; 7 rounds; 7 questions.** The candidate said interviewers may not always ask the right depth questions, but candidates are expected to provide depth independently and use examples showing they personally lived through the situation. [Read the full interview](https://www.aced.io/experiences/meta-facebook-engineering-manager-interview-916dc8?returnPath=%2Fguides%2Fmeta-engineering-manager-interview%2Fexperiences)
- **Engineering Manager, Meta — Jan 2026; verified; 5 rounds; 8 questions.** The candidate reported stronger management performance but failed coding and product design, and was surprised that the product-design feedback was structured in a way the recruiter could not readily challenge. The destination URL was not included in the supplied link inventory.
- **Engineering Manager, Meta — Nov 2025; 1 round; 2 questions.** The candidate described a fairly solid process, a helpful recruiter with quick turnaround, and a somewhat rushed team match. The destination URL was not included in the supplied link inventory.

[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-2febf7&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-2febf7). Opening a form does not execute a tool.