Google Business Analyst Interview Questions (2026)

1. 1Recruiter screen30 minEasy

   Background, level calibration, and process walkthrough with a recruiter.

2. 2Technical phone screen45 minHard

   One or two DSA problems solved live in a shared editor with emphasis on optimal complexity and clean code.

3. 3Coding round (onsite)45 minHard

   Harder DSA with follow-up constraint changes; interviewer scores GCA and RRK on a rubric.

4. 4System design round45 minHard

   Design a planet-scale system (e.g. a piece of Search or YouTube) with explicit capacity estimates and tradeoffs.

5. 5Googleyness & Leadership45 minMedium

   Behavioral round on collaboration, ambiguity, and user-first judgment scored against Google's structured rubric.

6. 6Hiring Committee review30 minMedium

   No candidate interaction; the written feedback packet is reviewed and the hire/no-hire decision is made, followed by team matching.

1. Q1

   Design an A/B test for a new Search ranking or recommendation change. Define hypothesis, primary metric, guardrails, randomization unit, and launch decision rule

   MediumStatistics & Experimentation RoundA/B TestingGoogle-specific

   Context: Context: Google wants to improve relevance while protecting user trust and privacy.

   How to answer: A strong answer will define a clear, testable hypothesis for the Search ranking change (e.g., 'New algorithm increases CTR'). The primary metric should directly reflect the hypothesis, such as Click-Through Rate (CTR) or query success rate, with guardrail metrics like latency, error rate, and revenue to prevent negative side effects. The randomization unit should be the user or search session to ensure independent observations, and the launch decision rule should specify statistical significance thresholds for the primary metric and acceptable ranges for guardrails over a defined test duration.

2. Q2

   During a Google Maps experiment, the treatment/control split is 52/48 instead of 50/50. How would you diagnose sample ratio mismatch?

   MediumStatistics & Experimentation RoundA/B TestingGoogle-specific

   Context: Assume assignment logs, exposure logs, and eligibility filters may disagree.

   How to answer: A strong candidate would first confirm the SRM by checking the observed split against the expected split using a chi-squared test. Next, they would investigate potential causes, starting with the random assignment mechanism itself (e.g., hash function issues, caching problems, or user ID inconsistencies). They would also consider external factors like bot traffic, data logging errors, or pre-existing user segments that might disproportionately fall into one group. Finally, they would discuss the implications of SRM on experiment validity and how to mitigate it, such as re-running the experiment or adjusting for the mismatch if possible.

3. Q3

   A new Cloud Marketplace feature shows a large week-1 lift in query success rate, but the effect fades by week 4. What could explain this and how would you design the test duration?

   MediumStatistics & Experimentation RoundA/B TestingGoogle-specific

   Context: Discuss novelty, learning effects, seasonality, and durable impact.

   How to answer: The fading effect could be due to novelty effect, where users initially engage more with the new feature but revert to prior behavior once the novelty wears off. Another explanation is a selection bias, where early adopters (who are often more tech-savvy or engaged) are the first to try the feature, inflating initial metrics. The feature might also have short-term benefits that don't translate to long-term value, or there could be external factors or seasonality influencing the later weeks. To design the test duration, I would recommend a minimum of 4-6 weeks to capture potential novelty effects and allow for user habituation. Longer durations (8-12 weeks) would be ideal to observe sustained impact, account for weekly/monthly cycles, and ensure statistical significance over time, especially for features impacting long-term user behavior or revenue.

4. Q4

   The Google Maps experiment lifts query success rate overall, but only for new users and only in one device_type. How would you evaluate heterogeneous treatment effects?

   HardStatistics & Experimentation RoundA/B TestingGoogle-specific

   Context: Balance pre-planned segments with exploratory slicing and multiple testing risk.

   How to answer: A strong candidate would first acknowledge the initial positive overall result and then immediately identify the need to segment the data by user type (new vs. existing) and device type to confirm the observed heterogeneity. They would propose running separate A/B tests or subgroup analyses within the existing experiment for each segment, focusing on the 'new users' and the specific 'device_type' where the lift was observed. The evaluation would involve calculating statistical significance and effect size for these specific subgroups, comparing them to the control group within those same segments, and considering potential reasons for the differential impact, such as UI changes being more intuitive for new users or specific device capabilities. Finally, they would discuss the implications for launch strategy, potentially rolling out the feature only to the successful segment initially.

5. Q5

   How would you design ramp-up, holdback, and post-launch monitoring for a successful Cloud Marketplace A/B test?

   HardStatistics & Experimentation RoundA/B TestingGoogle-specific

   Context: Include ramp stages, persistent holdback, alert thresholds, rollback criteria, and owner accountability.

   How to answer: A strong answer outlines a phased ramp-up strategy, starting with a small percentage of traffic (e.g., 1-5%) to validate technical stability and detect immediate negative impacts, followed by gradual increases (e.g., 10%, 25%, 50%) while continuously monitoring key metrics. For holdback, the candidate should propose retaining a small, untreated control group (e.g., 1-2%) even after 100% rollout, to measure long-term incrementality and guard against novelty effects or seasonal changes. Post-launch monitoring involves establishing a dashboard with critical business and technical metrics (e.g., conversion rates, revenue, error rates, latency) with clear alert thresholds, ensuring ongoing performance validation and rapid issue detection.

6. Q6

   Two overlapping experiments on YouTube Shorts both affect ad revenue per mille. How would you detect and manage interaction effects?

   HardStatistics & Experimentation RoundA/B TestingGoogle-specific

   Context: Discuss experiment registry, factorial design, exclusion rules, and interaction terms.

   How to answer: A strong candidate would first emphasize the importance of pre-analysis, including understanding the experimental designs and potential overlap points. They would then propose statistical methods like ANCOVA or regression analysis with interaction terms to detect significant interaction effects on ad revenue per mille. Mitigation strategies would involve sequential rollout, re-designing experiments to be mutually exclusive, or using a switchback/time-series approach if direct user segmentation is impossible. Finally, they would discuss the trade-offs of each approach in terms of statistical power, time, and complexity.

7. Q7

   Google is considering launching Google Ads in a new country. Build a decision framework and the first 90-day success metrics

   MediumProduct Analytics & Business CaseBusiness CasesGoogle-specific

   Context: Include demand, supply, operations, compliance, cost, and competitive positioning.

   How to answer: A strong decision framework for launching Google Ads in a new country should involve evaluating market potential (GDP, internet penetration, existing ad spend, competitor landscape), regulatory and legal considerations (data privacy, ad content laws), operational feasibility (local team, payment infrastructure, language support), and strategic alignment with Google's broader goals. Success metrics for the first 90 days should focus on leading indicators and early adoption, such as advertiser sign-ups, ad impressions served, initial ad spend, and cost-per-click (CPC) trends, rather than long-term profitability. Qualitative feedback from early adopters and local team ramp-up metrics are also crucial.

8. Q8

   Marketing spend for Cloud Marketplace increased, but query success rate did not. How would you evaluate whether spend is inefficient or the measurement is incomplete?

   HardProduct Analytics & Business CaseBusiness CasesGoogle-specific

   Context: Consider incrementality, attribution, channel mix, saturation, and lagged effects.

   How to answer: A strong candidate would first define 'query success rate' and 'marketing spend' in the context of Cloud Marketplace, identifying potential lagging indicators or indirect impacts. They would then propose a structured approach to analyze the data, looking for segmentation (e.g., new vs. existing users, specific product categories, marketing channels) and time-based trends. The evaluation would involve identifying potential confounding factors or external influences and then suggesting additional metrics that might better capture the impact of marketing spend, such as lead generation, MQLs/SQLs, pipeline value, or customer acquisition cost (CAC) for Marketplace solutions. Finally, they would outline an experimental design (e.g., A/B testing) to isolate the impact of spend or propose a deeper qualitative analysis.

9. Q9

   Google wants to launch or expand an ads/merchant monetization product related to Google Play. What business metrics decide whether it is worth scaling?

   HardProduct Analytics & Business CaseBusiness CasesGoogle-specific

   Context: Balance advertiser/partner value, customer experience, organic conversion, and incremental profit.

   How to answer: A strong candidate would outline a multi-faceted approach to evaluating a Google Play monetization product's scalability, starting with core financial metrics like Net Revenue (or Gross Merchandise Value, GMV, if applicable) and Profit Margin, considering both short-term and long-term viability. They would then discuss user/developer adoption and engagement metrics, such as Monthly Active Users (MAU) or Developers (MAD), conversion rates, and retention rates, as these indicate product health and potential for growth. Finally, they would touch upon operational efficiency metrics like Cost of Goods Sold (COGS) or Cost of Revenue, Customer Acquisition Cost (CAC), and Lifetime Value (LTV) to ensure sustainable scaling, along with strategic alignment with Google Play's ecosystem goals.

10. Q10

    Design a real-time operations dashboard for YouTube Shorts focused on page load latency. What thresholds, alerts, and ownership model would you set?

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingGoogle-specific

    Context: Assume the team needs to detect issues quickly and prevent alert fatigue.

    How to answer: A strong answer would outline key dashboard components: a primary metric (average page load time for Shorts), secondary metrics (p90/p99 latency, error rates, backend vs. frontend breakdown, geographical distribution), and dimensions (device type, browser, Shorts ID). Thresholds should be set with clear rationale (e.g., 2-second soft, 3-second hard for average load; 5-second for p99). Alerts would trigger for breaches, significant deviations, or sustained increases, escalating through L1/L2 support. Ownership would involve a cross-functional team (SRE, Product, Engineering) with clear roles for monitoring, investigation, and resolution.

11. Q11

    Build a cohort dashboard for Google Maps. Which cohort definitions, retention views, and segment controls should it have?

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingGoogle-specific

    Context: Prioritize clarity over chart count and make denominator definitions visible.

    How to answer: A strong answer will define cohorts based on user acquisition date (e.g., first app install, first search) and a key initial action (e.g., first navigation, first review). Retention views should include N-day retention (daily/weekly), rolling retention, and potentially bracket retention, showing engagement with core features like search, navigation, or contribution. Segment controls are crucial for slicing data by geography (country/city), device type (iOS/Android), acquisition channel, and user persona (e.g., frequent traveler, local guide) to identify specific trends and opportunities.

12. Q12

    Set alert thresholds for query success rate, ad revenue per mille, and page load latency in Cloud Marketplace. How would you distinguish noise from a real incident?

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingGoogle-specific

    Context: Use seasonality, baselines, statistical thresholds, and business severity.

    How to answer: A strong candidate would first define appropriate baseline metrics and historical trends for each KPI (query success rate, ad revenue per mille, page load latency). They would then propose statistical methods like standard deviation, moving averages, or control charts to set dynamic thresholds, rather than static numbers. To distinguish noise from real incidents, they would suggest correlating alerts across multiple related metrics and services, looking for sustained deviations rather than transient spikes, and considering the business impact and user experience implications of the change. Finally, they would emphasize the importance of continuous refinement of alert thresholds based on incident reviews and system behavior.

13. Q13

    A Search dashboard is slow and users export raw data instead. How would you improve performance and adoption?

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingGoogle-specific

    Context: Discuss aggregated tables, filters, caching, chart pruning, and stakeholder training.

    How to answer: Start by diagnosing the root cause of the slowness, focusing on data volume, query complexity, and dashboard design inefficiencies. Propose technical solutions like optimizing data sources (e.g., pre-aggregation, indexing, data warehousing), simplifying queries, and improving dashboard rendering (e.g., fewer visuals, asynchronous loading). For adoption, address user needs by improving UI/UX, providing training, and demonstrating the dashboard's value proposition over raw data. Implement a feedback loop and monitor performance metrics to ensure continuous improvement and user satisfaction.

14. Q14

    Create a dashboard narrative for Search Engineering lead explaining why query success rate changed for Google Ads. What charts would you show first?

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingGoogle-specific

    Context: Use a top-down story with impact, drivers, segments, and recommended actions.

    How to answer: The dashboard narrative should start with a clear summary of the change in query success rate (QSR) for Google Ads, including the magnitude and direction of the change, and the specific timeframe. The initial charts should highlight the overall QSR trend, then immediately break down the QSR by key dimensions like device type, geographic region, and ad type (e.g., Shopping, Search, Display) to pinpoint where the change is most pronounced. Subsequent charts should correlate these QSR changes with potential influencing factors such as recent algorithm updates, changes in ad quality scores, bid landscape shifts, or significant advertiser policy changes, using a drill-down approach to identify root causes. The narrative should conclude with actionable insights and recommended next steps for the Search Engineering lead.

15. Q15

    For Search, how would you measure supply-demand balance between users and advertisers?

    MediumProduct Analytics & Business CaseProduct AnalyticsGoogle-specific

    Context: Examples include availability, wait time, search zero-results, acceptance, inventory, or partner response rate.

    How to answer: A strong answer would define supply (advertiser inventory/bids) and demand (user queries/clicks) for Google Search. It would then propose key metrics for each, such as ad impressions available, bid density, ad coverage, click-through rates (CTR), and cost-per-click (CPC). The candidate should then suggest metrics to assess balance, like ad load, revenue per query, and advertiser ROI. Finally, they should discuss how imbalances manifest (e.g., low ad quality, high CPCs, missed revenue) and potential actions to restore equilibrium.

Practice these with instant AI feedback in a live mock interview → Start a Google Business Analyst mock

Master DSA and communicate your thinking out loud; use Google's structured Explain-Clarify-Improve approach; prepare for Googleyness/behavioral

Indicative Business Analyst pay in India: ~₹7–26 LPA (role-level range, not a Google-specific figure).

Other roles at Google

Business Analyst interviews at other companies