Meta Interview Questions
The coding and system-design questions asked in Meta interviews - with worked solutions, in-browser code execution, and active-recall review. 11 questions.
How Meta interviews software engineers
Meta's loop starts with a recruiter call and often a CodeSignal online assessment, then a technical phone screen, then a full onsite. The onsite is typically two coding rounds, a design round (system design or product architecture depending on role), and a behavioral round.
Meta has been rolling out an AI-enabled coding round that can replace one traditional coding interview - a 60-minute session in a CoderPad environment with an AI assistant available. Coding rounds favor speed plus correctness on two problems per 45-minute slot.
The interview loop
- 1Recruiter screenBackground, level calibration, and logistics; recruiter shapes the loop.
- 2Online assessmentCodeSignal coding assessment (proctored) as an early screen for many candidates.
- 3Technical phone screen45 min, usually two coding problems in a shared editor - medium/hard DS&A.
- 4Onsite loopTwo coding rounds (one may be the AI-enabled format), a system design or product architecture round, and a behavioral round.
What they look for
- Fast, correct coding - typically two problems per 45-minute round
- Design depth: distributed systems for infra roles, API/client design for product roles
- Behavioral signal mapped to Meta's values (move fast, impact)
How to prepare
- Practice solving two medium problems in 45 minutes, talking throughout.
- Know which design flavor your role uses - system design vs product architecture - and prep accordingly.
- If you draw the AI-enabled round, practice directing an assistant without losing your own reasoning.
Sources
- interviewing.io - Meta/Facebook hiring process - Senior-engineer breakdown of the loop.
- IGotAnOffer - Meta software engineer interview - Process, questions, and prep.
- Hello Interview - Meta's AI-enabled coding round - What the new AI-assisted coding interview is and how to prepare.
See every company's references on the interview-process sources page.
Practice questions
- Weather App
Design a forecast app like the Google or Apple weather app - one screen for the current location, a forecast that loads instantly from cache, an honest offline state, and a constrained background refresh.
Mobileeasy-1mo+2
- Analytics / Logging SDK(premium)
Design a Firebase-Analytics-lite / Amplitude-lite Android SDK - microsecond-budget `track()` on the main thread, a durable on-device queue that survives OOM kill, and batched uploads that respect battery and consent.
Mobilehard-2mo - HTTP Client Library(premium)
Design an OkHttp-lite Android HTTP client - the shared layer every network call flows through. Reuse warm connections, cache and retry safely, pin TLS certificates, and keep any one call from running forever.
Mobilehard-2mo - Image Loading Library(premium)
Design a Coil / Glide-lite Android image loader - memory + disk + network cache ladder, in-flight request dedup, downsampled decode, cancel-on-rebind, and bitmap pooling that keeps a 100-cell `LazyVerticalGrid` at 60 FPS without OOM.
Mobilehard-2mo - Messenger App(premium)
Design an Android messenger - a durable outbox so a tapped message survives a kill, a server-assigned per-chat seq so order is a property of the data, reconnect catch-up, and FCM wakeup for offline recipients.
Mobilehard-2mo+5
- Photo Gallery App(premium)
Design a Google Photos-style gallery - one timeline over the device and cloud libraries, background backup, full-resolution viewing, fresh-device restore.
Mobilehard-1mo+3
- Newsfeed App(premium)
Design an Android social feed - opaque cursor pagination over Paging 3 + RemoteMediator, optimistic engagement with idempotent retries, 60 FPS mixed-media scrolling with autoplay video, and pull-to-refresh that surfaces new posts without losing the reading position.
Mobilehard-2mo+7
- Ride-Sharing App(premium)
Design an Uber / Lyft-lite Android rider app - a server-authoritative ride state machine, an idempotent ride request that survives a process kill, a 1-2 Hz driver-location stream interpolated to 60 FPS, FCM (Firebase Cloud Messaging) wakeup when the WebSocket is closed, and reconnect-and-reconcile under cellular drops.
Mobilehard-2mo+4
- Valid Parentheses
Stack-walk a bracket string to validate it, then localize the first error, then find the longest valid substring (LC 32).
Practicalmedium35m2mo+12
- Time-Based Key-Value Store(premium)
A key-value store with timestamped writes. Read at time t returns the latest value written at or before t; later phases add arbitrary-order inserts and range queries.
Practicalmedium35m2mo+9
- Meeting Rooms(premium)
Given a list of half-open meeting intervals, find the minimum number of conference rooms; later phases assign specific room IDs and add capped capacity with priority eviction.
Practicalmedium35m2mo+9