Two facts shape the Google system design interview, and most candidates prepare for neither. First, a separate design round usually appears only at L5 and above. Second, the people who decide your result never met you. Your interviewers write feedback, and a hiring committee reads it and decides.
That second fact changes how you should behave in the room. You are not only convincing the person in front of you. You are giving them evidence they can write down, because their written notes are the only version of you the committee sees.
This article covers the Google loop, which levels get a design round, what the hiring committee actually reads, how the 45 minutes are spent, and what to practice.
The Google loop, round by round
Google usually starts with a recruiter call, then one or two technical phone screens. Passing those leads to the full loop of four to five interviews, often called the onsite even when parts are remote. Some loops now include an in-person day.
A common loop for an experienced engineer looks like this:
| Round | Length | What it covers |
|---|---|---|
| Coding | About 45 minutes | Data structures and algorithms |
| Coding | About 45 minutes | More coding, same format |
| Coding | About 45 minutes | A third coding round on many loops |
| System design | About 45 minutes | One open design question, L5 and above |
| Googleyness and leadership | About 45 minutes | Behavioral questions about your past work |
Note what is different from Amazon. The behavioral material has its own round, called Googleyness and leadership. Your design round is purely technical, and the full 45 minutes are yours to design in.
Which levels get a design round
Google reserves the standalone design round for L5 and above. An L3 or L4 loop is normally all coding plus the behavioral round. If a design topic appears at all for L4, it appears briefly inside a coding round.
Two consequences are worth planning for.
Interviewing at L5 means design can decide your level. The committee can approve you at a lower level than you interviewed for. A strong coding performance with a weak design round is the classic path to an L5 candidate receiving an L4 offer. Preparing the design round is how you defend the level, and the compensation band that comes with it.
Interviewing at L4 does not make design prep wasted. A design question inside a coding round is short and unpolished, and a candidate who can structure even ten minutes of it stands out. The habit also arrives with you at your next promotion cycle.
If you are unsure which level your loop targets, ask the recruiter directly. The answer decides whether you should split your time or spend nearly all of it on coding.
The hiring committee, and what it changes
At most companies, your interviewers meet and decide. At Google, they do not decide. Each interviewer writes detailed feedback, with a score, usually within a day of your interview. The feedback, your resume, and any referrals form a packet.
A hiring committee then reviews the packet. It is a small group of experienced Googlers who were not in your loop. They can approve, reject, or send the packet back for one more interview. They also set the level. Committee review is the reason Google decisions take longer than most companies.
This structure has one practical consequence: be easy to write up. An interviewer can be privately impressed and still produce vague notes, and vague notes lose in committee. You make the notes concrete by doing three things:
- Say your trade-offs out loud, with the option you rejected and the reason. "I chose leader-based replication over leaderless because we need read-your-writes here" is a sentence an interviewer can copy into feedback.
- Put numbers on the design. Users, requests per second, storage per year. A design with stated scale reads as evidence. One without reads as opinion.
- Name your assumptions before building on them. The committee reads for judgment, and stated assumptions are what judgment looks like on paper.
There is no Bar Raiser at Google. No single person can veto you. The committee is the check, and it works on the written record.
How the 45 minutes are spent
The round is shorter than most candidates expect, and it has no behavioral opening to absorb the time. A workable split:
- 5 minutes, requirements. Google questions are deliberately vague. Design search for a product catalog. Narrowing the question is part of the test, so ask what is in scope, who the users are, and what matters most.
- 5 minutes, estimation. State users, traffic, and storage. Round numbers are fine. Skipping this is a common mark against candidates at Google specifically.
- 15 minutes, high-level design. Draw the main parts and the data flow. Keep it changeable, because the interviewer will move you.
- 15 minutes, deep dive. The interviewer picks one part and pushes. Data structure, failure case, what happens at ten times the load.
- 5 minutes, trade-offs and wrap-up. Say what your design makes worse and what you would measure first.
Google interviewers are trained to probe ambiguity. Expect the question to shift mid-round. That is not a trap. It is a test of whether your design can absorb a change without collapsing.
What changes by level
| Level | Title | What separates a pass from a fail |
|---|---|---|
| L4 | SWE III | Mostly coding. Structure and clarity if design appears at all |
| L5 | Senior SWE | A complete design, trade-offs chosen out loud, one area in real depth |
| L6 | Staff SWE | Constraints you set yourself, failure handling, cost, and evolution over time |
| L7 | Senior Staff | Ambiguous problems spanning systems, and the organizational cost of choices |
The L5 bar is a complete, defensible design produced with little steering. The L6 bar is noticing the hard part before the interviewer points at it, and designing for what the system becomes in two years, not just for launch day.
The questions Google asks most often
Google questions lean toward its own problem space: search, video, crawling, location, collaboration, and very large scale. These free lessons cover the closest published versions:
- Designing typeahead suggestion, the autocomplete problem, the most Google-shaped question there is
- Designing a web crawler, for crawling, deduplication, and politeness at scale
- Designing YouTube or Netflix, for video upload, encoding, and serving
- Designing Twitter search, for indexing and querying large text corpora
- Designing Yelp or nearby friends, for location search and proximity, the Maps-shaped question
- Designing Gmail, for mailbox storage, search, and spam filtering
The building blocks underneath them are worth studying on their own: caching, sharding, replication, and the CAP theorem.
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 typeahead, the web crawler, YouTube, and Twitter search.
What to practice, in order
Practice narrowing a vague question. Take a one-line question and spend five timed minutes turning it into requirements and numbers. Google grades this step more heavily than most companies.
Do estimation until it is boring. Users to requests per second to storage per year, in under five minutes, for any system. This is the most mechanical skill in the round and the one Google candidates most often skip.
Prepare one deep dive per problem. For every practice design, pick one part you can defend for ten minutes. Know the data structure, the failure case, and the option you rejected.
Rehearse being quotable. After each practice design, write the three sentences an interviewer should have in their notes. If you cannot write them, the interviewer could not either.
Practice the Google-shaped problems first. Typeahead, crawler, video, search, location. The same half-dozen mechanics repeat across most questions Google actually asks.
Frequently asked questions
How long is the Google system design interview? About 45 minutes, and all of it is design. Behavioral questions live in a separate Googleyness and leadership round.
Does Google ask system design at L4? Usually not as a separate round. L4 loops are mostly coding, and design appears only briefly inside a coding round if at all. The standalone round starts at L5.
What is the hiring committee? A small group of experienced Googlers who were not in your loop. They read every interviewer's written feedback and decide the hire and the level. No single interviewer can approve or veto you.
Can Google offer me a lower level than I interviewed for? Yes. The committee sets the level from the packet, and a weak design round is the most common reason an L5 candidate receives an L4 offer.
How is Google's round different from Amazon's? Amazon opens the design round with Leadership Principle questions, which costs about 15 minutes. Google keeps behavioral material in its own round, so you design for the full 45 minutes. Amazon has a Bar Raiser with a veto. Google has a committee instead.
What is the most common reason candidates fail this round? Designing before narrowing. The question is vague on purpose, and candidates who start drawing boxes without stating requirements, users, and numbers leave the interviewer nothing concrete to write down.
Related reading
- The Meta System Design Interview, for a 45-minute round with a very different scoring style
- The Amazon System Design Interview, for the loop where behavioral questions share your design hour
- Top 30 System Design Interview Questions and Answers
- System Design Interview Prep When You Have Never Built a Distributed System
- A Beginner's Guide to System Design Interviews, if this is your first design round
Prepare for Google in this order: building blocks, one repeatable method, then the Google-shaped problems, then timed practice at narrowing vague questions. The committee never sees your diagram. It sees what your interviewer wrote about it, so practice saying your reasoning out loud. If you want the method and the case studies already assembled, start with Grokking the System Design Interview.