Meta — Coding Screen: Pattern, Syllabus & Mock Test
Meta — Coding Screen pattern: 4 questions in 70 minutes across 1 section. Sample questions, a preparation guide and a free timed mock.
- Pattern: Meta
- Duration: 70 minutes
- Questions: 4
- Timing: Free — move between sections until the paper's clock ends
- Negative marking: None
Four problems in seventy minutes. Most candidates do not finish, and that is expected.
- Pure coding
- Seventeen minutes a problem
- Most do not finish
Sections
| Section | Questions | Time | Kind | Marks each |
|---|---|---|---|---|
| Coding | 4 | 70 min | Coding | 10 |
Meta — Coding Screen syllabus
Coding: Meta coding questions 223 problems
Instructions
Meta's screen is the tightest clock here: four problems in seventy minutes, about seventeen minutes each.
- Speed is the test. Not finishing is normal; getting three clean is a strong result.
- Do not polish. Get a correct solution down, then move.
- One shared clock, so triage the four by difficulty before you start.
Meta also runs a different format in which a single large problem unlocks in four stages, and its real assessment is video and microphone monitored throughout. This paper models the four-discrete-problem variant, which is the one that can be reproduced.
How to prepare for this pattern
A guide to the Meta coding screen pattern, which has the tightest clock in this catalogue: four problems in seventy minutes.
What the paper looks like
One section: Coding, four problems, two easy and two of medium difficulty, in 70 minutes on a shared clock, which is about seventeen minutes a problem. You can move between the problems freely. Each problem is worth ten marks and is graded on the test cases it passes, with no negative marking and no multiple-choice section. The paper is not adaptive. Speed is the test: not finishing is normal, and getting three clean is a strong result. Meta's format changed in 2025 and two live formats are reported, one problem that unlocks in four stages over 90 minutes and four separate problems in 70 minutes. This mock models the second, because the staged format cannot be reproduced.
How to prepare, section by section
- Coding. Seventeen minutes a problem leaves no time to discover an approach, so the preparation is recognition: seeing a problem and knowing its pattern at once. Build that on the high-frequency hubs, Arrays, Strings, Hash Table, Two Pointers, Sliding Window, Stack, Sorting and Binary Search, then add Breadth-First Search and Depth-First Search for the medium problems. Time yourself: an easy problem should go from reading to a passing solution in about ten minutes. The DSA roadmap is a structured way to cover the ground first.
- Language. Speed depends on fluency with your language's library. Pick one and know its maps, sets, sorting and string methods without looking them up; the Python, Java, C++ and JavaScript study plans cover them.
On the day
Triage before you write. Read all four problems, which takes two minutes at most, and order them by how quickly you can see the solution, usually the two easy ones first. Do not polish: get a correct solution down, check it on the examples, submit, and move on. If a problem is still stuck after twenty minutes, submit what passes and go to the next, because an unread problem scores nothing and a partial one scores something. Come back to unfinished work only once all four have had an attempt.
This mock is modelled on the four-problem variant of Meta's published screen, whose format varies; CodeKairo is not affiliated with Meta.
About this pattern
Varies a lot, and Meta's format changed in 2025. Two live formats are reported: one CodeSignal problem in four unlocking stages over 90 minutes, and four separate problems in 70 minutes. The second is modelled because the staged format cannot be.
Modelled on the published pattern; not affiliated with Meta. Every sitting draws a fresh paper from the aptitude bank and the problem catalogue.