The Meta system design round is 45 minutes, one interviewer, one open question, and no code. You are not scored on recalling a known architecture. You are scored on how you narrow a vague problem, choose between options, and explain why you chose them.
That difference decides most outcomes. Many candidates prepare by memorizing designs for Twitter and Instagram. They then fail when the interviewer changes a requirement, because a memorized design cannot adapt.
This article covers the Meta loop, the two kinds of design interview Meta runs, and how the 45 minutes are spent. It also covers what the interviewer records afterwards and what to practice at each level.
The Meta interview loop, round by round
Meta usually runs two stages. First a technical screen, which is normally coding only. Then a full loop of four to five interviews, held on one or two days.
A common loop for a backend engineer looks like this:
| Round | Length | What it covers |
|---|---|---|
| Coding | 45 minutes | Two problems, data structures and algorithms |
| Coding | 45 minutes | Two more problems, same format |
| System design | 45 minutes | One open design question |
| Behavioral | 45 minutes | Past projects, conflict, influence, ownership |
The number of design rounds depends on the level you are interviewing for. Entry-level candidates often get no design round at all. Senior candidates get one. Staff candidates sometimes get two, with the second one deliberately harder.
Ask your recruiter which rounds you have. They will tell you, and the answer changes what you should practice.
The two kinds of design interview Meta runs
This is the detail most preparation guides miss. Meta does not run one design interview. It runs two, and which one you get depends on the team and the role.
| Product architecture | Systems and infrastructure | |
|---|---|---|
| Typical question | Design a live comments feature | Design a distributed key-value store |
| Main focus | Data model, API, client and server interaction | Storage, replication, consistency, failure |
| What gets deep attention | How the product behaves for a user | How the system behaves under load and failure |
| Common roles | Product engineering, mobile, full stack | Infrastructure, storage, traffic, data |
Product architecture rounds still involve scale, but the conversation starts from the user experience. You will spend real time on what the client sends, what the server returns, and how the data is shaped. Infrastructure rounds start from the storage layer and remain focused on it.
Both use the same 45 minutes and the same open format. Preparing only for the infrastructure version is the most common preparation mistake for product roles.
How the 45 minutes are actually spent
Time is the constraint most candidates underestimate. Forty-five minutes includes introductions and questions at the end, so your working time is closer to 35.
The first five minutes matter more than any other five. This is where you ask what the system must do, who uses it, and how much traffic it carries. An interviewer who watches you start drawing boxes immediately has already recorded something negative.
The deep dive usually determines your level. The interviewer picks one part of your design and pushes on it. For a feed question that might be the fan-out strategy. For a storage question it might be what happens when a replica falls behind.
What the interviewer records afterwards
Meta interviewers write structured feedback and give a rating. They do not fill in a public scorecard, and no published rubric exists. What they are asked to comment on is consistent enough to prepare for.
Scoping. Did you convert a vague question into a specific problem? Did you name what you were leaving out?
Structure. Was there a recognizable order to your design, or did the conversation wander?
Depth. When pushed on one part, did you have real detail, or did the answer stop at the name of a technology?
Trade-offs. Did you present options and choose between them, with a reason? A design with no rejected alternative looks memorized.
Communication. Could the interviewer follow you without asking what you meant? Interviewers cannot score reasoning they cannot hear.
One point worth knowing: your level is decided across the whole loop, not in one interview. A strong design round can move a senior candidate up. It rarely rescues a loop that went badly elsewhere.
What changes by level
| Level | Design rounds | What separates a pass from a fail |
|---|---|---|
| E4, mid-level | Often none, sometimes one | A working design with correct components and a clear explanation |
| E5, senior | One | Trade-offs chosen out loud, and one part designed in real depth |
| E6, staff | One or two | Constraints you set yourself, failure handling, and cost or operational reasoning |
The difference between E4 and E5 is the difference between describing and deciding. At E5 the interviewer wants to hear you reject an option and say why. At E6 they want you to identify the hard part of the problem before they point at it.
If you are unsure which level you are being assessed at, ask. Preparing for E6 depth when you are interviewing at E4 wastes time you could spend on fundamentals.
The questions Meta asks most often
Meta questions tend to come from its own products. Feeds, messaging, notifications, search suggestions, and media storage come up repeatedly. These free lessons cover the classic versions of each:
- Designing Facebook Newsfeed, the single most common Meta design question
- Designing Facebook Messenger, for chat delivery and presence
- Designing Instagram, for photo storage and feed generation
- Designing Typeahead Suggestion, for search boxes and autocomplete
- Designing Twitter, which shares most of its structure with the feed question
Learn the newsfeed problem properly before any other. Fan-out on write against fan-out on read is the trade-off Meta interviewers return to most, and it transfers to notifications, timelines, and live comments.
The building blocks underneath those questions are worth studying on their own: caching, sharding, replication, consistent hashing, and message queues.
If you want the case studies and the trade-off practice in one place, that is what Grokking the System Design Interview is built for. It contains 83 lessons and 15 full design problems, including the feed, messenger, and typeahead questions above.
What to practice, in order
Practice the first five minutes on their own. Take any design question and spend five minutes only on requirements and scale. Do this ten times. It is the cheapest improvement available, and it is the part most candidates never rehearse.
Practice being interrupted. Ask a friend to change one requirement halfway through. Make it ten times more traffic, or add a second region. A memorized design cannot survive this, which is exactly why interviewers do it.
Practice one deep dive per problem. Pick one part of your design and prepare to defend it for ten minutes. Know the data structure, the failure case, and the alternative you rejected.
Say numbers out loud. Estimate daily active users, writes per second, and storage per year. You do not need precision. You need to show the design follows from the numbers rather than being chosen first.
Match your practice to the round you will get. Product roles should practice feeds, comments, and notifications. Infrastructure roles should practice storage, queues, and replication.
Frequently asked questions
Does Meta ask system design questions at every level? No. Entry-level candidates often have a loop with no design round. Senior candidates almost always have one. Staff candidates may have two, and the second is usually deeper on failure and operations. Ask your recruiter which rounds are scheduled.
How long is the Meta system design interview? Forty-five minutes, including the introduction and your questions at the end. Working time is closer to 35 minutes, which is why scoping quickly matters.
Is the Meta system design interview harder than at other companies? Not harder, but differently shaped. Meta leans toward its own product surface, so feed, messaging, and notification problems appear more often than at companies whose products are infrastructure.
What is the Meta product architecture interview? It is a design round for product-focused roles. The question centers on the data model, the API, and how client and server interact, rather than on storage internals. It is still a 45-minute open design conversation.
Can I use a whiteboard or a drawing tool? Yes. Remote loops use a shared drawing surface, and onsite loops use a whiteboard. Keep the drawing simple. The interviewer scores your explanation, not the diagram.
How much distributed systems experience do I need? Less than most candidates assume. You need the vocabulary and a method for reasoning out loud. If you have never operated a large system, read preparing without distributed systems experience.
Related reading
- A Beginner's Guide to System Design Interviews, if this is your first design round
- System Design Interview Prep When You Have Never Built a Distributed System
- Top 30 System Design Interview Questions and Answers
- System Design vs Object Oriented Design Interviews, because some loops include both
- Grokking System Design Fundamentals vs the Interview Course, if you need the building blocks first
Preparing for a specific company is worth doing last, not first. Learn the building blocks, learn one repeatable method, then adjust for the feed and messaging problems Meta prefers. If you want that structure with the case studies already written, start with Grokking the System Design Interview.