Google interview process and practice questions

Behavioral questions

1. Tell me about a time you had to work through a problem with no clear owner or direction.

   A good answer covers

   • Why nobody owned it and what it would cost if nobody acted
   • How you created structure: defined the problem, found the right people, agreed next steps
   • What happened, and what you'd do the same or differently

2. Tell me about a time you helped a teammate who was struggling.

   A good answer covers

   • How you noticed, and what was really getting in their way
   • What you did that helped without taking over their work
   • How they and the work were doing afterwards

3. Tell me about a time you changed your mind after getting new information.

   A good answer covers

   • Your original view and why it was reasonable at the time
   • The data or argument that changed it
   • How you told others and what changed in the work

4. Tell me about a time you led something without having any formal authority.

   A good answer covers

   • The goal and why people didn't have to follow you
   • How you brought them along: listening, a clear plan, sharing credit
   • The outcome and what you learned about leading peers

Role and technical questions

1. How would you estimate how many people use Google Maps on a weekday morning in Bengaluru?

   A good answer covers

   • A clear structure: population, share with smartphones, share travelling in the morning, share who open Maps
   • Assumptions stated out loud with round numbers, and a sanity check at the end
   • Which assumption moves the answer most, and how you'd check it with data

2. Walk me through the hardest technical decision you've made and the trade-offs you weighed.

   A good answer covers

   • The options you had and the constraints: time, scale, team skills, cost
   • How you compared them: data, a prototype, or advice from others
   • What you chose, what it cost you, and whether it held up later

3. How would you design a service that suggests search queries as someone types?

   A good answer covers

   • Requirements first: latency per keystroke, languages, freshness, personalisation
   • A prefix index ranked by popularity, with caching close to users
   • Filtering harmful suggestions, and how you'd measure whether suggestions help

4. A web page loads slowly for some users but not for others. How would you find out why?

   A good answer covers

   • Splitting by region, device, network and browser before guessing
   • Evidence from browser timings, server logs and tracing across services
   • Likely causes such as a slow dependency, a cache miss or heavy assets, and how you'd confirm one

5. How would you remove duplicates from a list too large to fit in memory? Talk me through the trade-offs.

   A good answer covers

   • The in-memory answer first, such as a hash set, and its time and space cost
   • Scaling out: sorting in chunks and merging, or hashing records into partitions
   • Approximate options like a Bloom filter when a small error rate is acceptable

6. How would you improve Google Maps for people who travel mostly by bus or metro?

   A good answer covers

   • One user group and its biggest pain points, such as waiting times or crowding
   • Two or three ideas, ranked by impact and effort
   • A success metric, plus a guardrail so other users aren't worse off

7. How would you test whether a change to search results actually made them better for users?

   A good answer covers

   • Defining 'better': one main metric plus guardrails such as speed
   • An experiment design: who is in it, how long it runs, how large it must be
   • Watching for novelty effects and differences between user groups

Why Google? Fit and HR questions

1. Why Google, and which product or team would you most like to work on?

   A good answer covers

   • A specific product or team and the problem it solves
   • Something you've built or studied that connects to it
   • What you hope to learn or contribute there

2. Which Google product do you use most, and what would you change about it?

   A good answer covers

   • A product you know well and one clear problem with it
   • The change, who it helps, and what you'd leave out
   • How you'd know it worked

3. Where do you want your career to be in a few years, and how would this role help?

   A good answer covers

   • A realistic direction: the skills or scope you want to grow into
   • How this role builds towards it
   • What you'd bring to the team along the way

Tips

• Think out loud: they score how you reason, not only the answer.
• State assumptions, then test them; ask clarifying questions before you dive in.
• For coding, talk through complexity and edge cases before you write.
• Candidates commonly report coding in a plain shared doc: practise writing clean code without autocomplete or running it.
• For the Googleyness and leadership interview, prepare stories about ambiguity, helping others and leading without a title.
• Google says it scores structured interviews against rubrics, so answer the question you were asked fully before adding extras.