Google Interview Guides by Role
Sorted by experience volume — pick a role for the full breakdown.
Software Engineer
Data Scientist
Product Manager
Data Analyst
Business Analyst
Data Engineer
ML Engineer
AI Engineer
Product Analyst
Business Intelligence
Growth Marketer
How Google Interviews Across Every Role
Patterns that hold company-wide, regardless of which role you're interviewing for.
Typical Timeline
The end-to-end timeline varies meaningfully by role and team. SWE candidates frequently report six weeks to several months, especially when a referral sits in the talent database before a screen is scheduled, and team matching after the committee adds further time on top of that. PM candidates report a somewhat tighter loop of roughly four to eight weeks from first contact to offer, though team-specific hiring and reorgs — one PM candidate reported a mid-process hiring-manager change due to a reorg — can extend this. Across all roles, candidates should plan for at least four to six weeks from recruiter screen to offer, and SWE candidates specifically should budget for an additional team-matching phase after clearing the hiring committee.
Round type breakdown
- Onsite Coding / DSA Rounds25%
- Technical Phone Screen / Coding22%
- Behavioral / Googliness15%
- Recruiter Screen12%
- System Design12%
- Product Sense / Case9%
- Take-Home / Assessment5%
Recruiter Screen
Google's recruiter screen typically runs 15–30 minutes and covers role logistics, compensation expectations, location and relocation preferences, and a high-level review of the candidate's background. Candidates are sourced through online applications, internal referrals from current employees, and targeted outreach; SWE, PM, and other technical candidates commonly report that referrals can meaningfully shorten the time before a recruiter makes contact. The recruiter uses this call to explain the interview structure, and SWE candidates in particular report being offered dedicated preparation time and materials before the next stage is scheduled.
Hiring Decision
Google uses a hiring committee model rather than a pure hiring-manager decision. After the interview loop is completed, the candidate's packet — including interviewer scorecards and written feedback — is submitted to a hiring committee that reviews the full set of signals and makes the advancement decision; the hiring manager alone does not have final authority. SWE candidates in particular report that passing the committee review does not guarantee a role, because team matching is a separate subsequent step that can add several weeks to the process.
Values / Culture Round
Every interview loop at Google includes a dedicated Googleyness and leadership round, which is a behavioral interview assessing culture fit, collaboration, handling ambiguity, and how candidates navigate conflict and setbacks. Interviewers consistently push past rehearsed STAR answers and probe for specific moments, individual accountability, and genuine reflection rather than polished narratives — Data Analyst candidates report interviewers asking for the exact moment a project went wrong and why the candidate did not speak up sooner, while SWE candidates report questions focused on how they work through ambiguity and team dynamics rather than standard motivation prompts. This round is weighted seriously across all roles, with SWE, PM, Data Scientist, Business Analyst, and other candidates all reporting it as a distinct, evaluated component of the loop.
Offer & Negotiation
Google's compensation packages are structured around base salary, a cash bonus, and equity in the form of RSUs, with equity often representing a substantial share of total compensation, particularly at senior levels. SWE and PM candidates report that equity refresh schedules and signing bonuses are the most common negotiation levers, since base salary bands tend to be relatively fixed by level. Level assignment — which happens before an offer is extended — has a large downstream effect on total compensation, so candidates who believe their experience warrants a higher level report that raising that question early in the process with the recruiter is more effective than negotiating after an offer is made.
What they test you on
Topics based on recent interview experiences.
Recent Google Interview Reports
Sampled across roles, most recent first.
The most demanding part of my Google process was the systems-design discussion: I had to design a solution for a stream of server logs containing timestamps, service names, and latency values, then return the top k services by 99th-percentile latency within a sliding one-hour window. The interviewer wanted both the data structures and an explanation of how the approach would behave as the stream scaled, so it was not enough to sketch a high-level design.
For this systems-focused SWE role, I first spoke with a recruiter and then completed a 45-minute phone technical interview. The virtual onsite consisted of three coding interviews, one system-design interview, and a Googleyness round. The coding side was strongly DSA-focused, with medium-level LeetCode-style problems; at least one round included two questions that ranged from medium to hard. I also encountered a dynamic-programming optimization question, and there were questions on core CS fundamentals and my prior experience. The interviewers were smart and easy to work with, and they left time at the end for my questions.
The process felt lengthy, but I received feedback about a week after the onsite and ultimately did not receive an offer. My main advice is to prepare beyond standard medium coding questions: practice explaining a DP optimization clearly, refresh CS fundamentals, and be ready to reason concretely about streaming data structures, sliding windows, percentile calculations, and scalability for the system-design round.
Prep tip from this candidate
For the systems-design round, practice streaming log-data problems with a sliding one-hour window, top-k results, and 99th-percentile latency; be ready to justify the data structures and scaling behavior. Also prepare a dynamic-programming optimization problem alongside medium-to-hard coding questions and CS fundamentals.
Google Interview FAQ
How many rounds is the Google interview?+
The number of rounds varies by role. Software Engineer candidates typically go through a recruiter screen, one or two technical phone screens, and a virtual onsite with three to four coding rounds plus a system design and a Googliness/behavioral round. Product Manager loops commonly include five rounds covering product design, strategy, analytical, technical, and Googleyness. Data Analyst candidates report three rounds, while Business Analyst candidates report up to six interviews depending on the team.
How long does the Google interview process take?+
The full timeline commonly runs four to eight weeks, though SWE candidates have reported processes stretching beyond six months when team matching is factored in. For SWE roles specifically, passing the hiring committee does not guarantee a role — candidates then enter a separate team-matching phase that can add several additional weeks. Business Analyst and sales roles tend to move faster, with some candidates wrapping up in roughly two weeks.
How hard is the Google interview?+
The technical bar is high across roles. SWE interviews feature LeetCode medium-to-hard data structures and algorithms questions in a plain text editor with no ability to run code, plus follow-ups that change constraints mid-problem. PM interviews push hard on assumptions and expect AI to appear naturally in product thinking. Even Business Analyst candidates report questions such as designing a data structure for a running median or building a YouTube recommendation ranking model.
What roles does Google interview for?+
Google interviews across a wide range of roles. Based on recent experiences, the most common are Software Engineer, Product Manager, Data Scientist, Business Analyst, Data Analyst, Data Engineer, AI Engineer, Technical Program Manager, and various sales and account roles. Internship and new-grad tracks for software engineering and APM are also active.
Does Google use LeetCode-style questions?+
Yes. SWE and related technical role candidates consistently report LeetCode-style coding questions focused on data structures and algorithms including trees, graphs, heaps, dynamic programming, intervals, and sliding windows. Questions typically start at medium difficulty and escalate through follow-ups, and code is written in a shared document or plain text editor without autocomplete or execution support.
What is the Google Googliness round?+
The Googliness and leadership round is a behavioral interview present in nearly every Google role. Interviewers use STAR-style questions about conflict, failure, ambiguity, and collaboration, but they drill past rehearsed answers with follow-up questions to surface specific moments and real decisions. Multiple SWE and Data Analyst candidates noted this round was more intense than expected, even when technical rounds felt manageable.
Does Google require system design interviews?+
System design is a standard part of the SWE onsite and appears in some other technical roles such as Customer Solutions Engineer. Candidates are expected to identify constraints and bottlenecks independently, reason about scale and tradeoffs, and go beyond a high-level diagram. Recent interview topics include designing a top-K YouTube video system at planet scale and building a scalable distributed system handling millions of daily requests.
What happens after the Google onsite interview?+
After the onsite, a hiring committee reviews the full interview packet before an offer is extended. For SWE roles, passing the hiring committee does not guarantee a position — candidates then enter team matching, which can add several additional weeks. PM candidates may also go through team-specific matching after the loop, as one PM candidate noted the team-matching phase took a few additional weeks before they could accept an offer.
How important is the behavioral interview at Google?+
The behavioral component is taken seriously across all roles. Interviewers do not accept surface-level STAR answers and will probe for the exact moment a situation went wrong, why a candidate did or did not act, and what the real outcome was. Data Analyst and SWE candidates both noted that the Googliness round was more demanding than anticipated, with interviewers explicitly pushing back on polished or rehearsed responses.
What coding languages does Google accept in interviews?+
Google generally allows candidates to choose their preferred language. Python, Java, and C++ are all mentioned in recent SWE experiences, and at least one recruiter explicitly asked about comfort with Python and Java before the technical screen. For some rounds, candidates were also given the option to explain logic using pseudocode or spreadsheet-style functions rather than a formal programming language.