Company questionsGroundworkGoogle

Global · interview process

Google

Google runs a recruiter call, one live coding phone screen, a block of 45-minute onsite interviews (mostly algorithms plus a behavioural 'Googleyness' round), then a hiring committee and team matching before any offer. System design shows up from L5 upwards.

  • 8 rounds
  • Sources give about 4-8 weeks as typical (the oldest says 4-6, a 2026 guide says 6-8, another about 2 months). Reports range from about 3 weeks to several months, mostly because of team matching; one guide claims three months to over a year.
  • 3 design answers
  • 3 coding answers
  • 6 well-reported rounds
Start with round 1 Browse every question
  1. Screen
  2. OA
  3. Screen
  4. DSA
  5. System design
  6. Behavioural
  7. Manager
  8. HR
  9. People rounds

The process, round by round

Reported by candidates and, where we found one, the company itself. Each round shows how well it is reported. Processes change by team, level and year.

  1. Recruiter screen

    Recruiter or phone screenabout 30 min

    Prep guides

    A non-technical call covering your background, work authorisation, target level, location and team preferences, motivation, salary expectations and timeline. Guides say the recruiter's notes are shared with the interview panel.

    • role and level fit
    • motivation
    • logistics
    What can be asked in a recruiter or phone screen round

    A short call that decides whether you move on. Part resume and motivation, sometimes one easy coding or fundamentals question in a shared editor.

    • Walk me through your resume and your best project

      Give a two minute spine, not a life story: who you are now, the one or two projects that matter most, and why this role is the next step. Pick the best project and state the problem, your part, the technology and one measurable result. Keep every claim something you can defend if the next question digs in. You could open with: I am a backend engineer, and the project I am proudest of is the one where I cut checkout latency.

      Screening call chapter →
    • Why this company and why now

      The listener wants to know whether your reason is specific and sincere, not flattery. Name one or two real things about the product, the engineering problems or the team that you have looked at, then connect them to something you have done or want to learn. Why now should be about your growth, not escaping your current job. An opening could be: I have used the product, and the scaling problem it describes is the kind I want to work on.

      Screening call chapter →
    • Notice period, location and compensation expectations

      Give the facts that are true and keep the negotiation for later. State your notice period exactly as your contract says, and mention whether it can be shortened or bought out only if that is real. For compensation, say you would like to understand the role and level first, or give a researched range rather than a single anchor. Never invent a current figure. If you are asked directly, answer honestly and calmly.

      HR and the number chapter →
    • One easy or medium coding question, or a language fundamentals question

      Treat it as a short version of the full coding round. Repeat the problem back, ask about input size and edge cases, state a plan before typing, and talk while you code. For a language question, such as what a closure is or how a hash map handles collisions, give a one line definition and a tiny example. A good line is: first I will do the simple approach so we have something correct, then improve it.

      Tech phone screen chapter →

    Prepare with: Book · Screening callBook · Tech phone screen

    3 sources for this round

  2. Google Hiring Assessment (GHA)

    Online assessment30-45 min (one guide)

    Prep guides

    An online questionnaire of scenario and agree/disagree items about work style. Guides disagree on its length (roughly 50 versus 100 items) and on who takes it. One says failing it blocks reapplying for six months.

    • work-style consistency
    • judgement in scenarios
    • consistency of answers

    Varies: One guide calls it mandatory after applying; another says only some candidates get it (referrals and hiring-manager outreach) and that hiring-manager outreach may skip it.

    What can be asked in a online assessment round

    A timed test on a coding platform, taken alone. Usually two or three coding problems, sometimes with multiple-choice questions on CS basics, aptitude or SQL.

    • Array and string problems that need a hash map, two pointers or a sliding window

      Read the constraints first, because they point to the technique. If n is 100,000, an O(n^2) scan will time out, so look for a hash map, two pointers on a sorted array, or a window that moves forward only. Sketch the brute force, find the repeated work, then remove it. For two-sum style pairs you might say: I store each value's index as I scan, so the complement lookup is O(1) and the whole pass is O(n).

      DSA course →
    • Greedy and sorting problems with a catch in the constraints

      Greedy problems hide behind a sort. Ask what ordering makes the locally best choice safe, then try to argue why swapping two adjacent choices never helps. Interval scheduling is the classic case: sort by end time and take every interval that starts after the last chosen one. Check the catch in the constraints, such as overflow, ties or equal values, and test a tiny case by hand before submitting.

      DSA course →
    • A medium dynamic programming or graph-on-a-grid problem

      Decide whether the problem is a graph walk or a recurrence. On a grid, a shortest path with equal step cost is breadth-first search from the start, with a visited set so each cell is processed once, giving O(rows x cols). For dynamic programming, define the state in one sentence, write the transition, set the base cases, then see if only the previous row is needed to save space.

      DSA course →
    • SQL queries with joins and group by

      Start from the table that holds the thing being counted, join the others on their keys, filter rows with WHERE, group, then filter groups with HAVING. Remember that WHERE runs before grouping and HAVING after. Use LEFT JOIN when rows with no match must still appear, and COUNT of a column rather than star when nulls matter. Example: customers with more than three orders is GROUP BY customer_id HAVING COUNT(*) > 3.

      Databases →
    • Multiple-choice questions on OOP, operating systems, databases and networks

      These reward quick, accurate recall rather than long reasoning, so revise the short list of definitions that recur. Know the difference between a process and a thread, the four ACID properties, what an index trades for faster reads, TCP against UDP, and the four pillars of OOP. Eliminate two wrong options first, then choose. Do not spend more than a minute on any single question, and flag it to return to if time remains.

      Mock interviews →

    Prepare with: Book · Online assessmentDSA course

    2 sources for this round

  3. Technical phone screen

    Recruiter or phone screen45 min in the oldest source and one 2025 report; two 2026 guides say 45-60 min

    Several reports

    A live call with an engineer, coding in a shared document with no way to run code. Sources give one problem (the oldest source and a 2025 report) or one to two medium problems (two guides). The oldest source leaves roughly the last five minutes for your questions. The interviewer's rating feeds your packet.

    • data structures and algorithms
    • coding without an IDE
    • explaining your approach aloud

    Varies: One guide says a second screen is used only if the first is borderline.

    What can be asked in a recruiter or phone screen round

    A short call that decides whether you move on. Part resume and motivation, sometimes one easy coding or fundamentals question in a shared editor.

    • Walk me through your resume and your best project

      Give a two minute spine, not a life story: who you are now, the one or two projects that matter most, and why this role is the next step. Pick the best project and state the problem, your part, the technology and one measurable result. Keep every claim something you can defend if the next question digs in. You could open with: I am a backend engineer, and the project I am proudest of is the one where I cut checkout latency.

      Screening call chapter →
    • Why this company and why now

      The listener wants to know whether your reason is specific and sincere, not flattery. Name one or two real things about the product, the engineering problems or the team that you have looked at, then connect them to something you have done or want to learn. Why now should be about your growth, not escaping your current job. An opening could be: I have used the product, and the scaling problem it describes is the kind I want to work on.

      Screening call chapter →
    • Notice period, location and compensation expectations

      Give the facts that are true and keep the negotiation for later. State your notice period exactly as your contract says, and mention whether it can be shortened or bought out only if that is real. For compensation, say you would like to understand the role and level first, or give a researched range rather than a single anchor. Never invent a current figure. If you are asked directly, answer honestly and calmly.

      HR and the number chapter →
    • One easy or medium coding question, or a language fundamentals question

      Treat it as a short version of the full coding round. Repeat the problem back, ask about input size and edge cases, state a plan before typing, and talk while you code. For a language question, such as what a closure is or how a hash map handles collisions, give a one line definition and a tiny example. A good line is: first I will do the simple approach so we have something correct, then improve it.

      Tech phone screen chapter →

    Prepare with: Book · Screening callBook · Tech phone screen

    4 sources for this round

  4. Onsite coding rounds

    Data structures and algorithms45 min each

    Several reports

    Two to four rounds of algorithm and data-structure problems. Sources disagree on how many problems fit a round: the oldest says usually two per interview, a 2026 guide says typically one challenging one. Trees, graphs, arrays and dynamic programming appear in candidate reports. Some loops are virtual, some in person.

    • algorithms and data structures
    • clean working code
    • handling follow-ups and edge cases
    • time management

    Varies: L3/L4 loops are coding-heavy; the oldest source says four coding rounds at L3/L4 and three at L5+, while a 2026 guide says two to three onsite coding rounds at L4. One 2026 guide also describes a pilot on select US teams for junior and mid-level roles that adds a code-comprehension round (read and debug existing code, an AI assistant allowed).

    Practise for this round

    What can be asked in a data structures and algorithms round

    A live coding round of 45 to 60 minutes with one or two problems. You are judged on how you clarify, reason, code, test and state the complexity, not on the answer alone.

    • Arrays, strings and hashing: pairs, windows, frequency counts, prefix sums

      Name the pattern from the shape of the question. Pairs with a target use a hash map of seen values. A contiguous range with a condition uses a sliding window that grows on the right and shrinks on the left, so each element enters and leaves once, giving O(n). Range sums over many queries use a prefix sum array so each query is O(1) after O(n) setup. Count characters with a fixed-size array or map.

      DSA course →
    • Linked lists, stacks and queues, including design-a-structure problems such as an LRU cache

      For an LRU cache, combine a hash map from key to node with a doubly linked list ordered by recency. Get moves the node to the front, put inserts at the front, and when over capacity you remove the tail node and its map entry. Both operations are O(1), and you say why: the map finds the node, the list reorders it without a scan. For stacks, mention a monotonic stack for next greater element.

      DSA course →
    • Trees and BSTs, graphs (BFS, DFS, topological sort, shortest paths) and grids

      Decide the traversal from what is asked. Level by level or shortest path in an unweighted graph is BFS with a queue. Exploring all paths, components or cycles is DFS. A dependency order is topological sort: Kahn's algorithm repeatedly removes nodes with in-degree zero, and leftover nodes mean a cycle. Weighted shortest path with non-negative edges is Dijkstra with a heap, O((V + E) log V). On a BST, an in-order walk is sorted.

      DSA course →
    • Heaps and top-K, intervals, binary search on the answer

      For the K largest items keep a min-heap of size K: push each element and pop the smallest when the heap exceeds K, so the cost is O(n log K) and memory is O(K). For intervals, sort by start, then merge by comparing the next start with the current end. For binary search on the answer, define a yes or no check that is monotonic, such as can ship within D days, and search the capacity range.

      DSA course →
    • Dynamic programming from one dimension up to knapsack and string DP

      Define the state in a sentence, write the recurrence, fix the base cases, and decide the order of filling. Start with the recursive version with memoisation, then convert to a table. For 0/1 knapsack, dp[w] is the best value at capacity w, and in the one dimensional form you loop capacity downward so each item is used once. For string problems such as edit distance, the state is a pair of prefix lengths.

      DSA course →
    • Follow-ups: optimise space, handle streaming input, make it thread-safe

      Treat follow-ups as a chance to show depth, and answer in the same calm order each time. To save space, ask which previous rows or values the recurrence actually reads and keep only those. For streaming input, say what summary you can keep, such as a heap of size K or a running count. For thread safety, name the shared state, guard it with a lock, and keep the critical section short.

    Prepare with: Book · DSA roundDSA course

    4 sources for this round

  5. System design

    System design45 min

    Several reports

    A design discussion. The one concrete example in the sources is a 2025 candidate asked to design a URL shortener, covering hashing, schema, caching and high read throughput. Sources agree it belongs to the senior (L5 and up) loop.

    • scalable design
    • trade-off reasoning
    • database and caching choices
    • communication

    Varies: Normally from L5 upwards; the oldest source and a 2026 guide say L3/L4 loops have no dedicated design round (another guide says design ideas may surface inside L4 coding rounds), though one 2025 SDE-2 candidate (4 years experience) still got one.

    Practise for this round

    What can be asked in a system design round

    A 45 to 60 minute discussion of how to build a system at scale: requirements, numbers, APIs, data model, components, bottlenecks and trade-offs.

    • Short links, chat, news feed, notifications, search, rate limiting

      Use one repeatable path: clarify scope and scale, estimate load, define the API, sketch the data model, draw the main components, then probe bottlenecks. For short links, store a mapping from a generated short id to the long url, generate ids with a counter encoded in base 62, cache hot links, and note reads far outnumber writes. For chat, mention persistent connections and a store ordered per conversation.

      System design course →
    • Payments, wallets and ledgers where money must never be lost or doubled

      Money systems put correctness before speed. Use a double-entry ledger where entries are append-only and every transfer writes a debit and an equal credit in one transaction. Protect against doubled charges with an idempotency key stored with the result, so a retry returns the original outcome. For lost updates use a database transaction, and reconcile with the payment provider's records on a schedule.

      System design course →
    • Ride matching, maps and anything with live location

      Split the problem into location ingestion, a geospatial index and matching. Drivers send updates every few seconds to a write-optimised store, often in memory, keyed by a grid cell such as a geohash or S2 cell. To find nearby drivers, query the rider's cell and its neighbours, then rank by distance and estimated time. Say how you handle a stale location and a driver who accepts two rides.

      System design course →
    • File storage and sync, video streaming and content delivery

      For file sync, split files into chunks, hash each chunk and upload only chunks the server lacks, so a small edit transfers a small amount. Keep metadata in a database and chunks in object storage. For video, upload the original, transcode into several resolutions, store segments and serve them through a content delivery network with adaptive bitrate streaming, so the player switches quality as bandwidth changes.

      System design course →
    • Fundamentals: caching, sharding, replication, queues, consistency, failure handling

      Treat each as a tool with a cost. A cache cuts read latency but adds staleness and invalidation. Sharding spreads write load but makes cross-shard queries hard. Replication gives availability and read scale but introduces lag. Queues smooth spikes and decouple services but require idempotent consumers. For failures, name timeouts, retries with backoff and a fallback. State what you give up whenever you choose.

      System design course →
    • Back-of-envelope estimates and what they decide

      Estimates are there to choose a design, so finish each one with a decision. Use round numbers: a day has about 100,000 seconds, so 10 million requests a day is roughly 100 per second on average, with a peak of a few times that. Multiply object size by count for storage, and compare against one machine's capacity. If one database handles the load, say so and avoid sharding.

      Capacity estimation →

    Prepare with: Book · System designSystem design course

    3 sources for this round

  6. Googleyness and leadership

    Behavioural round30-45 min

    Several reports

    Behavioural questions mixing past experiences and hypothetical scenarios. Reports mention disagreeing with colleagues, deciding with incomplete information, mentoring, unclear or changing requirements and going above and beyond.

    • collaboration
    • comfort with ambiguity
    • valuing feedback
    • user focus

    Varies: One 2026 guide says that at L4 it looks at teamwork and growth potential rather than demonstrated leadership.

    Practise for this round

    What can be asked in a behavioural round round

    Story-based questions about how you work. Prepare a few real stories you can reshape: the situation, your action and the result, with numbers where you have them.

    • A conflict, a failure, a deadline you missed and what you changed

      Use situation, task, action and result, spending most of the time on what you did. For a failure, own your part, say what you learned and show a concrete change that you kept, such as a checklist or a test. For a conflict, show you listened and focused on the goal. The listener checks honesty and growth. Start plainly: the situation was a release that slipped, and my part in it was an estimate I did not revisit.

      Behavioural chapter →
    • Leading without authority, mentoring, raising a hard issue

      The theme is influence without a title. Pick a real example where you persuaded others, taught a teammate or raised a risk early. Describe how you built agreement, with data, a small proof or a one page proposal, and what changed afterwards. Raising a hard issue means doing it early, privately where fitting, and with a suggested fix. Do not present someone else's work as your own.

      Behavioural chapter →
    • Ambiguity: a time you had to decide with little information

      Interviewers check how you decide when facts are missing. Describe how you reduced the unknowns: asked who could answer, ran a small experiment, chose the reversible option, and set a point to review. Explain what you decided, what risk you accepted, and the outcome, including if it turned out wrong. A fitting opening: nobody could tell us the real traffic, so I proposed a two week trial before committing.

      Behavioural chapter →
    • Customer or user focus, and an example of going beyond the brief

      Show that you understand who uses the work. Pick a real example where you looked at user feedback, support tickets or usage data and changed what you built, even when the ticket asked for something narrower. Describe the extra step you took, why it mattered to the user, and the result. The listener checks initiative and that it is grounded in evidence, not just effort.

      Leadership principles chapter →

    Prepare with: Book · BehaviouralBook · Leadership Principles

    4 sources for this round

  7. Hiring committee and team matching

    Hiring managerfit calls of 30-45 min (oldest source)

    Several reports

    Your interview feedback is bundled into a packet for a committee that makes the hire decision and may offer a lower level. Separately, hiring managers hold fit calls with you. Passing the interviews does not guarantee a team: one 2026 candidate who said they passed was still waiting on team matching months later.

    • packet strength across interviews
    • mutual fit with a team
    • level decision

    Varies: Order varies: some sources say matching comes before the committee, others after; EU offices reportedly match first.

    Practise for this round

    What can be asked in a hiring manager round

    A conversation about your past work and how you would fit the team: depth on projects, ownership, decisions and trade-offs, sometimes a design problem.

    • Pick a project and go deep: why this design, what broke, what you would change

      Choose a project you can discuss at every layer. Explain the problem and who it served, the options you considered, why you chose one, what broke and what you would change now. Be clear which parts you did and which the team did. Admitting a flaw earns trust. Opening line: the main constraint was latency, so I chose a cache in front of the database, and I would now add an invalidation strategy.

      Resume grilling chapter →
    • A time you disagreed with a teammate or pushed back on a decision

      Use situation, task, action, result, and keep the disagreement about the work, never the person. The listener is checking that you can hold a view with evidence, listen, and commit once the decision is made. Describe what you proposed, the data or reasoning you used, how you reached agreement or accepted the other path, and what happened. Do not invent a story: use a real one, even a small one.

      Behavioural chapter →
    • How you prioritise when everything is urgent

      Show a method rather than a claim of being busy. Describe how you judge impact and deadline, ask who needs the result and when, and say no or renegotiate scope early when two things clash. Mention communicating the trade-off to stakeholders so nobody is surprised. A sentence you could adapt: I list what is blocking others first, then what has a fixed date, then what moves a metric.

      Behavioural chapter →
    • What you want from the next role and the team

      Answer honestly and tie it to what the role offers. Say what you want to learn or own next, such as larger systems, more ownership of design, or mentoring, and what kind of team helps you do it. Then ask what the team is trying to achieve this year and how the work is reviewed. The listener checks that your wishes match the job and that you have thought about it.

    Prepare with: Book · Resume grillingBook · Behavioural

    3 sources for this round

  8. Offer

    HR and offer

    Several reports

    After a team is settled, a recruiter delivers the offer, with compensation set by level and location, and follows up in writing. One 2025 candidate got the decision about two weeks after the final interview.

    • compensation negotiation
    • level and location pay
    • offer timing

    Practise for this round

    What can be asked in a hr and offer round

    The closing conversation: motivation, expectations, notice period, compensation and how the offer is structured. Prepared answers and a clear number help here.

    • Current and expected compensation, and how to answer without boxing yourself in

      Be honest and avoid giving a single number too early. Share your current pay only if you are comfortable, and make clear what is fixed and what is variable. For expectations, say you are flexible for the right role, and offer a researched range based on level and market. If pushed, state a figure you can justify. Never state a number you cannot support, because offers are often checked.

      HR and the number chapter →
    • Notice period, joining date and relocation

      Give the facts exactly as they are in your contract. State the notice period, whether early release or a buy-out is truly possible, and the earliest honest joining date. Do not promise a date your employer has not agreed to. For relocation, say whether you can move, how soon, and whether you would need support. Clear, early information helps the recruiter plan and shows you are reliable.

      HR and the number chapter →
    • Why you are leaving and what you are looking for

      Keep it positive and forward looking. Talk about what you want more of, such as larger scale, ownership or a stronger team, rather than criticising your current employer. The listener checks that you will not leave this job for the same reason. Opening line: I have learned a lot in the current role, and I now want to work on problems at a bigger scale.

    • Levels, equity and how the offer is built

      Ask for the structure rather than only the total. Find out the level and title, base salary, bonus and whether it is guaranteed, equity amount, vesting schedule and cliff, joining bonus and any clawback. Compare offers on a yearly total with the same assumptions. If equity is in a private company, ask how it is valued and what happens on leaving. Asking calmly is normal and expected.

      Levels and equity chapter →

    Prepare with: Book · HR & the numberBook · Levels & equity

    3 sources for this round

Preparing for the people rounds at Google

The hiring manager, behavioural and offer conversations. Candidate reports shape the themes; the answers and frames are written for this site, so use them as a structure and bring your own stories.

What Google says it valuesOfficial ↗

  • Focus on the user and all else will followDesign around what the person using the product needs rather than internal goals, and keep ads separate from rankings.
  • It's best to do one thing really, really wellGo deep on a core strength, then carry what you learn into neighbouring products.
  • Fast is better than slowSpeed counts as a real improvement, so lean pages and efficient systems that answer quickly are worth the effort.
  • Democracy on the web worksUse the collective signal of many people, such as links, and back open source rather than a single authority.
  • You don't need to be at your desk to need an answerMake information reachable wherever people are, which is why mobile services and open platforms matter.
  • You can make money without doing evilEarn revenue while keeping ads relevant and clearly labelled, and never let payment influence rankings.
  • There's always more information out thereLook past the obvious data toward other formats and sources, such as books, patents and news archives.
  • The need for information crosses all bordersMake information accessible worldwide, including through many languages and translation tools.
  • You can be serious without a suitA casual, creative atmosphere can sit alongside demanding work, and ideas are tested quickly.
  • Great just isn't good enoughTreat great as the starting point and work out the need users have not yet voiced.

Themes candidates report being probed

  • Collaboration and disagreement
  • Comfort with ambiguity
  • Valuing feedback
  • User-first thinking
  • Learning from failure
  • Mentoring
  • Deciding with incomplete information

Questions to rehearse

  1. Tell me about a disagreement with a colleague and how it ended.Several reports

    What is being checked. Reported as a Googleyness-style prompt. The listener checks whether you can hold a position, use evidence, and still leave the other person willing to work with you.

    How to frame it. Pick a disagreement about a technical or product choice, not a personality clash. Say what each side wanted, what data or experiment settled it, and what you changed in how you work together afterwards. Opening to adapt: "On [project], [colleague] and I disagreed about [choice], so we agreed to test it by [method]."

    Worked example in the Interview book →Candidate write-up · 2025 ↗Prep guide ↗

  2. Describe a decision you had to make before you had all the information.One report

    What is being checked. Checks comfort with ambiguity and whether you can move without waiting for certainty, while still limiting the cost of being wrong.

    How to frame it. State what was missing, what you did to shrink the gap quickly, the assumption you wrote down, and how you would have noticed if it was wrong. Close with the outcome and what you would repeat. Opening to adapt: "We had to choose [option] before [data] was available, so I picked the choice that was easiest to reverse."

    Candidate write-up · 2025 ↗

  3. How have you helped a more junior engineer grow?One report

    What is being checked. Looks for evidence that you raise the people around you rather than only your own output, which matters for collaboration and level.

    How to frame it. Describe the gap you saw, what you did that was specific (pairing, review comments, a stretch task with a safety net), and the visible change in their work. Avoid framing it as rescuing them. Opening to adapt: "A newer teammate on [team] was struggling with [skill], so I started by [action]."

    Candidate write-up · 2025 ↗

  4. Tell me about a time the goal was unclear and you still had to make progress.Prep guides

    What is being checked. A guide lists ambiguity as a theme. The listener checks whether you create structure, ask the right questions, and avoid stalling.

    How to frame it. Show how you turned a vague goal into a first milestone: who you asked, what you proposed, and how you confirmed direction early. Mention what you dropped. Opening to adapt: "The request was [vague goal], so my first step was to write down what success would look like and check it with [stakeholder]."

    Prep guide ↗

  5. Tell me about a time you put the user ahead of other goals.Prep guides

    What is being checked. Ties to the focus-on-the-user idea on the company philosophy page. The listener wants to see that you can name a real user need and trade something off to protect it.

    How to frame it. Name the user, the evidence you had about their problem (support tickets, logs, a conversation), and what you gave up or delayed. Say how you knew the result helped. Opening to adapt: "Our metric said [x], but users were hitting [problem], so I argued for [change]."

    Prep guide ↗Official ↗

  6. What do you do to keep learning, and what did you learn from a recent mistake?Prep guides

    What is being checked. Checks the learning mindset and self-awareness about failure that guides list, and whether you can describe a mistake without blaming others.

    How to frame it. Give one concrete habit and one specific mistake: what you misjudged, what you changed in your process, and where the change has since helped. Keep the tone plain, not performative. Opening to adapt: "My most useful recent lesson was on [topic], where I got [thing] wrong because [reason]."

    Prep guide ↗

  7. A teammate keeps missing review deadlines and it is blocking you. What would you do?Prep guides

    What is being checked. A guide reports that hypothetical "how would you handle this" questions appear beside past-experience ones. The listener checks your default approach to friction.

    How to frame it. Describe the order of your steps: understand their constraints privately first, agree a small change, involve the lead only if it persists. Then link to a real time you used the same approach. Opening to adapt: "I would start by asking what is getting in their way, and I have done this before on [project]."

    Prep guide ↗

The offer conversation

  • A guide reports that the recruiter screen is where work authorisation, salary expectations and timeline are checked.
  • A guide says coding performance often decides whether you land at L4 or are down-levelled to L3. Two guides disagree on whether team matching comes before or after the hiring committee, so ask the recruiter how it works for your case.
  • One January 2025 Bangalore SDE-2 candidate reports an offer about two weeks after the final round.
  • General advice: ask for the base, bonus and equity breakdown in writing, ask which level the offer is at, and avoid naming a figure before they do if the recruiter lets you.

What we could not verify. The page used for values is the company philosophy page, not a hiring-values page, so the ten headings are principles of the business rather than interview criteria. Google's own careers pages describing the behavioural round did not load as readable text, and only one short first-hand account was found.

What we could not verify. Google's own careers pages (how-we-hire, interview-prep) loaded without readable content, so nothing here is official. Candidate reports were few; LeetCode and Glassdoor posts were blocked. Exact GHA length, who takes it, and the committee/team-match order are contested between sources. The code-comprehension pilot comes from a single guide. Per-round durations for onsite are mostly from one old and one new source.