Google Senior (L5+) Software Engineer Interview Guide: Coding, System Design and the Hiring Committee
Prepare for Google software engineer senior interviews with reported assessment patterns, interview questions, and preparation advice.
On this page
Last reviewed November 10, 2026.
For L5, Senior and Staff candidates.
Built by the Codinzhub team from Google interview experiences that candidates shared, including the ones posted on Codinzhub. Each experience is one person's interview, and Google changes its process by year, level and team, so use this as a map, not a promise.
The 30-second version. A referral or recruiter call, a first loop of one coding round and one Googleyness round (staff candidates had a system design round here instead), then an onsite with two coding rounds and one or two system design rounds. Each coding round is one problem and a chain of follow-ups. A hiring manager must support you before the hiring committee, and team matching can take a month.
Round-by-round breakdown
Stage 1: Application, where candidates applied
How it works. Several candidates were referred by a friend at Google. In one staff account, a recruiter phoned about a month after the referral.
Stage 2: Shortlisting, how candidates moved forward
How it works. A recruiter call about your background and the loop. For staff, the role a candidate was being lined up for was given to someone else before their onsite, so the team is not fixed until team matching.
Stage 3: First virtual loop
At a glance
- Length: 45 minutes per round, 2 rounds
- Questions per round: 1 problem plus follow-ups in coding; 4 to 5 behavioral questions
- What was asked: priority queues with cool-downs, past challenges, difficult coworkers
- Most common: none repeated
How it works. Usually one 45-minute coding round and one 45-minute behavioral round. In the staff account, it was a Googleyness interview with a hiring manager and a system design round instead.
Questions candidates reported:
| Question (our summary) | Follow-up reported |
|---|---|
| Job queue with priorities: addJob and getJob | Each job cools down for 3 calls |
| Behavioral: biggest recent challenge, what you would do differently, a difficult coworker, juggling tasks | Next-day invite to the onsite |
More questions: Browse Google questions.
Stage 4: The onsite
How it works. Two coding rounds (45 minutes) and one or two system design rounds (45 to 60 minutes), in person for some 2026 candidates. Code is written in a Google Doc. The interviewer types notes throughout and keeps pushing with "what if the input becomes X" until time runs out.
Coding rounds
At a glance
- Length: 45 minutes each, 2 rounds
- Questions per round: 1 main problem and a chain of "what if" follow-ups
- What was asked: binary search on the answer, grid graphs and Dijkstra, class design
- Most common: no single question repeats; the tee iterator and the spreadsheet are typical
Questions candidates reported:
| Question (our summary) | What it tests |
|---|---|
| Cut at least K equal pieces from wooden boards; find the longest length | Binary search on the answer |
| Walk from the first row to the last in a 0/1 grid; then all paths; then with weights | BFS, Dijkstra |
| N-by-N tic-tac-toe for K players | Class design |
| Python's tee iterator: n independent iterators from one | Class design |
| A spreadsheet with set_cell and get_cell | Class design, dependencies |
| snake_case to camelCase, then renaming a whole code base and testing it | Strings, open discussion |
| Best anagram match; prerequisite ordering | Hashing; topological sort |
More questions: Browse Google questions.
System design rounds
At a glance
- Length: 45 to 60 minutes; 1 or 2 rounds
- Questions per round: 1 design problem
- What was asked: ranking, paging, one-claim-per-user rules, escalation to humans, crawling
- Most common: no design repeats
Designs candidates reported:
- Deals service: deals arrive weekly, are ranked by browsing history, have start and end times, can be claimed once per user, and are paged 20 at a time with filters.
- Customer-service system where users talk to a virtual agent and can escalate to a human.
- Web crawler.
More questions: Browse Google questions.
Googleyness round
At a glance
- Length: 45 minutes
- Questions per round: varies; one interviewer spent the whole round on one project
- What was asked: why Google, culture, past projects
- Most common: your most challenging project
How it works. One interviewer spent all 45 minutes on a single project. Others asked why Google, what appeals about the culture, and about past projects. "Your most challenging project" was the one question named in the data.
More questions: Browse Google questions.
Stage 5: Hiring committee, team match and offer
How it works. A hiring manager has to support you before your packet reaches the hiring committee. In the staff account, the first team-match call came a month after the onsite, the first team said yes, the committee approved two days later, and the offer was signed by the end of that month.
Topics to prioritise
Across these experiences, the most common topics are behavioral, system design, graphs, object-oriented design. Class-design coding and follow-up depth matter more here than raw algorithm difficulty.
The Codinzhub Next-Round Playbook
What L5+ candidates who moved on did. Put together by the Codinzhub team from the senior experiences in this guide.
To get past the first loop
- Ask which requirements are in scope when several are pasted at once.
- Know one project well enough to talk about it for 45 minutes.
To get past the onsite coding rounds
- Say out loud when a direction is not working; that is when the useful hint comes.
- Practise class-design problems (an iterator, a spreadsheet, a game board) in the language you will use.
To get past system design
- Use a fixed structure: requirements, scale, data model, APIs, then trade-offs.
- Practise ranking, paging and one-claim-per-user rules; they came up in a reported design.
To get to an offer
- Make sure a hiring manager supports you. Without one, your packet does not reach the hiring committee.
About this guide
This guide is researched and written by the Codinzhub team. We read every Google interview experience we could find, kept only what candidates actually described, and rewrote it in our own words. Questions are our own short summaries; the practice links point to similar problems, not the exact interview questions. Found something out of date? Share your own experience on Codinzhub and we will update the guide.
Keep track of what you’ve learned.