Google Business Analytics Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Google hiring for Business Analytics roles
Google, part of Alphabet, builds products such as Search, YouTube, Android, Google Cloud, Maps and Pay. Its Indian offices contribute to engineering, cloud, payments and research work for local and global products. It hires in India for software engineers, test and reliability engineers, data scientists and analysts who work on large-scale data and experimentation.
For Business Analytics roles, this Google practice set focuses most on Case Studies and Guesstimates (6), SQL for Business Analysis (6), UAT and BA Documentation (6), Requirements and Agile (5). It has 2 easy, 29 medium, 9 hard questions, so you can start easy and work up to the harder ones.
Company type
Product
Headquarters
Mountain View, California, USA
Main India offices
Bengaluru, Hyderabad, Gurugram, Mumbai, Pune
Google Business Analytics interview process
Recruiter screening
Online coding assessment or phone screen
Technical interviews (coding, 3-4 rounds)
Googleyness and leadership round
Hiring committee review
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for GoogleStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
✓ 3 questions free • Unlock the rest in seconds
01
Write an Excel formula for a two-way lookup that finds sales for a given product and month.
Population about 20 million, adult tea drinkers about 50%, cups bought outside per person around 1 on average. This gives roughly 10 million cups, then adjust for offices and stalls.
03
Your AS-IS map of a loan approval process shows 14 handoffs between teams. How do you identify improvements?
First measure each handoff: waiting time, rework rate and volume, using system timestamps where possible. Then classify steps as value-adding, required for compliance or waste. Look for patterns: repeated approvals, information re-entered in two systems, work bouncing back for missing documents. Typical fixes are merging roles, adding a checklist at intake so applications arrive complete, parallelising checks and automating rule-based approvals. Quantify the expected reduction in cycle time for each option.
04
How do you calculate monthly revenue growth in SQL?
Identify which documents are actually used: usually a product overview, process maps, business rules, data dictionary and integration details. Update those first rather than everything. Make documentation part of the Definition of Done, so a story is not complete until related docs are updated. Keep living documents in a shared wiki with owners and last-reviewed dates, and archive outdated files clearly. Test the result by having a new joiner use it during onboarding.
06
Write a SQL query that shows revenue, cost and gross margin percent by product category.
SELECT
p.category,
SUM(oi.quantity * oi.unit_price) AS revenue,
SUM(oi.quantity * p.unit_cost) AS cost,
ROUND(100.0 * (SUM(oi.quantity * oi.unit_price)
- SUM(oi.quantity * p.unit_cost))
/ NULLIF(SUM(oi.quantity * oi.unit_price), 0), 2) AS gross_margin_pct
FROM order_items oi
JOIN products p ON p.product_id = oi.product_id
GROUP BY p.category
ORDER BY gross_margin_pct DESC;
07
A mid-size manufacturer must choose between building and buying a warehouse management system. How do you advise?
Compare options on fit, cost, time and risk. Buying a proven product is faster with lower risk and includes upgrades, but may need process changes and has recurring licence fees. Building fits unique processes exactly but needs a strong tech team, longer time and ongoing maintenance. Estimate five-year total cost of ownership, check whether processes are truly unique, and usually recommend buying and configuring unless warehousing is a core differentiator.
08
How would you analyse the declining sales of a retail store?
Break the change into drivers. Price: were discounts or promotions deeper? Mix: did sales shift towards lower-margin products, channels or regions? Cost: did raw material, freight or supplier prices rise, or did currency movements raise import costs? Also check one-offs like inventory write-offs and accounting reclassifications. Build a margin bridge showing how many percentage points each driver contributed, then take the biggest driver to the business owner with a specific action.
10
How do sample size and minimum detectable effect affect an A/B test design?
The minimum detectable effect is the smallest lift worth detecting, such as a 2 percent relative increase in conversion. Smaller effects, lower baseline rates and higher required power need much larger samples, roughly four times the users to detect half the effect. Calculate sample size before starting using the baseline rate, MDE, significance level and power, usually 80 percent, then fix the test duration and avoid stopping early.
Situation: leadership planned to expand a loyalty programme company-wide. Task: as the analyst, I believed the pilot results were inflated. Action: I showed that pilot stores were already our best performers and built a matched control comparison, which cut the estimated uplift from 15 to 4 percent. I presented it to the sponsor first and proposed a larger randomised pilot. Result: the rollout was redesigned, saving significant cost on a weak programme.
13
Write an Excel formula to count the number of unique customers in a column.
// Excel 365
=COUNTA(UNIQUE(A2:A500))
// unique customers in the North region only
=COUNTA(UNIQUE(FILTER(A2:A500, B2:B500="North")))
// older versions (no blanks in range)
=SUMPRODUCT(1/COUNTIF(A2:A500, A2:A500))
14
What steps would you follow to create an AS-IS process map for a customer refund process?
Define the scope: where the process starts, such as a refund request, and where it ends, such as money credited. Identify the roles involved and draw swimlanes. Interview and observe each role, capturing steps, decisions, systems used, handoffs and time taken. Draw the flow in BPMN, mark pain points like rework loops and waiting time, and add measures such as average refund time. Validate the map with the people who do the work.
15
A critical defect is found on the last day of UAT, and the go-live date cannot move. What do you do?
Confirm the impact and reproduce it quickly. Work with development to estimate a fix and its regression effort. Then present options to the business owner with risks: fix and do targeted retesting before go-live, go live with a temporary workaround or manual process, go live with the affected feature switched off, or delay. The decision belongs to the business, documented at the go or no-go meeting. Never hide a critical defect to protect a date.
16
A business head wants 25 charts on one dashboard page. How do you respond?
Ask what decisions they make weekly and which three to five KPIs drive them. Propose a summary page with those KPIs, trends and one breakdown, then drill-through or separate pages for detail. Show a quick mock-up of both versions so they see the clutter and the load time. Use bookmarks or a field parameter to let them switch views without adding charts. Agree on the layout before building.
17
Write a SQL query to find the percentage of orders delivered late in each city.
-- late = delivered after the promised date
SELECT
city,
COUNT(*) AS total_orders,
SUM(CASE WHEN delivered_at > promised_at THEN 1 ELSE 0 END) AS late_orders,
ROUND(100.0 * SUM(CASE WHEN delivered_at > promised_at THEN 1 ELSE 0 END)
/ COUNT(*), 2) AS late_pct
FROM orders
WHERE status = 'DELIVERED'
GROUP BY city
ORDER BY late_pct DESC;
// second highest value
=LARGE(C2:C100, 2)
// rep name for that value
=INDEX(B2:B100, MATCH(LARGE(C2:C100, 2), C2:C100, 0))
// with ties, SORTBY gives a clean list:
=TAKE(SORTBY(B2:C100, C2:C100, -1), 2)
20
An order has a value of 600 rupees, product cost 360, delivery 60, payment fee 12 and a discount of 50. What is the contribution margin?
Net revenue after discount is 600 minus 50, which is 550 rupees. Variable costs are 360 plus 60 plus 12, totalling 432. Contribution margin is 550 minus 432, so 118 rupees per order, or about 21 percent of net revenue. This is what each order contributes towards fixed costs such as salaries and rent. If the discount were raised to 150, the order would contribute only 18 rupees.
Users are coming but not completing transactions, so look at the gap. Possible causes: a release that broke a payment flow, new security steps like extra OTPs adding friction, logins driven by balance checks or offers, or transactions shifting to another channel. Compare the funnel from login to transaction by app version and device, check failure and error rates, and review support complaints before recommending fixes.
23
What is User Acceptance Testing (UAT) and what is the BA's role in it?
UAT is the final testing phase where real business users check that the system supports their work and meets requirements before go-live. The BA helps plan UAT, prepares business scenarios and test cases from requirements, arranges test data, supports users during testing, triages defects versus change requests and tracks sign-off. UAT is not about finding code bugs, which earlier testing should have caught.
24
Tell me about a time you mapped a process and discovered a major inefficiency.
Situation: vendor onboarding at my company took around 18 days and procurement blamed finance. Task: I was asked to map the AS-IS process. Action: I interviewed five roles, traced 25 recent vendor records through system timestamps and built a swimlane map. It showed that bank details were collected twice and verified by two teams separately. Result: we merged the steps into one checklist at intake, cut onboarding to 9 days and reduced rework emails by about half.
25
A business tester raises a defect, and the developer closes it as 'works as designed'. How do you resolve it?
Go back to the requirement and acceptance criteria. If the system matches the agreed requirement, the developer is right, and the business need is a change request. If the requirement is unclear or the design misread it, it is a defect, and the requirement wording should be fixed. Discuss it in triage with both parties, using examples. Either way, close the loop with the tester so they understand the outcome and keep trusting the process.
26
Explain exclusive, parallel and inclusive gateways in BPMN.
An exclusive gateway (diamond with X) sends the flow down exactly one path based on a condition, for example approved or rejected. A parallel gateway (diamond with +) splits into all paths at once and, when joining, waits for every path to finish. An inclusive gateway (diamond with O) activates one or more paths whose conditions are true and joins only those that were activated. Choosing the wrong one causes deadlocks or duplicated work in automated processes.
27
Your analysis contradicts a strongly held belief of the vice president. How do you handle it?
Double-check the data and method first, and ask a peer to review it. Then share it privately with the VP before any group meeting, so they are not surprised in public. Present it neutrally: what we expected, what the data shows, and possible reasons. Invite their context, as they may know factors you missed. Suggest a small test to settle it. Focus on the decision, not on being right.
28
What is the hierarchy of epic, feature and user story in Agile?
An epic is a large body of work that delivers a major business goal and spans several sprints, such as 'Online loan application'. It is broken into features or capabilities, such as 'Document upload'. Each feature is split into user stories small enough to finish in one sprint, such as 'As an applicant, I want to upload my PAN card photo so that I do not need to visit a branch'.
29
What are MRR and ARR, and how do you calculate net revenue retention?
MRR is monthly recurring revenue from active subscriptions; ARR is the annualised figure, usually MRR times 12. Net revenue retention measures revenue kept from an existing customer cohort over 12 months: (starting MRR + expansion - contraction - churned MRR) / starting MRR. Example: 100 lakh start, plus 15 expansion, minus 5 contraction, minus 8 churn gives 102 percent. Above 100 percent means existing customers grow revenue even without new sales.
30
Revenue grew but profit fell. Why could that happen?
Look at the cost side: heavier discounts, higher CAC, logistics costs, product mix shifting to low-margin items, one-time expenses or pricing changes. Break contribution margin down by segment.
31
Two analysts report different monthly active user numbers from the same database. How do you resolve it?
Put both queries side by side and compare definitions: which events count as active, time zone, calendar versus rolling month, test and internal accounts, deleted users, and DISTINCT on user ID versus device ID. Run both on a single day to find where they diverge. Agree on one definition with the metric owner, document it, and publish it as a shared view or metric so everyone queries the same logic.
32
What sections does a good software requirements specification (SRS) contain?
A typical SRS includes purpose, scope and definitions; overall description with users, operating environment, assumptions and constraints; functional requirements, each with a unique ID, description, priority and acceptance criteria; external interface requirements for UI, APIs and integrations; non-functional requirements such as performance, security, availability and compliance; data requirements; and appendices with diagrams and a traceability reference. Each requirement should be clear, testable and traceable to a business need.
33
What is the difference between UNION and UNION ALL?
Both stack the results of two queries with the same number and type of columns. UNION removes duplicate rows, which needs a sort or hash step and is slower. UNION ALL keeps every row and is faster. Use UNION ALL when combining data such as online and store sales where duplicates are genuine or impossible, and UNION only when you specifically need a distinct list, such as unique customer IDs from two sources.
34
During UAT, users log 60 defects, but you suspect many are actually new requirements. How do you handle it?
Run a joint triage with the business owner, QA and development. Compare each item against the signed-off requirements and acceptance criteria. Real defects stay in the defect log; items not covered by requirements are reclassified as change requests and prioritised separately through change control. Keep the tone neutral so users do not feel dismissed. Also review why the gap happened, for example prototypes were not shown early enough, and fix that for the next release.
35
Describe a BPMN model for a purchase order process where credit check and stock check happen at the same time.
Start event: purchase order received. Task: validate order details. A parallel gateway then splits into two paths: Finance lane runs Check customer credit, Warehouse lane runs Check stock. A second parallel gateway joins them, waiting for both to complete. An exclusive gateway then decides: credit OK and stock available goes to Confirm order and Schedule dispatch; otherwise go to Notify customer with reason. Using a parallel join here is correct because both results are always needed.
36
Write non-functional requirements for an online payment page.
NFR-01 Performance: the payment page loads within 2 seconds for 95 percent of requests at 500 concurrent users. NFR-02 Availability: 99.9 percent monthly uptime outside planned maintenance. NFR-03 Security: card data is never stored by the application, and all traffic uses TLS 1.2 or higher. NFR-04 Compliance: the flow meets PCI DSS and RBI payment guidelines. NFR-05 Usability: works on mobile screens from 360 pixels wide. NFR-06 Audit: every transaction attempt is logged with a timestamp.
37
What steps would you follow to create a tracking plan for a new 'save for later' feature?
Start from the questions to answer: how many users discover it, use it and later buy saved items. Define events such as save_clicked, saved_item_viewed, saved_item_removed and saved_item_purchased, with properties like product ID, price, source screen and platform. Follow the existing naming convention, assign owners, review with developers, and test events in a staging build. Build the dashboard before launch so data is checked on day one.
38
Write a SQL query that shows revenue per region with one column per quarter.
SELECT region,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 1 THEN amount ELSE 0 END) AS q1,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 2 THEN amount ELSE 0 END) AS q2,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 3 THEN amount ELSE 0 END) AS q3,
SUM(CASE WHEN EXTRACT(QUARTER FROM order_date) = 4 THEN amount ELSE 0 END) AS q4
FROM orders
WHERE EXTRACT(YEAR FROM order_date) = 2026
GROUP BY region;
39
Write a SQL query to find requirements that have no linked UAT test case.
SELECT r.req_id, r.title, r.priority
FROM requirements r
LEFT JOIN test_case_links l ON l.req_id = r.req_id
WHERE l.req_id IS NULL
AND r.status = 'APPROVED'
ORDER BY r.priority;
-- Run this before UAT starts: every approved requirement
-- should trace to at least one test case.
40
What is normalisation, and why are analytics tables often denormalised?
Normalisation splits data into related tables to remove redundancy and update anomalies, which suits transactional systems that write often. Analytics workloads read far more than they write, so warehouses often denormalise into wide fact and dimension tables or star schemas. That reduces joins, makes queries simpler for analysts and speeds up aggregation, at the cost of extra storage and the need for controlled loading pipelines.
Tips to crack the Google Business Analytics interview
Practise solving DSA problems in a plain document without autocomplete, since Google interviews often use a shared editor without running code.
For data science roles, revise statistics, A/B testing and product metrics for products like YouTube, Search or Google Pay.
Prepare examples showing collaboration, handling ambiguity and doing the right thing, which the Googleyness round tends to explore.
Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
Practise the hard questions on this page aloud; Google interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Google Business Analytics interview?
Candidates usually go through 5 stages: Recruiter screening; Online coding assessment or phone screen; Technical interviews (coding, 3-4 rounds); Googleyness and leadership round; Hiring committee review. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Google Business Analytics interview?
This practice set leans on Case Studies and Guesstimates (6), SQL for Business Analysis (6), UAT and BA Documentation (6), Requirements and Agile (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Google interviewers ask you to walk through real work.
Are these the exact questions asked at Google?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Google's. They are not a leaked or verified list of past questions.
Where does Google hire Business Analytics professionals in India?
Google has large teams in Bengaluru, Hyderabad, Gurugram, Mumbai, Pune. Openings and locations change often, so check the Google careers page and filter by city and experience.
Business Analytics questions for similar companies