Google Data Scientist interview typically runs 4-5 rounds: recruiter screen, technical screen, technical rounds, on-site, and HR/Googliness. It usually takes a few weeks and is notably rigorous but fair, with technical screens often mirroring the on-site.
$152K
Avg. Base Comp
$285K
Avg. Total Comp
5-6
Typical Rounds
3-6 weeks
Process Length
Multiple candidates reported that Google cares less about polished theory and more about whether you can reason through a messy product problem end to end. We’ve seen that in the way interviewers push on metric tradeoffs, edge cases, and failure modes: one candidate was pressed on novelty effects and misleading test results, another on what to do when CTR rises but session time falls, and others on Simpson’s paradox, seasonality, and sample size. The pattern is consistent — Google wants people who can defend assumptions, not just name the right framework.
A recurring theme is that the company rewards candidates who can connect SQL, experimentation, and product sense in one coherent story. Several experiences mention window functions, rolling metrics, and data-cleaning tasks, but the real signal came from how candidates structured the answer around a product question rather than the syntax itself. The ML portions were similarly grounded: interviewers repeatedly cared more about evaluation, drift, cold start, and how a system fails in the real world than about fancy model names. That tells us Google is screening for practical judgment in ambiguous settings.
We also see a strong emphasis on communication to mixed audiences. One candidate noted that the HR conversation was not a formality, and another said the recruiter prep matched the actual loop closely, which suggests Google values clarity and consistency throughout the process. In our view, the candidates who do best here sound like people who can explain a decision to a PM, a scientist, and a non-technical stakeholder without changing the underlying logic.
Synthetized from 5 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Google process.
I got into Google's process without an HR screening call at all. They just emailed me directly saying I'd been selected for a technical screen. That was a nice surprise. The process ended up being two technical rounds, then an on-site that mirrored those same two rounds plus an HR round.
The first technical screen covered AB testing and SQL -- it was the heavier round in terms of breadth. The second was more of an ML case study where they gave me a scenario and asked how I'd approach it, including what models I'd use. It was high-level, not a coding round. More like, here's a situation, walk us through your thinking.
The on-site was basically the same two formats I'd already done in the technical screen, so having gone through those earlier I kind of knew what to expect. They added an HR round on top. The recruiters did a really great job preparing me -- whatever they shared with me matched pretty closely to what actually happened, so nothing really threw me off.
For the AB testing questions, they really wanted to see that you understood the full lifecycle -- not just setting up the test but interpreting results, handling edge cases like novelty effects, and knowing when a test result might be misleading. They asked things like how you'd handle a situation where your metric moved but you weren't sure if it was a real effect. For SQL, it wasn't just syntax -- they wanted to see how you'd structure a query to answer a real product question, so thinking out loud about your logic mattered as much as getting the right answer.
The ML case study round felt more like a product sense conversation with a modeling layer on top. They gave me a scenario tied to a Google product and asked how I'd frame the problem, what data I'd want, and what model I'd reach for. They pushed back on my answers to see how I'd defend my choices, so being able to explain your reasoning clearly is really important there.
I didn't get an offer. The feedback I got was that it came down to me and another finalist, and the other person just gave stronger signals for what the specific team was looking for. It was a close call, which honestly made it harder to hear, but the process felt fair and the interviewers were engaged throughout.
One thing I'd pass along: treat the technical screen as practice for the on-site, not just a gate. The formats are the same, so if you make it through the screen, you'll have a real preview of what's coming. Also, don't underestimate the HR round -- it's not just a formality. They're assessing whether you can communicate your work clearly to non-technical stakeholders, so practice telling the story of your past projects in plain language.
Prep tip from this candidate
The Google DS process here had two core round types repeated across both the technical screen and the on-site: an Applied Analysis round (AB testing plus SQL) and an ML case study round (high-level scenario, model selection). Nail both formats early because the on-site is essentially a repeat of the screen.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Google
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| First Touch Attribution | |
| Merge Sorted Lists | |
| First to Six | |
| Experiment Validity | |
| Last Transaction | |
| String Shift | |
| 500 Cards | |
| Button AB Test | |
| Top 3 Users | |
| Raining in Seattle | |
| Job Recommendation | |
| Impression Reach | |
| Minimum Change | |
| Jars and Coins | |
| Lazy Raters | |
| Bucket Test Scores | |
| Complete Addresses | |
| WAU vs Open Rates | |
| Network Experiment Design | |
| Delivery Estimate Model | |
| Find Bigrams | |
| Random Bucketing | |
| RMS Error | |
| Size of Joins | |
| Instagram TV Success | |
| Reducing Error Margin | |
| The Brackets Problem |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation with HR or a recruiter to review your background, role fit, and logistics such as timeline and compensation. In some cases, candidates reported being contacted directly for the next step without a separate HR screen.
A first technical interview focused on SQL, Python, and experimentation/statistics fundamentals. Candidates were asked to write queries with window functions, solve light data manipulation tasks, and discuss A/B test sanity checks, sample ratio mismatch, and metric interpretation.
A second screen centered on product analytics and ML thinking. This round often included product sense questions like improving Google Maps or measuring feature success, plus a high-level ML case study or model lifecycle discussion.
The onsite mirrored the screening formats and typically included multiple interviews covering SQL/coding, statistics or experimentation, product sense, and ML design. Some candidates also reported a behavioral or Googliness-focused round, with interviewers pushing on edge cases, assumptions, and how to explain work clearly.
A behavioral interview focused on communication, collaboration, leadership, and culture fit. Candidates were expected to tell clear stories about past projects and show they could work effectively with both technical and non-technical stakeholders.
The team reviews performance across the loop and makes a decision. Outcomes reported included offer, rejection after onsite, or waiting for final feedback, with the process described as fair and fairly standard for Google.