Google interview, from the behavioral round to the offer.

Updated · Sources at the end

Google publishes more about how it interviews than most companies, and the behavioral half is where its own words help most. Its hiring page says every candidate is assessed using clear rubrics, the same ones for everyone considered for that role, and that interviewers ask role-related, open-ended questions to learn how you solve problems and how you work with a team. Its interview tips page says many questions will sound like "Tell me about a time when..." or "How would you approach this situation...?" and asks for specific examples with data.

The name candidates use for the behavioral round, Googleyness and Leadership, does not appear on Google's current careers pages. It comes from ex-Googlers and prep guides, and in May 2026 Business Insider reported from an internal document that the round now also includes a technical design conversation about your own past work. Before any of this, Google may send its Hiring Assessment, a work-style questionnaire, and new graduates usually take a coding test.

Free · 2 minutes · no account

The questions for your exact Google role and level.

01

Who Google hires

Google hires software engineers from new graduates to Senior Staff, site reliability engineers, product managers from Associate Product Manager up, technical program managers (289 US openings on 13 October 2026, many on AI and DeepMind programs), and a large number of people in Cloud, sales, design and research. In the US, current engineering ads list roles on Search, YouTube, Google Cloud, Photos, Android and the AI teams, in Mountain View, Sunnyvale, San Jose, New York, Seattle, Kirkland and other offices. You can apply for up to three jobs in a rolling 30-day window, and Google asks people who were not selected to wait about a year before applying for the same type of role again.

Wondering whether your resume reads like someone Google hires? Get a free resume review.

Google says the basics are the same whether you apply for engineering, marketing, an internship or a leadership role. What sits around the interviews changes with the role and the level. These are the versions most people searching this page will meet.

  • Track · New grad

    New grad and intern engineers (L3)

    You apply with a resume and a transcript. Candidates report a timed coding test of two problems in 60 to 90 minutes before any live interview, and some report a separate behavioral fit questionnaire in the same invite. Then come the technical interviews, with no system design round in the loops candidates report. Google's own early career ads list one year of software experience or a degree as the bar.

  • Track · Mid and senior

    Software engineers, L4 to L7

    Experienced candidates usually skip the coding test and start with a recruiter call and a technical phone screen. Candidates report no system design round in most US L4 loops in 2025 and 2026, one from L5 and two at L6 and staff, and the behavioral round expects bigger stories as the level rises. Google's US engineering ads now say that in most instances the role requires in-person interviews. Since May 2026 some junior and mid-level US teams pilot a round where you work through existing code with Gemini, as Business Insider reported.

  • Track · PM

    Product managers

    Associate Product Manager roles hire new graduates, and Product Manager I, II and Senior PM roles hire experienced people. Expect product design and strategy questions asked as hypotheticals ("Imagine you..."), alongside the same behavioral questions engineers get. Google's re:Work guide gives a pricing scenario as its own example of a hypothetical question.

  • Track · Other roles

    Sales, Cloud, design and everything else

    Google may ask you to complete a small project before the interviews, such as a case study, a writing sample or code, and may send the Google Hiring Assessment first. The behavioral round works the same way for every role.

  • Track · Europe

    Zurich and Stockholm offices

    The loop is the same in Europe, but team matching, pay and work permits are different. Read the Google Zurich and Google Stockholm guides for those offices.

02

What is the Google interview process?

Google says the process can differ by role and team, and typically takes 6 to 8 weeks once interviews for a role begin. The stages below follow Google's own hiring page. Round counts and lengths, the coding test and the team match come from candidate reports and prep guides, and are marked as reported.

9 roundsApplication · Google Hiring Assessment · Coding online assessment · Recruiter conversations · Technical phone screen · Interview loop · Hiring decision · Team matching · OfferSee each roundHide
01
Application
Online, with your resume; interns and new graduates add a transcript

Up to three applications in 30 days. Google reviews your resume, and your transcript for interns and new graduates, to find the best fit, so pick the roles that match you.

02
Google Hiring Assessment
Online work-style questionnaire, for some candidates

Google says you may be asked to take it before interviews, to measure workstyle skills for the role. Our Google Hiring Assessment guide covers it in full.

03
Coding online assessment
Timed test, reported as two problems in 60 to 90 minutes

Google says you might be asked for a role-related assessment such as a coding exercise. Candidates report two algorithm problems, often one easier and one harder, auto-graded against hidden tests.

Mostly interns and new graduates
04
Recruiter conversations
One or two short calls by phone or video

Google says these usually assess key skills for the role and cover your preferences, such as location. The recruiter also sets your level, which decides which rounds you get.

05
Technical phone screen
One or two video interviews, reported at about 45 minutes

A coding problem in a shared document or editor, solved while you talk. Explain your assumptions and state time and space complexity yourself.

Engineering roles
06
Interview loop
A panel of interviews over video or in person, reported as four to five of about 45 minutes

For engineers: two or three coding rounds, system design from L5 (one round at L5, two at L6, reported), and the behavioral round. Google's US engineering ads say that in most instances the role requires in-person interviews, and Google says initial interviews are often virtual before you come onsite.

07
Hiring decision
No candidate contact

Google says interviewers write structured feedback and that internal reviews follow, so a decision can take several weeks. Candidates and prep guides call this the hiring committee; reports in 2026 say it still sets hire and level from the written notes.

08
Team matching
Calls with hiring managers who have an opening, reported

Prep guides report short calls with managers after approval, taking from a few days to two months or more. In Europe the wait is often longer; see the Zurich guide.

09
Offer
From your recruiter

The recruiter walks you through pay and benefits. US ads post a base range for the role, plus a bonus target and equity.

03

Google behavioral interview: what it assesses and how to answer

From Google's own pages and candidate reports

Candidates, ex-Googlers and prep guides call this round Googleyness and Leadership, or G&L, and older guides say Google scores four attributes: general cognitive ability, role-related knowledge, leadership and Googleyness. Google's current careers pages use none of those names. What Google says today is that every candidate is assessed using clear rubrics, the same for everyone in the role, with open-ended questions and no brainteasers. Its re:Work guide, updated in March 2026, names three attributes to define for a structured interview: role-related knowledge, problem solving and leadership, and says Google documents what a poor, borderline, solid and outstanding answer covers. The round itself is reported to last about 45 minutes, with one question and several follow-ups at a time.

7 reported problemsSee them and how to solve themHide
  • What Google says it listens for: Google's tips page names the themes: how you handle ambiguity, how you grow outside your comfort zone, how you deal with conflict and influence teammates, how you drive collaboration, and your leadership style, including times you were not the official leader. Prepare at least one story for each.
  • Expect follow-ups after every answer: re:Work says Google's questions have an initial prompt and predetermined follow-ups, such as what your primary goal was, how teammates responded and what your plan is now. Keep the first answer to about two minutes so there is time for them, and know the details of each story well enough to go deeper.
  • Behavioral and hypothetical questions: Behavioral questions ask what you did ("Tell me about a time..."). Hypothetical ones ask what you would do ("Imagine you..."). For a hypothetical, clarify first, say your assumptions out loud and explain each call. Google says it is looking at your thought process more than one right answer.
  • Use Google's version of STAR: Google's tips page spells it Situation, Task, Activity, Result, where Activity is the specific steps you took and the role you played. Spend most of your time on the Activity, and say "I" for your own part.
  • Put a number on the result: Google suggests the form "Accomplished X, as measured by Y, by doing Z". Find a measure for every story before the interview, such as time saved, users reached or errors removed.
  • The technical design conversation: Business Insider reported in May 2026 that the round now includes a technical design conversation about your own past work, under a pilot for some US software engineering roles. Prepare one project you can explain end to end: the options you weighed, why you chose yours and what you would change.
  • Build a library of stories: Google advises cross-referencing your resume with the job description and building a library of examples where they overlap. Six to eight stories, each usable for two or three themes, cover most questions. Do not use AI during the interview: Google's pages say it is not permitted.

Calibrd's practice scores your spoken answer to each behavioral question above on three criteria taken from what Google says it listens for, so you can rehearse the follow-ups out loud before the real round.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Google.

Predict my Google questions →
04

Google system design interview: the round, the levels and the prompts

Candidate reports, 2024 to 2026

The Google system design interview is a round of 45 to 60 minutes where you design a large system out loud without writing code, and candidates in 2024 to 2026 report it from L5 up: one round at L5, two at L6 and staff, and none in most US L4 loops. Google publishes no length, level or rubric for it. The only design-specific advice on its careers pages is a 2019 video it still links, which covers communication, designing to scale, and trade-offs and compromises. Virtual rounds run in a Google Doc, and 2026 candidates with an in-person onsite report a whiteboard. No prompt below was reported twice, so treat them as the kind of problem Google sets.

7 reported promptsSee them and how to take themHide
  • Which levels get it: L4: in August 2026 one candidate asked the recruiter directly and was told there was no system design round, and several others confirmed two coding rounds and no design. L5: one round, now in the in-person part of US loops next to two coding rounds. L6 and staff: two design rounds. Android, machine learning, embedded and security roles get their own version of the round. Ask your recruiter which one you have.
  • Prompts built on Google's own products: Reported prompts: design Google Sheets (L5, 2024), Google Photos (staff, 2024), a TikTok-style Google News (L5, 2024), and "Hey Google" on several devices without duplicate answers (2025). Find the hard core of the product before drawing anything: concurrent edits and recalculation for Sheets, storage and search for Photos, ranking and freshness for News, and which device answers for the assistant.
  • News and content from many sources: Three separate candidates had a variant: an event scraper with search and booking (L5, 2024), the News feed above, and a news summary app where the follow-up was how to avoid duplicate summaries of the same story from different sources (L5, 2025). Prepare how you would detect the same item arriving from several places, and what you store to do it.
  • Real-time streams: A staff candidate in 2024 designed a trend finder on live tweets, and an L5 candidate a service that indexes a Twitter feed. Say how events come in, how you count over a time window, and what you keep in memory versus on disk, with numbers.
  • Sync and conflicts across devices: Android candidates report a to-do app synced across devices, with follow-ups on cancellation and conflicting updates, and an app controlling a light over a bad network. Decide what happens when two devices change the same thing offline, and say it before you are asked.
  • Estimate first, then expect changes: An L6 candidate in 2025 reported a lot of focus on resource estimates and the ability to scale. Others had the problem changed halfway through and had to redesign, or were told to expect the interviewer to challenge the whole approach. Do the rough numbers out loud, keep the first design simple enough to change, and explain each decision as you make it.
  • What decides the outcome: Two candidates were rejected after the design round, one at L5 and one at staff, without a stated reason. In three reported loops the design round was rated Hire or Strong Hire and the candidate was still levelled at L4 because of coding. At L5 and above, prepare design and coding with equal care.

Prep lists often name Google Docs, Maps, Drive, YouTube or a URL shortener as Google's design questions. We found no first-hand report of any of them in 2024 to 2026, which does not mean they are never asked; prepare the patterns above and expect the prompt to be new.

05

What Google screens for

Google's interview tips page lists what to prepare for the conversations that are not about code, and its re:Work guide, updated in March 2026, names the attributes Google suggests every structured interview should test. Together they describe the behavioral round better than any prep guide:

  • Navigating ambiguity: how you decide and act when you cannot see the whole picture, and how you push yourself outside your comfort zone
  • Working with people and teams: how you handle a conflict, influence teammates and drive collaboration across teams
  • Leadership at every level: mobilising others with your communication and decisions, including helping a team succeed when you were not the official leader
  • Impact shown with data: Google suggests the form "Accomplished X, as measured by Y, by doing Z"
  • Thinking out loud: asking to clarify, naming your assumptions and explaining your calls, because Google says the interviewer is looking at your thought process
06

Google interview questions

Candidate-reported themes

Google says its behavioral questions ask for specific examples, and its hypothetical questions ask what you would do in a new situation. These are our own practice questions, built on the themes Google's tips page and re:Work guide name. Candidates report questions in the same shape.

Rehearse these out loud for Google. Free to try.

See what's included →

Behavioural & motivation

  • Why Google, and why this team?
    Cal

    I'm Cal, your AI coach. Say whatever comes to mind: I'll put your answer in order, show what's missing, then score it.

    Scored on Specificity · Connection · Research
    • Your answer is scored on
    • SpecificityNames at least two concrete things about this company or role that could not be copy-pasted to a competitor.
    • ConnectionTies those specifics to their own goals or experience, so it reads as fit rather than flattery.
    • ResearchShows they actually looked: a product, a technical choice, a public post. Generic praise for culture or mission does not count.
    See how a strong answer sounds

    Example · not your answer

    “You're the only team I've found that publishes incident reviews with the real timeline in them, and I've read four now. I've worked somewhere that treated postmortems as a ritual you get through, and I'd rather not do that again.”

    Strong. One row still open.

    • SpecificityOne, not twoThe incident reviews are the only specific here. The rest could be said to any company.
    • ConnectionJoined upTies the observation to how they want to work, not just to admiration.
    • ResearchLooked properlyRead four of them. That is looking, not skimming an About page.

    That comes back in about ten seconds, with what worked, what to fix, and what the question was really after.

    We never store your recording or your answer. How this is handled ↗

  • Tell me about a time you had to make a decision without the full picture. What did you do when new information arrived?
  • Tell me about a time you disagreed with a teammate about how to do something. How was it resolved?
  • Tell me about a time you helped a team succeed when you were not the official leader.
  • Tell me about the achievement you are proudest of, and how you know it made a difference.
  • Tell me about a time you pushed yourself well outside your comfort zone.
  • Walk me through a technical design decision on a past project. What were the options, why did you choose yours, and what would you change now?
  • Imagine your team's launch date is fixed, and two weeks before it a partner team tells you their piece will be late. What do you do?

How to stop rambling in your answers

Technical

  • Practice: given a list of meeting time ranges, return the minimum number of rooms needed so no two meetings overlap. Talk through your approach and the complexity.Coding, phone screen and loop: Candidates report medium to hard algorithm problems on arrays, strings, graphs, trees and dynamic programming, written in a shared editor while you talk. Practice question in that style.Listening for: Clarifies the problem · Efficient approach · Complexity unprompted
  • Practice: design the backend for a photo sharing app's feed that serves hundreds of millions of users.System design, L5 and up: Reported as one round at L5 and two at L6 and staff; most US L4 loops in 2025 and 2026 had none. A service at Google scale, with trade-offs said early. Practice question in that style.Listening for: Requirements first · Storage, fan-out, cache · Trade-offs named early
  • Practice: you are handed a 2,000-line service you have never seen, and a test is failing after a recent change. Explain how you would find and fix the bug, and how you would check any code an AI assistant suggests.Code comprehension with AI, pilot: Business Insider reported in May 2026 that Google is piloting a round for junior and mid-level roles on select US teams where you work through an existing codebase with Gemini as an approved assistant, scored on AI fluency, including validating output and debugging. Google's hiring page still says AI tools are not permitted in interviews, so use AI only if your recruiter says the round includes it. Practice question in that style.Listening for: Finds the way in · Checks the AI's output · Proves the fix
  • Practice: usage of a Google product you know drops 10% in one country over a month. How would you find out why, and what would you recommend?Product sense, PM roles: Google's re:Work guide uses a competitor pricing change as its own example of a hypothetical interview question. Our practice question in the same style.Listening for: Clear structure · Uses data to narrow it · Recommends and measures
Your Google interview

Don’t walk in hoping. Walk in rehearsed.

Calibrd predicts the questions Google is likely to ask for your role, interviews you out loud, and tells you what a hiring manager would hear.

Free · talk any answer through

Ready to go all in? for 90 days · or Unlimited graded answers and 45 mock interviews · no subscription ·
Built by Xiaochen Guo, 500+ interviews on the hiring side

How the questions are predicted

07

Pay

L3 · Software Engineer IINo current US ad posted; ≈ $218K total a year reported on Levels.fyi
L4 · Software Engineer III$147,000 to $210,000 base posted, plus 15% bonus target and equity; ≈ $312K total reported
L5 · Senior Software Engineer$174,000 to $252,000 base posted, plus 15% bonus target and equity; ≈ $444K total reported
L6 · Staff Software Engineer$207,000 to $300,000 base posted, plus 20% bonus target and equity; ≈ $756K total reported
L7 · Senior Staff Software Engineer$262,000 to $364,000 base posted, plus 25% bonus target and equity
Associate Product Manager, new grad$116,000 to $165,000 base posted, plus 15% bonus target and equity
Product Manager II$163,000 to $236,000 base posted, plus 15% bonus target and equity
Senior Product Manager$192,000 to $278,000 base posted, plus 20% bonus target and equity

Posted ranges are US base salary from Google job ads read on 5 October 2026, published where pay transparency laws require them. Google says individual pay depends on job-related skills, experience and education. The ads name the title; the L3 to L7 labels are how Levels.fyi and candidates map those titles. Reported totals are Levels.fyi's US averages for software engineers by level, given there as monthly figures and multiplied by twelve here, so treat them as estimates; at L5 and above, stock is a large part of the total. Calibrd benchmarks the offer against your level and location in the report.

Applying to Google? Paste the posting and see whether they’d shortlist you →

Already receiving LinkedIn alerts for Google? Forward them to your own Calibrd address. Calibrd reads each job against your resume and keeps only the ones you could be shortlisted for, so you apply where your odds are best. Set it up.

08

How to prepare for a Google interview

  1. Read Google's own hiring and interview tips pages first. They describe the behavioral round in more detail than most prep guides.
  2. Write six to eight stories that cover ambiguity, conflict, leading without a title, growth, collaboration and a result you can measure, and say each one aloud in about two minutes.
  3. Give every story a number, in Google's form: accomplished X, as measured by Y, by doing Z.
  4. Practise follow-ups: after each story, answer what your goal was, how others responded and what you would do differently.
  5. Prepare one past project you can explain as a design conversation: the options, the trade-offs, your part and what you would change.
  6. For hypothetical questions, clarify first and say your assumptions out loud. Google says it is looking at your thought process.
  7. New grads and interns: practise two timed algorithm problems in 90 minutes, since that is the coding test candidates report.
  8. Engineers: practise coding aloud in a plain shared editor with complexity stated, and system design from L5.
  9. Ask your recruiter which rounds are in person, and whether any round allows an AI assistant. Assume no AI unless they say so.
  10. If Google sends the Hiring Assessment, read our guide to it before you start.

This guide covers Google's hiring in general, with US pay. What Google publishes is quoted from its careers pages, re:Work and job ads; the round names, counts, the coding test and the 2026 pilot come from news reports and candidate accounts, and are marked as reported. Your recruiter's description of your loop is the final word. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Amazon, Microsoft or Meta? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Google mock: spoken answers, coached on the spot. Your first mock is free.

Run a Google mock →
09

FAQ & sources

What is Google's interview process?

Google says the process can differ by role and team, and typically takes 6 to 8 weeks once interviews for a role begin. The stages, in order: Application; Google Hiring Assessment; Coding online assessment; Recruiter conversations; Technical phone screen; Interview loop; Hiring decision; Team matching; Offer.

What does Google look for in candidates?

Google's interview tips page lists what to prepare for the conversations that are not about code, and its re:Work guide, updated in March 2026, names the attributes Google suggests every structured interview should test. Navigating ambiguity; Working with people and teams; Leadership at every level; Impact shown with data.

What questions does Google ask in interviews?

Google says its behavioral questions ask for specific examples, and its hypothetical questions ask what you would do in a new situation. Technical themes: Coding, phone screen and loop; System design, L5 and up; Code comprehension with AI, pilot; Product sense, PM roles.

What does Google assess in the behavioral interview?

Candidates, ex-Googlers and prep guides call this round Googleyness and Leadership, or G&L, and older guides say Google scores four attributes: general cognitive ability, role-related knowledge, leadership and Googleyness. Google's current careers pages use none of those names. Covered on this page: What Google says it listens for; Expect follow-ups after every answer; Behavioral and hypothetical questions; Use Google's version of STAR; Put a number on the result; The technical design conversation; Build a library of stories.

What is the Google system design interview?

The Google system design interview is a round of 45 to 60 minutes where you design a large system out loud without writing code, and candidates in 2024 to 2026 report it from L5 up: one round at L5, two at L6 and staff, and none in most US L4 loops. Google publishes no length, level or rubric for it. Covered on this page: Which levels get it; Prompts built on Google's own products; News and content from many sources; Real-time streams; Sync and conflicts across devices; Estimate first, then expect changes; What decides the outcome.

How much does Google pay?

L3 · Software Engineer II: No current US ad posted; ≈ $218K total a year reported on Levels.fyi; L4 · Software Engineer III: $147,000 to $210,000 base posted, plus 15% bonus target and equity; ≈ $312K total reported; L5 · Senior Software Engineer: $174,000 to $252,000 base posted, plus 15% bonus target and equity; ≈ $444K total reported; L6 · Staff Software Engineer: $207,000 to $300,000 base posted, plus 20% bonus target and equity; ≈ $756K total reported. Posted ranges are US base salary from Google job ads read on 5 October 2026, published where pay transparency laws require them.

How do I get a job at Google?

Google hires software engineers from new graduates to Senior Staff, site reliability engineers, product managers from Associate Product Manager up, technical program managers (289 US openings on 13 October 2026, many on AI and DeepMind programs), and a large number of people in Cloud, sales, design and research. In the US, current engineering ads list roles on Search, YouTube, Google Cloud, Photos, Android and the AI teams, in Mountain View, Sunnyvale, San Jose, New York, Seattle, Kirkland and other offices. Hiring runs in 9 stages, starting with Application.

How do I get job alerts for Google jobs?

Already receiving LinkedIn alerts for Google? Forward them to your own address in Calibrd's Job search. Calibrd reads only what arrives there, nothing else in your mail. Each job in them is checked against your CV in your next search, and you see only the ones you could be shortlisted for. Not receiving any yet? Set one up for Google on LinkedIn first.

How do I prepare for a Google interview?

Read Google's own hiring and interview tips pages first. They describe the behavioral round in more detail than most prep guides. Write six to eight stories that cover ambiguity, conflict, leading without a title, growth, collaboration and a result you can measure, and say each one aloud in about two minutes.

Prep for a real Google role

Practise your Google interview, out loud.

Paste a real Google posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your resume — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Google prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Google Interview Process: Behavioral Questions — Calibrd