1Phone screen (two problems)
One engineer, on a video call with a shared editor.
Meta's coding interviews move fast — usually two problems in one interview — so speed with correctness matters as much as the idea.
- 1 Problem 1
- 2 Approach
- 3 Code
- 4 Test
- 5 Problem 2
- 6 Approach
- 7 Code
- 8 Test
There is no score. The screen decides whether you go to the onsite.
Assessed on: Problem solving · Coding · Verification · Communication
2Onsite · Coding (classic)
One engineer.
- 1 Problem 1
- 2 Approach
- 3 Code
- 4 Test
- 5 Problem 2
- 6 Approach
- 7 Code
- 8 Test
Since October 2025 one onsite coding round is AI-enabled instead — practise it as its own round. This is the classic one.
Assessed on: Problem solving · Coding · Verification · Communication
3Onsite · AI-enabled coding
One engineer, with a shared editor, the code running, and an AI assistant beside it.
Meta introduced an AI-enabled coding round in October 2025: candidates fix a bug, build a feature and optimise it in an unfamiliar codebase, using an AI assistant — and are judged on whether they understand and verify what it writes.
- 1 The codebase
- 2 Fix the bug
- 3 Build
- 4 Optimise
Meta's real round runs in CoderPad with a file tree and a choice of models. Here the codebase is one file, and the assistant will not simply hand you the solution — reportedly neither does Meta's.
Assessed on: Problem solving · Code quality · Verification · Communication
One senior engineer.
- 1 Prompt
- 2 Requirements
- 3 High-level design
- 4 Deep dive
- 5 Scale & failure
For mid-level and above; a product-design variant is offered for some roles.
Assessed on: Requirements and scope · High-level design · Depth · Trade-offs and scale · Communication
One interviewer.
- 1 Introduction
- 2 Conflict
- 3 Impact
- 4 Ambiguity
- 5 Growth
The behavioural interview helps decide the level of the offer as well as the offer itself.
Assessed on: Ownership · Collaboration · Handling ambiguity · Learning and growth · Communication