Google Data Analyst Interview Guide

Google evaluates data analysts on the same hiring attributes it uses for software engineers and product managers, so the data analyst interview scores your structured reasoning and leadership alongside your SQL. Expect hypothetical prompts like a sudden sales decline across every channel, which you'll work through out loud with no dataset to query. Posting titles like Business Intelligence Analyst, Product Analyst, and Engineering Analyst change the questions in the role-related knowledge round, but the core round types stay consistent across most analyst teams.

This guide breaks down each stage of the data analyst interview process, what Google interviewers look for, and how to prepare with real example questions, actionable tips, and resources.

Google data analyst interview process

The Google data analyst interview process scores 4 attributes: general cognitive ability (GCA), role-related knowledge (RRK), leadership, and Googleyness. Interviewers draw questions from shared question banks that Google refreshes regularly, and the hiring manager is often involved before the final decision.

Here's what the interview process can look like:

• Google Hiring Assessment: Pass/fail online work-style questionnaire, often sent within days of applying and before any recruiter contact
• Recruiter screen: Short call covering your background, motivation, and fit for the specific analyst posting, sometimes with light technical questions
• SQL technical screen: Roughly 60-minute live interview covering multi-table SQL queries
• Final loop: 3-5 interviews of roughly 45 minutes each covering GCA, RRK, and Googleyness and Leadership, sometimes including a hiring manager or director conversation, with up to 6 interviews for some business analyst teams
• Team matching: Conversations to place you on a team, which can begin before the final decision for some postings

Expect the process to take about 5 weeks from first contact to offer, and plan for 2 months or more for some postings. Google sometimes adds an extra interview when the loop doesn't fully cover one of the 4 attributes.

Google Hiring Assessment

The Google Hiring Assessment is a pass/fail, text-based work-style questionnaire that Google uses to screen many data analyst candidates before the technical interviews begin. The assessment doesn't include coding or video, and you complete it in Google's own recruiting portal.

Expect the assessment within days of applying, often before any recruiter contact. It takes under 30 minutes, and you'll typically have several days to complete it.

Recent versions use forced-choice sets where you pick the statement most and least like you, workplace scenarios where you choose the most and least likely response, and in some cases agree-disagree ratings on a 5-point scale. Google hasn't published the format, so expect variation.

Not every Google analyst posting includes the assessment. Google limits you to 3 applications in any 30-day period and requires a 90-day wait before you reapply to the same job.

The assessment evaluates:

• Adaptability: How quickly you adjust plans when goals or requirements change
• Collaboration: Whether you share resources and help teammates complete their work
• Resilience: How you respond to setbacks, mistakes, and critical feedback
• Attention to detail: How you treat small errors and document decisions
• Consistency: Whether your answers to related statements align across the full assessment
• Workplace judgment: How you respond to scenarios involving policy, ethics, confidentiality, and teamwork

Sample assessment statements

Here are real assessment statements reported by candidates:

• I quickly adjust my pre-existing work plans to meet changes in project goals.
• I complete my tasks effectively despite changing requirements.
• I share resources with my colleagues to help them complete their work.
• I keep detailed notes about the decisions made in meetings.
• I can overlook small, but important, errors in my work.
• Do you tailor your message based on the audience?
• Will you behave ethically?

SQL technical screen

Google's data analyst SQL technical screen tests whether you can write correct, efficient queries against a multi-table schema while explaining your logic. The live screen lasts roughly 60 minutes, and your interviewer may be the hiring manager or a technical team member.

Expect schemas with 5-7 related tables and prompts that test join logic and duplicate handling. The screen may take place in a shared document where you can't run your queries, and your recruiter can confirm which tool you'll use.

Prompts range from easy to hard, and many have simpler solutions than they first appear. Write the most direct query that answers the prompt, then refine it.

Some screens also add a statistics question, such as a hypothesis testing prompt.

Interviewers look for:

• Stated assumptions: Whether you name data-quality and business-logic assumptions before writing a query
• Join and aggregation fluency: Your command of multi-table joins, GROUP BY with HAVING, and window functions
• Data cleanup: How you handle duplicates, nulls, and inconsistent records without dropping valid rows
• Query efficiency: Your ability to optimize a working query and explain what made the original version expensive
• Clear narration: How well you explain each step so the interviewer can follow your logic as you write
• Statistical reasoning: Whether you can answer a hypothesis testing question alongside your SQL work

Recently asked questions

Here are some real interview questions reported by candidates:

• Optimize a given SQL query.
• Write a query to delete duplicate emails from a table.
• Explain the key differences between the BETWEEN and HAVING clauses in SQL.
• How would you perform a lookup in SQL?
• Write a query that returns the last transaction for each day from a table of bank transactions.

General cognitive ability (GCA) interview

The Google data analyst GCA interview tests how you break down an open-ended business question when there's no dataset to analyze.

Google GCA interviews mix hypothetical prompts with at least one behavioral question about how you've handled ambiguity, and the exact mix varies by team. The hypotheticals cover Google's own products as well as general business and stakeholder situations.

Product and metric prompts can appear in either the GCA or RRK interview, so prepare them for both.

Interviewers look for:

• Structured decomposition: How you break a vague scenario into components you can investigate in a logical order
• Clarifying questions: Whether you define scope, timeframe, and success metrics before proposing an answer
• Hypothesis-driven reasoning: How you prioritize likely causes and name the data you'd pull to confirm each one
• Stakeholder judgment: How you respond to conflict and accountability questions while keeping the focus on the fix
• Concise delivery: Whether you reach a clear recommendation without long pauses or circular answers
• Adaptability: How you adjust your approach when the interviewer adds a constraint or new information

Recently asked questions

Here are some real interview questions reported by candidates:

• Imagine sales dropped by 20% across all channels. What would you do?
• If an angry stakeholder calls you and asks, "Who's at fault?", how do you react?
• Should Google introduce ads to Google Flights?
• How would you measure customer satisfaction for Gmail?
• Choose a product you like. How would you identify its competitors?
• How would you define the internet to your audience?

Role-related knowledge (RRK) interview

Google data analyst role-related knowledge (RRK) questions test the skills listed on your specific posting, such as visualization design for Business Intelligence Analyst roles or experimentation for Product Analyst roles. The RRK portion of the final loop can include more than one interview, with case studies and product sense questions.

Hiring managers often ask detailed follow-up questions about your most recent work. Expect to explain the methods, trade-offs, and results of each analysis you discuss.

Trust and Safety postings can include a dedicated data analytics round with SQL extraction work, plus scenario questions on how you'd analyze a safety issue and work across teams.

Interviewers look for:

• Visualization judgment: How you choose chart types and dashboard layouts for a specific audience and decision
• Metric diagnosis: Your approach to investigating a sudden change in a key product metric
• Statistical grounding: Whether you can apply hypothesis testing to a product question
• Business translation: How you connect an analysis to the decision it supports
• Product sense: How you define success metrics for a Google product and connect them to user behavior
• Ownership of past work: How precisely you explain your own contribution to the analyses on your resume

Sample questions

Here are some real interview questions reported by candidates:

• What are your best practices for data visualization?
• A key product metric suddenly dropped. What data would you look at first?
• Walk me through your most recent analysis work.
• How would you measure whether a new feature improved user behavior?
• How do you compute a p-value from a single sample?

Googleyness and Leadership interview

The data analyst Googleyness and Leadership interview evaluates how you handle ambiguity, learn from mistakes, and lead work you don't formally own. Expect opening questions on your background and motivation for Google, followed by project-specific questions with hindsight follow-ups and hypothetical workplace situations.

Some loops close with a hiring manager or director conversation focused on your experience and fit for the team. Others add a separate stakeholder communication interview.

Interviewers look for:

• Comfort with ambiguity: How you move a project forward when goals or data are unclear
• Self-awareness: Whether you can name a mistake and what you changed afterward
• Emergent leadership: How you lead a decision or project without formal authority
• Prioritization: How you decide what to work on when requests compete
• Motivation for Google: Whether your reasons for joining Google connect to the team's work

Recently asked questions

Here are some real interview questions reported by candidates:

• Tell me about yourself.
• Why do you want to work at Google?
• Tell me about a project where you faced ambiguity. What would you do differently in hindsight?
• Tell me about a time you made a mistake.
• How do you prioritize?
• Describe the exact moment a project went wrong. Why didn't you speak up sooner?

How to prepare for the Google data analyst interview

1. Write SQL without running it: Practice multi-table SQL queries in a plain document, then trace each step by hand to catch duplicate rows from joins. State your assumptions out loud first, then rewrite each working query for efficiency.
2. Record yourself on hypotheticals: Work through 20 "imagine if" scenarios out loud and play them back. Cut long pauses and restarts until you can reach a recommendation in a few structured steps.
3. Map your stories to Google's attributes: Build behavioral stories for ambiguity, a mistake, competing priorities, and leading without authority, with a hindsight answer for each one. Research the products your target org supports so your Why Google answer connects to the team's work.
4. Use the posting to predict RRK topics: List the required and preferred qualifications on your job description and match each one to an analysis from your own work. For Business Intelligence Analyst postings, prepare a clear point of view on chart and dashboard design.
5. Review statistics and Python basics: Prepare to explain hypothesis testing and A/B test design in plain terms. If your posting lists Python, practice data manipulation in pandas.
6. Confirm formats with your recruiter: Ask which tool the SQL screen uses, how many interviews your loop includes, and whether any round is in person. Treat recruiter prep materials as a starting point and prepare for every round type.
7. Practice with mock interviews: Run SQL walkthroughs and GCA scenarios in mock interviews with a peer or AI interviewer, and ask for follow-up questions mid-answer. For targeted feedback on your answers, book a session with an expert coach.

Additional resources

• Data Analyst Interviews Course
• SQL Interviews Course
• Data Analyst Interview Guide
• Data Analyst Case Study Interview
• Google GCA Interview
• Google Data Analyst Interview Experience
• Other Google Interview Experiences
• Google Data Analyst Interview Questions

FAQs about the Google data analyst interview

Does the Google data analyst interview include Python?

Some Google data analyst loops include a live Python exercise using pandas, though SQL is the primary technical skill tested. Other loops add a standard coding challenge, such as merging overlapping intervals. Business Intelligence Analyst postings can include questions on Tableau or Power BI. Check your job description for the tools it lists and prepare to discuss each one.

Are Google data analyst interviews in person?

Google runs most data analyst interviews over video, including the final loop. Google's 2025 commitment to at least one in-person round focused on engineering and programming roles, so confirm your analyst loop's format with your recruiter. Google began piloting interviews that allow its Gemini AI assistant in 2026, but the pilot covers one software engineering round. Assume AI tools aren't allowed in your analyst interviews unless your recruiter says otherwise.

How hard is the Google data analyst interview?

The Google data analyst interview is moderately hard, with SQL prompts that range from easy to hard and open-ended GCA hypotheticals that have no single correct answer. Expect one process to test SQL, statistics, product sense, and behavioral judgment.

How do Google business analyst, product analyst, engineering analyst, and business systems analyst interviews differ?

Google business analyst, product analyst, and engineering analyst interviews share the same structure and differ mainly in SQL depth and RRK content. Business analyst loops lean on window functions, multi-table joins, and hypothetical business scenarios. Product Analyst roles sit on Google's data science ladder, and their loops add hypothesis testing and product sense questions. Trust and Safety engineering analyst loops focus closely on your recent analysis work, and Business Intelligence Analyst loops add query optimization and data visualization. Business Systems Analyst loops focus on solution and integration design, often for SAP or finance systems, with open-ended end-to-end design questions.

How much does a Google data analyst make?

Here are the reported compensation ranges by level for Google Data Analysts, according to Levels.fyi:

• L3: ~$145K
• L4: ~$205K
• L5: ~$254K
• L6: ~$386K

Base salary is the largest share at every level, and stock and an annual bonus account for the rest. Stock's share of the package roughly triples between L3 and L6.