0 day streak

Google interview rounds

Big techProduct US and India AI-assisted coding

Pick your level above: the list shows only your rounds, with what interviewers score at that level.

0%ready
  1. Online assessment · 90 min

    Some candidates, often from referrals or recruiter outreach, get the Google Hiring Assessment (a survey-style questionnaire) and an easy coding test before any live interview.

    At : The main filter for new grads and campus drives. Expect two medium problems, sometimes one hard. Passing all test cases on both usually gets you to the next round.

    At : Used by some companies for experienced hires (Amazon, Uber, Salesforce, Oracle). The bar is the same as for SDE 1 but the time is often shorter.

    At : Rare. Most companies replace it with a live screen for senior candidates.

    At : Almost never used.

  2. Phone / recruiter screen · 45 min

    One live data-structures-and-algorithms problem, sometimes two, in a shared doc with no code execution; a second screen is added only when the first gives too little signal.

    At : Usually one medium problem. Explain your idea before coding and test by hand at the end.

    At : One or two problems, a little faster. Some companies mix in a design question.

    At : Often a coding problem plus questions about your past systems; some companies (Uber) use it to set your level.

    At : Frequently a hiring-manager conversation about scope and impact instead of pure coding.

  3. Coding (DSA) × 3 · 45 min

    Junior loops are mostly coding (about 3 rounds); senior loops drop to about 2 as design rounds take their place, and some prompts ask you to build a small class with several methods.

    At : The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.

    At : Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.

    At : Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.

    At : One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.

  4. AI-assisted coding · 45 min

    A pilot reported in May 2026 for some US junior and mid-level loops swaps one coding round for a code-comprehension round where you read, debug and optimize an existing codebase with Gemini available.

    At : Focus on reading unfamiliar code quickly and fixing the bug correctly. Explain every line you accept from the AI.

    At : Expected to move through all stages and test as you go.

    At : Expected to plan the change, use the AI for routine parts, and catch its mistakes.

    At : Where used, scored on design decisions and how you verify, not on speed.

  5. System design (HLD) · 45 min

    An open-ended design round is standard from L5; staff candidates may get two and are expected to drive the discussion.

    At : Usually absent, or light design questions inside a coding round.

    At : Present at most companies. A sound end-to-end design with sensible components and basic scaling is enough.

    At : One or two rounds that set your level. Expected to lead, size the system and go deep on two or three hard parts.

    At : Two rounds at many companies. Expected to handle ambiguity, cost, operations and cross-team trade-offs, and to change the design when the interviewer pushes.

  6. Behavioral · 45 min

    The Googleyness and Leadership round uses STAR-style questions on ambiguity, conflict and learning; the 2026 pilot adds a technical talk-through of a past project.

    At : Stories from internships, projects or your first job are fine. Show learning, ownership and teamwork.

    At : Stories should show you owning features end to end and handling conflict maturely.

    At : Expected scope: projects across quarters, influencing other teams, mentoring.

    At : Expected scope: org-wide impact, setting direction, hard trade-offs with leadership.

  7. Team match · 30 min

    You talk with managers who have open headcount, both sides have to opt in, and this step now usually comes before the hiring committee review.

    At : Mostly about whether the packet clears the bar; team match can take a few weeks.

    At : Committees can down-level you instead of rejecting.

    At : Down-leveling to SDE 2 is the most common surprise outcome.

    At : Staff packets get extra scrutiny on design and behavioral scope.

  8. Hiring committee

    A panel of Googlers who did not interview you reviews the full packet and decides hire or no-hire and the level, so passing the onsite does not guarantee an offer.

    At : Mostly about whether the packet clears the bar; team match can take a few weeks.

    At : Committees can down-level you instead of rejecting.

    At : Down-leveling to SDE 2 is the most common surprise outcome.

    At : Staff packets get extra scrutiny on design and behavioral scope.

What interviewers look for

  • Breaks a vague problem into parts and asks clarifying questions before coding
  • Reaches an optimal or near-optimal algorithm and explains the complexity trade-offs
  • Writes clean, correct code without running it and checks it by hand
  • Thinks out loud: the reasoning counts as much as the final answer
  • Handles follow-ups that change the constraints
  • Collaboration, humility and comfort with ambiguity
  • At L5+: architecture reasoning, scalability and defensible trade-offs

Worth knowing

  • In June 2025 the CEO said Google is bringing back at least one in-person round, so it can confirm candidates have the fundamentals now that remote interviews are exposed to AI cheating.
  • A May 2026 report describes a 'human-led, AI-assisted' pilot for junior and mid-level roles on select US teams: one coding round becomes a code-comprehension round with Gemini.
  • Under the same pilot, the Googleyness and Leadership round adds a design discussion about a project you actually worked on.
  • Team matching now usually happens before the hiring committee review, and a hiring manager's support goes into the packet.
  • Outside the pilot, using AI in a Google interview is still forbidden. Publicly tagged questions are reportedly retired, so learn patterns instead of memorizing lists.
  • Downleveling is common: the committee can offer a lower level than the one you applied for.

Sources

Written in our own words from public candidate reports and Google's careers pages, checked 2026-11. Company names and logos belong to their owners; AlgoRung is not affiliated with Google.

Questions people ask

How many interview rounds does Google have for SDE 1 (L3 Software Engineer II)?

About 5 interviews after the screening: online assessment, phone / recruiter screen, coding (dsa), ai-assisted coding, behavioral, team match. There is usually no separate design round at this level.

How many interview rounds does Google have for SDE 2 (L4 Software Engineer III)?

About 5 interviews after the screening: phone / recruiter screen, coding (dsa), ai-assisted coding, behavioral, team match. There is usually no separate design round at this level.

How many interview rounds does Google have for SDE 3 (L5 Senior Software Engineer)?

About 5 interviews after the screening: phone / recruiter screen, coding (dsa), system design (hld), behavioral, team match. Design is part of the loop at this level.

How many interview rounds does Google have for staff (L6 Staff, L7+ Senior Staff and above)?

About 5 interviews after the screening: phone / recruiter screen, coding (dsa), system design (hld), behavioral, team match. Design is part of the loop at this level.

What coding questions does Google ask?

The most reported are Implement Trie (Prefix Tree), Snapshot Array, Minimum Domino Rotations For Equal Row, Long Pressed Name, Expressive Words, Text Justification. Candidates say Google focuses on graphs, trees, tries, dynamic programming, arrays and strings.

What is the Google behavioral interview based on?

Googleyness and Leadership, plus the four hiring attributes: General Cognitive Ability, Role-Related Knowledge and Experience, Leadership, Googleyness. Every interviewer writes standardized feedback that maps to these attributes. The G&L round covers Googleyness (comfort with ambiguity, bias to action, collaboration) and emergent leadership: stepping up when the situation needs it.