Google New Grad (L3) Interview Guide: OA, R1, Onsite and Team Matching
Prepare for Google software engineer new grad interviews with reported assessment patterns, interview questions, and preparation advice.
On this page
Last reviewed November 10, 2026.
For new grad and early-career software engineers.
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. Apply, take the online assessment a few days later, send your transcript, then R1: one coding round and one behavioral round (45 minutes each). If R1 goes well, R2 is an onsite with two coding rounds, often in person. Then team matching with hiring-manager calls, which can take weeks. Research-track candidates may swap one coding round for an ML domain round.
Round-by-round breakdown
Stage 1: Application, where candidates applied
How it works. Candidates applied on the careers site, some with a referral, and one applied without a referral and still joined Google. In the public account, Google emailed the candidate an invitation and held a virtual briefing for everyone selected.
Stage 2: Shortlisting, how candidates moved forward
How it works. The online assessment arrived quickly, within two days of applying in one report. Most candidates were then asked to submit a transcript, and in one case an updated resume. US candidates had a short visa-status call after R1. One HR team asked about the candidate's research area and offered a choice of loop.
Stage 3: Online assessment
At a glance
- Length: not stated in the new grad reports
- Questions per round: not stated
- What was asked: not described in the new grad reports
- Most common: none
How it works. It came right after applying, and one says the candidate was told they passed the same night. None of the new grad reports describe the OA questions. The main Google guide lists recent OA questions for other levels.
More questions: Browse Google questions.
Stage 4: The interview loop
How it works. Two parts. R1 is virtual: one 45-minute coding round and one 45-minute behavioral round, on the same day or a week apart. R2 is usually an onsite with two coding rounds, held in person in New York, Mountain View or the Bay Area in 2026 reports. One research-track candidate chose one behavioral, one ML domain and two coding rounds.
R1, coding round
At a glance
- Length: 45 minutes
- Questions per round: 1 problem plus 2 follow-ups
- What was asked: heaps and streams, class design, DP
- Most common: no single question repeats; Find Median from Data Stream is the most detailed
Questions candidates reported:
| Question (our summary) | Follow-up reported |
|---|---|
| Find Median from Data Stream (two heaps) | Very small value range; kth smallest instead of median |
| Design a restaurant waitlist | Not stated |
| A dynamic programming problem | A follow-up solved in the last minute |
| An arrays and intervals problem | None |
More questions: Browse Google questions.
R1, behavioral round
At a glance
- Length: 45 minutes
- Questions per round: many; one candidate called it intense
- What was asked: shifting priorities, your role on a team, your biggest challenge
- Most common: none repeated
How it works. 45 minutes, described as intense, with many questions. One interviewer did not ask about the resume at all.
Questions candidates reported: how you handle shifting priorities; what role you play on a team; your biggest challenge; standard questions from recent question lists.
R2, onsite coding rounds
At a glance
- Length: 45 minutes each, 2 rounds back to back, often in person
- Questions per round: 1 problem plus a follow-up each
- What was asked: prefix sums, DFS with memoisation, digit DP, backtracking and tries
- Most common: no single question repeats; the gold-chain split and the mahjong hand are typical
Questions candidates reported:
| Question (our summary) | What it tests |
|---|---|
| Remove one link from a gold chain so two people get equal weight; then every way to do it | Prefix sums |
| Largest sum between two equal values; then in O(1) extra space | Prefix sums |
| Longest water-flow path on a height grid, with a momentum rule | DFS with memoisation |
| Count "good" numbers up to m | Digit DP |
| Is a 14-tile mahjong hand a winning hand? | Backtracking |
| All dictionary words that start with a prefix | Trie |
| A hard backtracking problem | Backtracking |
More questions: Browse Google questions.
Stage 5: Hiring committee, team match and offer
How it works. After R2, candidates got a team-match form and hiring-manager calls. In one report, the time from onsite to team matching was about three weeks.
Topics to prioritise
Across these experiences, the most common topics are behavioral, DP, graphs, arrays, backtracking, stacks and queues, trees. New grad onsites in this data lean more on DP and backtracking than the L4 loops do.
New grad experiences shared on Codinzhub
| College | Role and result | What was asked |
|---|---|---|
| IIT Madras | L3/L4 loop, offered L3 | Leaves with the largest root-to-leaf sum; the longest word that shrinks one letter at a time; a hard DP; Googleyness; a final DSA round |
The Codinzhub Next-Round Playbook
What new grads who reached team matching did. Put together by the Codinzhub team from the new grad experiences in this guide.
To get past the OA
- Do it soon after it arrives. Candidates who passed heard back within days.
To get past R1
- Explain the brute force and its complexity, then the optimisation, and agree with the interviewer before coding.
- Write comments while you code and narrate each step.
- For the behavioral half, prepare a story for every common theme, including how you handle shifting priorities.
To get past the onsite
- Expect DP and backtracking more than at other levels. Practise digit DP, memoised DFS on grids and backtracking.
- Leave time for the follow-up. Candidates who ran out of time on it did not move on.
To get through team matching
- Fill in the team-match form quickly and prepare questions for the hiring-manager calls.
FAQ
Is there system design for new grads?
One report mentions a design-style question (the restaurant waitlist), coded as a class. None describe a full system design round.
How long does it take?
From application to team matching took about 5 months in one report and about 7 months in another.
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.