The Google SWE Interview Guide

Walk through Google's software engineer hiring loop the way it actually runs: the phone screen, the onsite rounds, the hiring committee, and team matching. Then rehearse the real questions candidates report, so the room holds no surprises.

• Loop length: 6 to 12 weeks
• Expected difficulty: Medium, some hard
• Coding rounds: 2 to 3
• System design: From L5

Google levels & pay

• SWE II (L3, Entry)
• SWE III (L4, Mid)
• Senior SWE (L5, Senior)
• Staff SWE (L6, Staff)
• Senior Staff SWE (L7, Sr Staff)
• Principal Engineer (L8, Principal)
• Distinguished Engineer (L9, Distinguished)

The Google SWE interview, stage by stage

Recruiter screen (30 min · phone call)

The first real conversation, and it is short. Your recruiter checks your background, asks what you are building right now, and decides which level to submit you at. They also walk you through the shape of the loop, ask about your timeline, and usually ask for a compensation range. Nothing here is technical, but the level they write down at the end of this call sets the bar for every round that follows, so it is worth treating as part of the interview rather than as paperwork.

• Ask which level you are being submitted at. L4 and L5 are graded against different bars, and an L5 submission adds a system design round that L3 and L4 candidates usually do not get. Knowing the target before you start preparing saves weeks of aiming at the wrong thing.
• Get a real timeline, not a friendly one. Ask when the loop is likely to be scheduled, how busy the interview pool is, and what happens after the onsite. Google has more stages after the interviews than most companies, and you need that picture to keep other processes in step.
• Have a compensation range ready before the call. The number you say here follows you into the offer conversation weeks later. A range with a reason behind it, such as a competing process or the equity you would be walking away from, holds up better than a single figure you cannot explain.

Hiring assessment and online assessment (~30 min and ~90 min · online)

Before an engineer ever speaks to you, Google may send one or two online stages, and they are not the same thing. The Hiring Assessment is a questionnaire about how you work with no coding in it at all, and candidates in 2026 report the format has changed: instead of rating single statements from strongly agree to strongly disagree, you are shown three descriptions and asked which is most like you and which is least. Early career and new grad candidates often get a separate coding assessment on top, usually two problems in about 90 minutes on a HackerRank style platform. Recent candidate reports say some of those coding problems now come with an AI assistant you are allowed to use, with sample problems beforehand so you can try it. Plenty of experienced loops skip both stages, so getting one, both or neither says nothing about your chances.

• The questionnaire now forces a choice. With three statements and a most and least pick, the old habit of parking every answer safely in the middle is not available to you. Read all three, choose honestly, and stay consistent when the same idea comes back in different words later in the form.
• Treat the coding assessment as a real filter. Two problems in about 90 minutes is tight, and candidates describe finishing at the buzzer even when the invitation email said it would take seventy. Bank the easier problem quickly so the harder one gets the time it actually needs.
• Spend ten minutes on the sample problems. If your assessment offers an AI assistant, the samples are the only place you learn what it answers well and where it wastes your time. Candidates who skipped them describe walking into the real thing with no feel for the tool at all.

Technical phone screen (45 min · shared Google Doc)

One Google engineer, one or two coding problems, and a blank shared document. In most reports there is no autocomplete, no syntax checking and nothing runs, so you have to hold the code in your head and check it yourself. Many candidates also describe a behavioral half, either as a second scheduled round or as the last ten minutes of the same 45, with questions about conflict, ambiguity and a project someone else blocked. Some teams have moved to a proper editor, but the plain document is still the format most candidates describe, so prepare for that. This screen removes a large share of applicants, so it deserves the same preparation as the onsite rather than being treated as a warm-up.

• Practise in a bare document, not on a platform. Writing code with no editor help is a genuinely different skill from solving on a site that compiles and runs for you. It is also worth knowing you can draw in the Doc, because a problem that turns into a design discussion is much easier to hold together with a diagram on the page.
• Agree on the problem before you type anything. Candidates report correct solutions being marked down because the code appeared before the plan did. Say the approach, the time cost and the space cost out loud first, which gives the interviewer something concrete to write down and gives them a chance to redirect you before you burn twenty minutes.
• Walk through a small input before you say you are done. Nothing compiles for you, so an off-by-one or an unchecked empty input stays in the code unless you find it yourself. Finishing and going silent is one of the most common ways a solvable round ends up as a weak signal.

The onsite loop (4 to 5 rounds · 45 min each)

The main event: four to five interviews of about 45 minutes, usually run back to back across one or two days, each with a different engineer who has not spoken to the others. For most candidates that is two or three coding rounds, one Googleyness and Leadership round, and, from L5 upwards, a dedicated system design round. From around May 2026 Google has been piloting a code comprehension round on select US teams including Google Cloud and Platforms and Devices, reported so far at L3 and L4, where you read, debug and improve an existing codebase in a shared editor with Gemini available as an assistant in place of one traditional coding round, so ask your recruiter which format your loop uses. Every interviewer writes up detailed notes and a score afterwards, and that write-up is the only thing the hiring committee ever sees. An answer the interviewer can capture clearly on paper carries further than a clever one they cannot.

• Coding, two or three times. Graphs and traversal, union find, trees and recursion, dynamic programming and heavy string work come up again and again, alongside the usual arrays, hash maps and heaps. Interviewers commonly keep changing the requirement once you have a working answer, so expect follow-ups that push a solved problem into much larger inputs, then onto several machines, and ask you to name whether the bottleneck is CPU, memory, bandwidth or disk. Clean readable code plus edge cases you raise before being asked is what lifts a round from a pass to a strong pass.
• System design, from L5 up. One open problem, about 45 minutes, taken end to end: requirements, API, data model, storage choice, scaling, caching, and what happens when a component fails. Rough capacity numbers you can defend land well here, and candidates report interviewers working through their own list of follow-ups, so get a simple version on the board early and check in rather than talking through a plan of your own for twenty minutes. The fastest way to lose this round is to start drawing boxes before you have pinned down what the system is required to do.
• Googleyness and Leadership. One round on how you work with other people: collaboration, ambiguity, disagreement, and what you did when something went badly. Recurring questions include a conflict with a manager, a project blocked by a colleague, a time you were handed something ambiguous, and a time you had to give someone difficult feedback. Vague, team-level answers with no clear account of what you personally did are what gets marked down here.

Team matching (days to several weeks · manager conversations)

Google hires you into the company first and onto a team second, which is why this stage exists at all. Your recruiter circulates your packet to hiring managers with open headcount, and you have conversations with the ones who are interested. The timing moves around: some candidates match after the onsite, some are told a role was filled and they must re-match before an onsite can even be booked, and a few are simply assigned a team and never have the conversation at all. These are not scored the way an interview round is, but managers do pass, and candidates describe team match calls that included behavioral questions and then a week of silence before a no. This is the stage that most often stretches a six week process past twelve, because it depends entirely on which teams have budget that quarter.

• Treat it as a conversation you are also assessing. Ask what the team ships, what the on-call rotation looks like, how much of the work sits in the monorepo versus a newer stack, and how big the team is. You are choosing the next few years of your working life, and managers do notice when a candidate has no questions.
• Give your recruiter specific preferences. Product area, office, and whether you want infrastructure work or product work all help them build a shortlist faster. Saying you are open to anything sounds accommodating but in practice slows the search down.
• Keep your other processes warm. A strong loop with no matching team can sit for weeks, and no offer is written until a team commits. Positive feedback from your interviewers is not an offer, so do not stand down your other conversations on the strength of it.

Hiring committee and offer (1 to 3 weeks · no candidate involvement)

This is the stage that makes Google's process different from most of its peers. A committee of senior engineers who never met you reads the entire packet: every interviewer's written feedback, the code you wrote, your resume, referrals, and any manager support. They can approve, reject, or send the packet back for an extra interview when the signal is mixed. At L6 and above it then goes through further compensation and senior leader review before anything reaches you. You do nothing at this stage except wait, which is exactly why consistency across the loop matters more here than one outstanding round.

• Your interviewers do not make the decision. They supply written evidence, and the committee decides on that evidence alone. Reasoning you said out loud and that made it into the notes counts. Reasoning that stayed in your head does not exist as far as this room is concerned.
• One weak round is usually what sinks a packet. The committee is looking for a steady signal across the whole loop. Four solid rounds and one no-hire is a much harder packet to approve than five consistently good ones, even if the average looks similar.
• Expect more review the more senior you are. L6 and above pass through extra committee and leadership steps, and each one adds calendar time. Some candidates also get a separate visa check call in here. Two quiet weeks after your onsite is normal and is not a signal about the outcome.

How hard is the Google interview?

Difficulty mix: 14% easy, 72% medium, 14% hard.

How to prepare

Build a daily coding base (Weeks 1 to 6)

Code every day, weighted toward the patterns Google leans on: graph traversal, trees and recursion, dynamic programming, and string manipulation. Start at medium and push into hard as the weeks pass, and practice in a plain doc with no autocomplete so the phone screen feels familiar.

Drill talk-out-loud fundamentals (Weeks 2 to 5)

Google scores communication and clean code as much as the answer. Rehearse stating your approach and complexity before typing, narrating trade-offs, and dry-running your solution, ideally with a partner or mock interviewer who can flag where you go quiet.

Learn system design (Weeks 3 to 7)

If you are targeting L5 or above, build a repeatable design framework: requirements, API, data model, scaling, caching, and failure handling, with capacity math you can defend. Practice designing a handful of real systems end to end and explaining why you chose each piece.

Prepare Googleyness stories (Weeks 5 to 8)

Write concrete behavioral stories for the Googleyness and Leadership round: collaboration, handling ambiguity, learning from failure, and bias to action. Keep each one specific about your role and the outcome, and practice telling them tightly so they fit inside a shared round.

Recently asked

Meeting rooms: minimum rooms for overlapping intervals

About Google

Google is a subsidiary of Alphabet Inc., the holding company formed in 2015 to separate the core search and advertising business from Alphabet's other bets. Founded in 1998 by Larry Page and Sergey Brin out of a Stanford research project, Google grew from a single search engine into a sprawling product portfolio spanning Search, Ads, Android, Chrome, YouTube, Google Cloud, Workspace, and a widely used suite of consumer and enterprise services. Advertising still generates the majority of revenue, while Cloud and subscriptions have become fast-growing pillars.

The company is headquartered at the Googleplex in Mountain View, California, and operates engineering offices across the United States, Europe, and Asia. Alphabet has invested heavily in artificial intelligence through Google DeepMind, positioning models and AI-driven features across nearly every product line. For engineers, Google is known for a strong internal infrastructure culture, a large monorepo, and a heavy emphasis on code quality, readability, and technical rigor.

Frequently asked

How many rounds are in the Google SWE interview?

Most candidates go through a recruiter call, a technical phone screen, and an onsite loop of four to five rounds. Google then adds two stages that many companies do not have: team matching and a hiring committee review before any offer is made.

What is the Google hiring committee?

After your loop, a committee of senior engineers who did not interview you reviews your written feedback, your code, and your interviewers' notes, then decides whether to extend an offer. Keeping the decision separate from the interviewers is meant to hold a consistent bar across the company.

What is Googleyness?

Googleyness is Google's shorthand for the non-coding traits it looks for: collaboration, humility, comfort with ambiguity, bias to action, and doing the right thing. It is assessed mainly in the Googleyness and Leadership round and reinforced by comments throughout the loop.

How does team matching work at Google?

You pass the loop first, then get matched with a specific team that has open headcount. You talk with hiring managers, and both sides decide on fit. It is not a pass-or-fail interview, but it can add days or weeks to the process, especially when headcount is tight.

At what level does system design start?

System design typically enters the loop at L5 and above. L3 and L4 candidates are usually evaluated on coding and Googleyness, with at most a light design signal, while L5 and up get a dedicated design round that carries real weight.

What is the difference between L4 and L5 at Google?

L4 is a mid-level engineer expected to deliver well-scoped work with strong, clean coding. L5 is a senior engineer expected to own systems end to end, drive design decisions, and lead work with less direction, which is why the L5 loop adds a system-design round and a higher Googleyness bar.

What does an L5 Senior SWE earn at Google?

Median total compensation for an L5 Senior SWE is about $434k a year, made up of roughly $232k base, $170k a year of GSUs from a four-year grant, and a target bonus near $32k. Google front-loads its grants 33/33/22/12, so year one pays well above a flat quarter of the grant. Use the pay estimator above for a location-adjusted range.

What coding topics does Google focus on?

Google's coding rounds lean heavily on graphs and traversal, trees and recursion, dynamic programming, and string manipulation, alongside the usual arrays, hash maps, and heaps. Optimal time and space complexity is expected, not just a working answer.

Which programming languages can I use?

You may use whatever mainstream language you are strongest in, commonly Python, Java, C++, Go, or JavaScript. Google cares about correct, readable code and sound reasoning far more than the language you pick.

Do the phone screens use a code editor?

The technical phone screen is usually done in a shared Google Doc with no autocomplete and no compiler, so you have to manage syntax and edge cases yourself. Practicing in a plain document before the screen makes a real difference.

How long does the Google interview process take?

Most candidates should plan for six to twelve weeks from the recruiter call to a signed offer. The interviews are only part of it. The hiring committee reviews your packet after the loop, senior levels get extra review on top, and then team matching has to find you a team with open headcount. Team matching is the stage that stretches timelines the most, and it can add weeks on its own even after a strong loop.

What is the Googleyness and Leadership round?

It is a dedicated behavioral interview focused on how you work with others, handle ambiguity, learn from failure, and take initiative. Interviewers want specific stories where your individual role and the outcome are clear, not team-level summaries.

If I get rejected, when can I reapply to Google?

Google generally asks candidates to wait before reapplying, commonly around a year for the same kind of role, though it can be shorter. Recruiters can hold your packet and feedback, so a stronger, well-prepared second attempt is entirely realistic.

Are the onsite rounds virtual or in person?

Google runs the onsite loop either virtually or in person depending on the role, team, and location. The format and structure are the same in both cases: four to five roughly 45-minute rounds covering coding, design where applicable, and Googleyness.

Does a great loop guarantee an offer?

Not on its own. A strong loop has to clear the hiring committee, and then you still need a team match with open headcount. Consistent signal across every round is what gives the committee the confidence to say yes.

How much does behavioral signal matter at Google?

More than many candidates expect. Googleyness is scored throughout the loop and in a dedicated round, and weak or vague behavioral answers can stall an otherwise strong technical packet at the committee stage.

Google interview questions on Karavine