Meta · Software engineer · E4/E5
Conversational career retrospective, not a rigid script
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
Meta’s published process. Lime marks the stage this round runs.
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.
Warm, logistics-first conversation
Minimal warmup, then straight into 1-2 problems in a shared editor
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
Spoken design on a collaborative diagram