Google interview, from the behavioral round to the offer.

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.

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.

• 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 CV 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.

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

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.

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.

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 L4.
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 Netflix, Google Zurich or Meta London? Their guides follow the same format, from the first screen to the offer.

• 01Google Careers, our hiring processthe Hiring Assessment and coding exercise, recruiter conversations, project work, the interview panel over video or in person, clear rubrics, open-ended questions, no brainteasers, no AI tools in interviews, 6 to 8 weeks, three applications in 30 days and the one-year wait to reapply, read 5 October 2026.
• 02Google Careers, interview tips"Tell me about a time when..." questions, the data formula, Google's STAR (Situation, Task, Activity, Result), ambiguity, conflict, leadership without a title, reintroduced in-person interviews for some roles, and structured feedback with internal reviews, read 5 October 2026.
• 03Google re:Work, a guide to structured interviewing (updated March 2026)role-related knowledge, problem solving and leadership, emergent leadership for individual contributors, behavioral and hypothetical questions with follow-ups, and poor to outstanding rubrics, read 5 October 2026.
• 04Google job ad, Software Engineer III, Mobile, iOSUS base $147,000 to $210,000 plus 15% bonus target and equity, two years of experience, in-person interviews in most instances, read 5 October 2026.
• 05Google job ad, Senior Software Engineer, Platforms Infrastructure EngineeringUS base $174,000 to $252,000 plus 15% bonus target and equity, five years of experience, read 5 October 2026.
• 06Google job ad, Staff Software Engineer, Google Cloud ComputeUS base $207,000 to $300,000 plus 20% bonus target and equity, eight years of experience, read 5 October 2026.
• 07Google job ad, Senior Staff Software Engineer, Search PlatformsUS base $262,000 to $364,000 plus 25% bonus target and equity, read 5 October 2026.
• 08Google job ad, Associate Product Manager, University Graduate, 2027 StartUS base $116,000 to $165,000 plus 15% bonus target and equity, transcript required, read 5 October 2026.
• 09Google job ad, Product Manager II, YouTube AdsUS base $163,000 to $236,000 plus 15% bonus target and equity, read 5 October 2026.
• 10Google job ad, Senior Product Manager, Agentic SystemsUS base $192,000 to $278,000 plus 20% bonus target and equity, read 5 October 2026.
• 11Business Insider, Google plans to let software engineers use AI in job interviews (7 May 2026)reported from an internal document: the AI-assisted code comprehension pilot, the technical design conversation in the Googleyness and Leadership round, and an open-ended round for junior candidates; details read through the coverage below.
• 12Entrepreneur, Google is testing a new interview rule (8 May 2026)the pilot for junior and mid-level US roles, Gemini as the assistant, AI fluency scoring, and the statement from Google's VP of Recruiting, read 5 October 2026.
• 13HRD, Google opts for in-person interviews (12 August 2025)Sundar Pichai on adding at least one in-person round for engineering roles, read 5 October 2026.
• 14Levelop, Google coding interviews in 2026 (20 May 2026)reported: the design conversation added to the Googleyness and Leadership round, and a hiring committee process that has not changed.
• 15TechScreen, Google interview process 2026 (1 September 2026)reported: round lengths, the online assessment of two problems in 60 to 90 minutes for new grads and interns, what the Googleyness and Leadership round covers, the hiring committee and team match timing.
• 16Reddit r/csMajors, Google SWE intern (North America) OA questions (about January 2025)reported: two questions, one easier and one harder, with 90 minutes; read from the Google result snippet because the page would not load for us.
• 17Reddit r/csMajors, advice for the Google Early Career (US) SWE online assessment (about August 2024)reported: a 90-minute coding assessment with two questions plus a behavioral fit assessment; read from the Google result snippet.
• 18Levels.fyi, Google software engineer pay, United Statesreported: the L3 to L6 averages with base, stock and bonus, the title mapping (L3 SWE II to L6 Staff SWE) and the 38/32/20/10 vesting schedule, last updated 5 October 2026.

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.