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: 4 to 8 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 (L7, Sr Staff)
- Principal (L8, Principal)
The Google SWE interview, stage by stage
Recruiter screen (30 min · call)
The opening call with your recruiter. They confirm your background, the level they intend to slot you into, your timeline, and rough comp expectations, and they lay out how the rest of the loop will run. It is not a technical round, but the level it sets quietly decides how hard every stage after it will be.
- Clarify your target level. L4 versus L5 reshapes the entire loop, especially whether a system-design round is in play, so understand where you are being placed.
- Ask about the timeline. Google loops run long once team matching and the hiring committee are counted, so get a realistic picture up front.
- Have your comp range ready. This is where the negotiation window first opens; a vague answer here can anchor you low later.
Technical phone screen (45 min · shared Google Doc)
One to two coding problems with a Google engineer, typed into a plain shared Google Doc with no autocomplete and no compiler. Because nothing runs for you, syntax discipline and talking through your reasoning matter as much as the algorithm. This screen is a genuine filter, not a formality.
- Code as if it must compile in your head. There is no editor help in the Doc, so track types, off-by-ones, and edge cases yourself as you write.
- Narrate the whole way. State your approach and complexity before you type, then think out loud; a silent solve reads as a weaker signal even when it is correct.
- Land the optimal, then verify. Reach the best time and space you can and dry-run it on a small input before you call it done.
The onsite loop (4 to 5 rounds · virtual or onsite)
The core evaluation: four to five back-to-back interviews of about 45 minutes each. Typically two to three are coding rounds on data structures and algorithms, one is system design from L5 and up, and one is Googleyness and Leadership, Google's behavioral round. The coding bar leans hard on graphs, trees, dynamic programming, and string manipulation.
- Coding, two to three times. Expect graph traversal, tree recursion, dynamic programming, and heavy string work. Optimal complexity is assumed, and interviewers want clean, readable code with edge cases handled without being asked.
- System design, from L5 up. Design a real system end to end: APIs, data model, scaling, caching, and failure handling, with back-of-envelope capacity math. Depth on trade-offs beats reciting service names.
- Googleyness and Leadership. One dedicated behavioral round on collaboration, humility, bias to action, and handling ambiguity. Bring concrete stories with your specific role and the outcome, not team-level generalities.
Team matching (days to weeks)
A step unique to Google's flow: you pass the loop first, then get matched to a team. You talk with hiring managers who have open headcount, and both sides decide on fit. It is not another interview, but it can add real calendar time, and in tight headcount periods it is where offers stall the longest.
- Fit runs both ways. These are conversations, not interrogations; ask about the roadmap, on-call, and the tech stack, because you are choosing too.
- Have preferences ready. Domains, product areas, or locations you care about help your recruiter route you faster to a good match.
- Budget for the wait. With no open req that fits, matching can stretch for weeks even after a strong loop, so keep other options warm.
Hiring committee and offer (1 to 2 weeks after)
Google's signature step. Your interviewers write detailed feedback, and a hiring committee of senior engineers who never met you reviews the whole packet and makes the decision. Because the deciders are not the people in your rounds, consistent, well-documented signal across every interview matters more than one dazzling round.
- The committee, not your interviewers, decides. They read written feedback and code, so clear reasoning that an interviewer can capture on paper is what actually carries.
- Consistency clears the bar. A steady loop reads better to the committee than one standout round paired with a shaky one.
- Expect further review for senior levels. L6 and up can go to additional committee and executive review, and the offer and comp follow only once the packet clears.
How hard is the Google interview?
Difficulty mix: 15% easy, 71% 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?
Senior SWE total compensation commonly lands in the mid-to-high six figures once base, a four-year GSU grant, and any sign-on are combined, and it varies by location and negotiation. 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?
End to end, expect roughly four to eight weeks, though it can run longer. Team matching and the hiring committee are the two steps that most often add time beyond the interviews themselves.
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