This guide tracks 10 patterns, 17 commonly reported questions, and a 4-round loop that usually runs 3-5 weeks.
Key patterns
Showing 3 of 10Common questions
Showing 3 of 17Interview process
Showing 1 of 4 roundsStart studying now, without an account
Every lesson below is a free public reading page. No sign-up, no install, and the worked examples run in the tab.
The Python behind Meta's top patterns
These lessons do not teach the patterns themselves. They teach the language mechanics each pattern is built from, which is the part you have to have in your hands before the pattern is worth practicing.
- Arrays & HashingPython10 min readTuples & setsGroup fixed records with tuples and track uniqueness with sets.
- Arrays & HashingPython10 min readDictionariesMap keys to values: read safely, assign, and merge dictionaries.
- TreesPython11 min readRecursion: a function that calls itselfSolve a problem in terms of a smaller version of itself, with a base case to stop.
- Binary SearchPython22 min readShrink the failing inputA bug report with a 400 row file is not a diagnosis. Cut the input down until removing anything else makes the failure disappear, and the answer is usually visible.
- StringPython9 min readString indexing & slicingReach into text by position, take slices, and measure length.
- StringPython10 min readString methods & f-stringsClean and reshape text with methods, and build strings with f-strings.
How Meta judges you outside the code
The values and engineering norms the interviewers are calibrated against. Useful for the behavioral round, and useful for deciding which trade-off to argue for in the technical one.
Values they name
- Move Fast - velocity matters, ship and iterate
- Be Bold - take risks and don't fear failure
- Focus on Impact - prioritize work that matters
- Be Open - share information, give/receive feedback openly
- Build Social Value - create meaningful connections
What they look for in behavioral rounds
- Demonstrate bias for action and shipping quickly
- Show you can work at scale and with large impact
- Exhibit openness to feedback and direct communication
- Display comfort with rapid change and ambiguity
- Show you can build and maintain relationships across teams
How the team builds
- Ship early and iterate - don't over-engineer
- Code wins arguments - build prototypes to prove ideas
- Bootcamp for new engineers - learn the codebase hands-on
- Internal tools are first-class products
- Embrace the monorepo - one codebase for web
Primary stack
- React
- React Native
- Hack/PHP
- Python
- C++
- PyTorch
- GraphQL
- Mercurial
- Code review
- fast async reviews with focus on shipping
- Deployment
- continuous deployment multiple times per day
- Documentation
- lightweight - code is documentation
Reading the guide is the easy part. Meta will ask you to perform.
CodeSparring is a practice environment, not a question bank. You sit a full round against an AI interviewer, in an editor that runs your code, and you leave with a score and a specific next rep.
An interviewer that reacts
Carry one problem from clarifying questions through to working code while an AI interviewer responds to what you say and what you type, by voice or by text.
Code that actually runs
An editor in the page with a real runtime and real test cases. You run your solution and read the output, the same way you would in a shared editor on the day.
A scored round, not a vibe
Every session ends with a rubric covering problem solving, communication, and code quality, so you can see which part of the round is costing you the offer.
And 364 lessons you can read right now, free
The whole curriculum is public. Read the concept, run the worked example in the tab, and only sign in when you want the graded exercise at the end of a lesson.