Docs / Interview Guides / Meta (Facebook) Interview Guide

Meta Interview Guide

Meta (formerly Facebook) runs one of the fastest-paced coding interviews in the industry. Two problems in 45 minutes is the norm, which means speed of pattern recognition matters more than at most other companies.

Compensation (US, approximate)

LevelBase + Bonus + Stock
E3 (SWE)$190K – $230K
E4 (SWE)$280K – $360K
E5 (Sr. SWE)$400K – $540K
E6 (Staff)$600K+

E5 is the "terminal level" — you can stay at E5 indefinitely. E6 and above require sustained cross-team impact.

Interview Process

  1. Recruiter Pre-screen (20–30 min) — Background, motivation, resume highlights. No coding.

  2. Technical Phone Screen (45–60 min) — One or two coding problems on a shared editor (CoderPad). Topics: data structures and algorithms. Time and space complexity always asked.

  3. Onsite Loop (4–5 interviews, ~4 hours)

    • Ninja (Coding) — 2 rounds, 45 min each. Two problems per round is standard. Solve them on a whiteboard or virtual whiteboard.
    • Pirate (Design) — 1–2 rounds. System design for E5+, product/architecture design for E4. Junior engineers (E3) typically don't get a design round.
    • Jedi (Behavioral) — 1 round, 45 min. Motivation, conflict, ambiguity, growth. Less Leadership-Principle-style scripting than Amazon, more of a real conversation.

What Meta Actually Evaluates

Meta uses a calibrated rubric across four signals:

  • Coding — speed and correctness. Hitting "optimal" within 25 minutes is the bar.
  • Problem solving — can you decompose, propose multiple approaches, and pick the right one?
  • Design — for E5+, can you reason about scale, sharding, and tradeoffs?
  • Communication & culture — clear, collaborative, low-drama.

Interview Tips

  1. Don't burn time on clarifying questions. Meta's coding rounds are tight. Ask 1–2 sharp clarifying questions, then start solving. Long clarification phases hurt the round.

  2. Plan two solutions before coding. Mention the brute force, then the optimized approach, then code. Interviewers explicitly look for this.

  3. Two problems means pace matters. If you spend 30 minutes on the first problem, you've already failed the round. Practice solving medium problems in 15–20 minutes including dry runs.

  4. For E5 design, prepare 6–8 system blueprints. Meta favors product-flavored design (news feed, chat, photo upload, ads delivery) over abstract distributed-systems design.

  5. Behavioral is real evaluation. Meta has rejected strong coders for "communication issues." Practice telling 1-minute stories about conflict, ambiguity, and what you'd do differently in past projects.

Topics That Come Up Often

  • BFS / DFS — extremely common, especially on grids and trees.
  • Sliding Window & Two Pointers — almost guaranteed in at least one round.
  • Dynamic Programming — 1D and 2D, often as the second problem in a round.
  • Tree manipulation — serialize/deserialize, LCA, vertical order.
  • Design — news feed, chat, distributed cache, rate limiter.

Reference