What does the Meta SWE onsite loop look like for E4/E5?

Four scored 45-minute rounds: two coding rounds, one system design or product architecture round (nicknamed 'Ninja'), and one behavioral round (nicknamed 'Jedi'). A 45-minute technical phone screen comes first. The structure is the same for E4 and E5; leveling is decided largely in the design and behavioral rounds.

What do Meta's coding rounds evaluate?

Meta scores four coding signals: Problem Solving, Coding (code quality), Verification (testing your own code), and Communication. Onsite coding is fast, often two problems in 45 minutes, centered on LeetCode Medium. State your approach and complexity before coding, then test with concrete examples.

How does Meta decide E4 versus E5?

The loop structure is identical for both levels. Leveling is driven mainly by the system design round (senior scoping, tradeoffs, and drive) and the behavioral round (scope, cross-team influence, ownership). Strong candidates who fall short of the E5 bar are often down-leveled to E4 rather than rejected.

What are the most common Meta system design prompts?

Design Instagram is the most frequently reported prompt, followed by the News Feed, Messenger/real-time chat, notification fan-out, typeahead/autocomplete, and rate limiters. You are expected to drive: gather requirements, estimate scale early, then deep-dive one or two components.

All interview guides

Sources checked Aug 10, 2026

Meta

Two coding rounds at LeetCode pace, a system design round for experienced hires, and a behavioral round that reads for drive, conflict and impact. Fast, signal-dense and level-calibrated.

The Meta process

3 of 5 stages you can practise here

01
Recruiter Screen30 minchill
Warm, logistics-first conversation
motivationbackgroundlevel fit
02
Coding, Technical Phone Screen45 minrealistic
Minimal warmup, then straight into 1-2 problems in a shared editor
problem solvingcodingverification
03
Onsite 'Full Loop'
Four scored 45-min rounds: two coding, one system design or product architecture ('Ninja'), one behavioral ('Jedi').
3 rounds you can practise
Coding, Onsite45 minbrutal
The signature Meta cadence: typically two problems in 45 minutes, so you must finish problem one with clean working code in ~15-20 min to leave room for the second
problem solvingcodingverification
System Design / Product Architecture ('Ninja')45 minbrutal
Spoken design on a collaborative diagram
requirements & scopinghigh-level architecturedeep dive & data modeling
Behavioral ('Jedi')45 minrealistic
Conversational career retrospective, not a rigid script
drive & initiativeconflict & ambiguityimpact & scope
04
Team Matching
After a hire decision; conversations with teams. Can affect final level and offer conversion, not scored as a competency.
05
Hiring Committee & Offer
Committee reviews packet, confirms level (E4 vs E5, with down-leveling common), and extends offer.

Common questions

What does the Meta SWE onsite loop look like for E4/E5?: Four scored 45-minute rounds: two coding rounds, one system design or product architecture round (nicknamed 'Ninja'), and one behavioral round (nicknamed 'Jedi'). A 45-minute technical phone screen comes first. The structure is the same for E4 and E5; leveling is decided largely in the design and behavioral rounds.
What do Meta's coding rounds evaluate?: Meta scores four coding signals: Problem Solving, Coding (code quality), Verification (testing your own code), and Communication. Onsite coding is fast, often two problems in 45 minutes, centered on LeetCode Medium. State your approach and complexity before coding, then test with concrete examples.
How does Meta decide E4 versus E5?: The loop structure is identical for both levels. Leveling is driven mainly by the system design round (senior scoping, tradeoffs, and drive) and the behavioral round (scope, cross-team influence, ownership). Strong candidates who fall short of the E5 bar are often down-leveled to E4 rather than rejected.
What are the most common Meta system design prompts?: Design Instagram is the most frequently reported prompt, followed by the News Feed, Messenger/real-time chat, notification fan-out, typeahead/autocomplete, and rate limiters. You are expected to drive: gather requirements, estimate scale early, then deep-dive one or two components.

Sources

Built from what Meta publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.

companyMeta Careers, Preparing for your SWE interview at Metametacareers.com
Round list (coding, system design vs product architecture, behavioral), and the four coding competencies (Problem Solving, Coding, Verification, Communication).
datalevels.fyi, Meta interview processlevels.fyi
E4/E5 loop structure, round counts, and leveling notes.
dataTech Interview Handbook (yangshun, MIT)techinterviewhandbook.org
Coding topic/difficulty distribution and canonical problem list.
companyMeta, Company Info / operating valuesmeta.com
Meta's published company values as the behavioral reference frame.

Sources last checked August 10, 2026. Hiring loops change, so this date is the honest limit on everything above.