Meta · Software engineer · E4/E5
Coding, Technical Phone Screen
Minimal warmup, then straight into 1-2 problems in a shared editor
What this round is judged on
- Problem Solving · translate an ambiguous prompt into an optimal algorithm
- Coding · clean, correct, idiomatic code
- Verification · test your own code with concrete cases
- Communication · explain approach and complexity while working
Where this round sits
Meta’s published process. Lime marks the stage this round runs.
- 01Recruiter Screen
- 02Technical Phone Screenthis round
- 03Onsite 'Full Loop'
- 04Team Matching
- 05Hiring Committee & Offer
What happens in each stage›
- Recruiter Screen
- ~30 min non-technical call: motivation, background, timeline, and level calibration (E4 vs E5).
- Technical Phone Screen
- 45 min live coding in a shared editor (CoderPad), typically 1-2 problems. Gate to the onsite.
- Onsite 'Full Loop'
- Four scored 45-min rounds: two coding, one system design or product architecture ('Ninja'), one behavioral ('Jedi').
- Team Matching
- After a hire decision; conversations with teams. Can affect final level and offer conversion, not scored as a competency.
- Hiring Committee & Offer
- Committee reviews packet, confirms level (E4 vs E5, with down-leveling common), and extends offer.
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.
Round list (coding, system design vs product architecture, behavioral), and the four coding competencies (Problem Solving, Coding, Verification, Communication).
E4/E5 loop structure, round counts, and leveling notes.
Coding topic/difficulty distribution and canonical problem list.
Meta's published company values as the behavioral reference frame.
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
Other Meta rounds
- Recruiter Screen
Warm, logistics-first conversation
- Coding, Onsite
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
- System Design / Product Architecture ('Ninja')
Spoken design on a collaborative diagram
- Behavioral ('Jedi')
Conversational career retrospective, not a rigid script