Frontend interview guide
Meta
Facebook, Instagram, WhatsApp, Threads, Messenger. The frontend org that invented React — and that still shapes the discipline.
Frontend engineers interviewing at Meta. The FE loop at Meta is one of the most structured and well-known in the industry.
Last reviewed 2026-10-04
What they emphasise
- React depth — reconciliation, hooks internals, performance measurement with the real profiler.
- UI building fluency — the Meta loop famously centres on real component builds under time pressure.
- Algorithmic bar — present but less dominant than at Google. Enough to pass, not the heart of the loop.
- Behavioural specifics — 'move fast, be bold, impact' translated into measurable outcomes.
The loop, round by round
5 rounds. Durations and formats are typical, not guaranteed — confirm the loop shape with your recruiter in the screen.
Round 1
Recruiter screen
~30 minPhone or videoWhat it covers
- Resume, level alignment, loop shape confirmation.
What they're looking for
- A specific, team-aware answer for why Meta and why this product.
Round 2
Technical phone screen
45 minLive coding — often an actual UI build in a shared editorWhat it covers
- A real component build (an autocomplete, an infinite-scroll list, a nested comments tree). React, from scratch.
- A short JS/algorithmic warm-up may precede it.
What they're looking for
- Shipping a working component in the hour.
- Visible iteration under feedback — adding keyboard nav or an empty state when prompted.
Round 3
Onsite: UI coding (two rounds)
45–60 min eachLive coding, usually two separate component buildsWhat it covers
- Two UI builds in Meta's famously detailed component rubric — infinite scroll, autocomplete, tabs, tag input, modal, nested comments.
- Clean prop APIs, accessibility, loading/empty states, keyboard nav.
What they're looking for
- Correctness and completeness within the time.
- Accessibility baked in, not bolted on.
- A visible 'what I would do next with more time' at the end.
Round 4
Onsite: system design
45 minWhiteboard / shared docWhat it covers
- A frontend-shape prompt in the Meta product domain — a feed, a chat, a photo-heavy feature, a notifications surface.
- Rendering strategy, data model, concurrency, real-time, scale.
What they're looking for
- Clarifying questions first, trade-offs named explicitly.
- Specific numbers — 'at 10M users we need…', not 'at scale we need…'.
Round 5
Onsite: behavioural ('Jedi')
45 minConversationWhat it covers
- 'Impact', 'conflict', 'hardest project', 'most difficult teammate', 'biggest mistake'.
- Grounded in specific, time-bounded stories.
What they're looking for
- Specific, measurable outcomes — 'cut TTI by 400ms', 'saved the team two engineer-months'.
- A real 'I was wrong, I changed, here's what happened' story — the lack of one reads as insufficient scar tissue.
What each level expects
The bar you're being measured against — plus the failure modes candidates most often trip on at that level.
SDE 2 / mid
~2–4 yearsE4 — owns features end to end with mentorship.
What they expect
- Can ship a UI component build to the Meta rubric in the time allotted.
- Comfortable with React internals at the hooks-and-reconciliation level, not just the API.
Common failure modes
- Spending the first 15 minutes thinking about architecture before writing any code. The UI rounds reward iteration.
- No accessibility pass — in a Meta loop, missing keyboard navigation is often the deciding gap.
Senior
~5–8 yearsE5 — technical lead for an area, mentor to mids.
What they expect
- A system design round where the discussion goes deep — not a presentation, a conversation.
- Behavioural stories with measurable outcomes and a clear 'I owned this'.
Common failure modes
- Behavioural stories at the 'we' level — the loop is explicit about wanting 'I did X'.
- A system design that reads as the standard answer with no adaptation to the specific prompt.
Staff
~8+ yearsE6 — technical direction across teams, drives multi-quarter initiatives.
What they expect
- Visible leverage — your work made other engineers more productive, measurably.
- A system-design discussion that is peer-to-peer, not candidate-to-judge.
Common failure modes
- E5+ output rather than E6 leverage. The Staff bar is explicitly about multiplying others.
How to crack it
Day-of advice. The specific moves that separate offers from no-offers when the content is already in your head.
- 1Grind the Meta UI build pattern. Autocomplete, infinite scroll, nested comments, tabs — rebuild each one from scratch, with keyboard support, in under 45 minutes.
- 2Learn React's reconciliation and hooks internals well enough to answer 'why is this re-rendering' without the profiler.
- 3For the system-design round, know the three or four 'classic' Meta prompts (feed, chat, photo feature) cold, with clarifying questions pre-rehearsed.
- 4Pre-write six behavioural stories using Meta's rubric (impact, conflict, growth). Rehearse to 2 minutes each with specific numbers.
- 5In the UI rounds, show your working — talk through your plan before coding. The signal is iteration speed, not clean one-shot writes.
How to master it (over months, not days)
The longer-horizon work. These are the habits that pay off at Senior+ bars where cramming visibly fails.
- Ship a real production React app. The UI rounds reward people who have built products, not just studied components.
- Read React core team blog posts and PRs. The culture of thoughtful technical writing is explicit at Meta.
- Build one component to the standard of a production component library — API design, docs, tests, accessibility, versioning. The depth is what makes the Senior+ bar.
- Pick an accessibility pattern (focus management, ARIA tabs, live regions) and own it. One deep area beats broad surface knowledge.
- Follow one React core team member on their blog or Mastodon. Patterns of thinking are learnt by watching.
Resources
On-site content for the technical prep, plus short-list of external links worth your time.