Candidates describe a Google Data Analyst process that starts with a recruiter or phone screen. Technical rounds center on SQL, and metric-diagnosis cases and behavioral questions (including why Google) also come up. Reported rounds range from 3 to 6.
$146K
Avg. Base Comp
$183K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Across the Google Data Analyst reports, SQL is the most consistent technical thread, but it rarely stands alone. Candidates describe joins, counting occurrences, subqueries, BigQuery-style multi-table schemas, a timed three-query assignment, and conceptual questions such as DELETE versus TRUNCATE, HAVING versus WHERE, and what a full outer join does. Several also say they were asked to explain their logic aloud, in one case using Venn diagrams, so practice narrating your query as well as writing it.
The second theme is open-ended analytics reasoning. Candidates report prompts such as investigating a sudden drop in website traffic or in a product metric, measuring a new feature, and turning an ambiguous business question into a data plan. One candidate's SQL screen centered on naming the assumptions needed to handle messy data before writing the query. Stating assumptions and asking clarifying questions looks like a good habit.
Fit and communication also matter. Some candidates mention being asked why Google and why this role more than once. Others describe questions on personal projects, stakeholder communication, and resolving conflict with a colleague. A few mention statistics questions such as hypothesis testing and p-values, and live Python or SQL coding in a shared document.
Round counts and pacing vary by candidate, from about three interviews to six rounds. Reports of slow communication are common, so plan for a process that may take weeks. Most reports in this set ended without an offer.
Synthesized from 25 candidate 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.
The process was more intense than I expected. I went through several rounds covering SQL, analytical thinking, case-style problems, and behavioral questions. I felt most confident when we got into SQL and data analysis because that is what I work with every day. What surprised me was how much the interview focused on explaining my thinking rather than just getting the technically correct answer. The part where I started sweating was the ambiguous business cases—I had to make assumptions, ask clarifying questions, and defend my approach instead of relying on a predefined solution. It was challenging, but also one of the most interesting interview experiences I’ve had.
Questions asked: The technical rounds focused heavily on SQL and analytical reasoning. Some questions involved joining multiple tables, handling duplicates, calculating conversion rates, and using window functions to compare performance over time. One case asked me to investigate why a key product metric had suddenly dropped and explain what data I would look at first. Another focused more on experimental thinking—how I would measure whether a new feature actually improved user behavior. There were also behavioral questions around working with stakeholders, dealing with ambiguous requirements, and influencing decisions with data. The SQL itself wasn’t necessarily the hardest part; explaining why I chose a particular approach was where I had to think carefully.
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 | |
| First to Six | |
| Experiment Validity | |
| 500 Cards | |
| Last Transaction | |
| Button AB Test | |
| Top 3 Users | |
| Raining in Seattle | |
| Third Purchase | |
| Minimum Change | |
| Impression Reach | |
| Lazy Raters | |
| Network Experiment Design | |
| Daily Retention Summary | |
| Complete Addresses | |
| Reducing Error Margin | |
| Delivery Estimate Model | |
| Instagram TV Success | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Significance Time Series | |
| P-value to a Layman | |
| Losing Users | |
| Google Maps Improvement | |
| Fair Coin | |
| Found Item | |
| Ride Coupon |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report starting with a recruiter or phone call of roughly 20 to 45 minutes. It covers your background, projects, and why you want the role. A few also mention a fundamental SQL question at this stage. One candidate described this screen as the main gate, so prepare a concise story about why data analysis and why Google.
Some candidates report a timed assessment before or alongside the live interviews. Examples include a 30-minute assignment with three SQL queries of varying difficulty, and online tests covering SQL fundamentals, logic or pattern recognition, and English. Not every candidate describes this step, so treat it as something that may happen.
Candidates report one or more technical rounds of about 45 to 55 minutes. SQL topics include joins, counting occurrences, subqueries, and multi-table business queries, sometimes in BigQuery. Some mention live Python or SQL coding in a shared document, query debugging or optimization, or Pandas questions. Explain your reasoning as you write.
Several candidates describe scenario questions with no single right answer. Examples include why a metric or website traffic suddenly dropped, how to measure a new feature, and how to clean messy data for a non-technical stakeholder. Candidates report that clarifying questions, stated assumptions, and a structured approach mattered more than a quick answer.
Candidates report behavioral rounds on stakeholder communication, project ownership, conflict with colleagues, and using data to influence a business decision. Some mention Googliness-style questions, a hiring-manager conversation, or a final team-fit discussion. Prepare specific STAR examples, including what you would do differently.
