Unite Wings

Google interview questions

14 questions candidates report from Google interviews, plus the general HR questions every interviewer asks. Each has a model answer and the follow-ups to expect.

Typical selection process

Online challenge or recruiter screen, then technical phone screens and onsite rounds on algorithms and data structures, plus a Googleyness and leadership round.

As reported by recent candidates. Always check the latest official notification.

31 questions

HRMotivationEasy

Why do you want to work at Google?

Reported at Google

What they are checking: Genuine motivation rather than prestige.

Model answer

I want to work on problems where good engineering makes a difference at huge scale. When I was learning Android development, I was struck by how a small optimisation in a Google library could save battery for billions of phones.

I also like Google's engineering culture: code review on every change, design docs before big work, and a strong habit of writing things down. In my internship I saw how much faster a team moves when decisions are documented, and I want to learn that discipline properly.

Specifically, I'm interested in [Android / Cloud / Search infrastructure] because [one concrete reason].

Tips

  • Be specific about a product or team. "Google is a great company" is not a reason.
BehaviouralCourageHard

Tell me about a time you disagreed with your manager, professor or team lead.

Reported at Amazon, Microsoft, Google

What they are checking: At Amazon this maps to "Have Backbone; Disagree and Commit". They want respectful challenge backed by data, and full commitment once a decision is made.

Model answer

During my internship my team lead wanted to cache the entire product catalogue in memory to speed up search. I was worried because the catalogue was growing about 10% a month and our servers had limited memory.

I didn't just object. I measured it: the catalogue was 1.2 GB, and at that growth rate it would exceed the server's free memory in about five months. I shared those numbers in a short doc and suggested caching only the top 5,000 most-searched products, which covered about 80% of queries according to our logs.

My lead agreed to try my version first. Search time dropped from 800 ms to around 120 ms for most users, and memory use stayed flat. Had he decided to cache everything anyway, I would have committed to it and set up a memory alert so we'd know before it became a problem.

Tips

  • Disagree with data, not opinion.
  • Show that you would commit fully even if the decision went the other way.

Likely follow-ups

  • What if the data had supported your lead?
  • What did you do about the other 20% of queries?
BehaviouralProblem solvingHard

What is the most technically challenging problem you have solved?

Reported at Google, Microsoft, Amazon

What they are checking: Depth. They will keep asking "why" until they reach the limit of what you know, so pick something you understand completely.

Model answer

In my internship, our app's order page sometimes showed duplicate orders, roughly 1 in 500. Nobody could reproduce it locally.

I added logging with request IDs and found that duplicates always came in pairs about 300 ms apart. The mobile app retried a request whenever the network was slow, and our server processed both requests because it had no way to tell they were the same order.

I proposed an idempotency key: the app generates a unique ID per order, and the server stores it with a unique constraint in the database. A second request with the same ID returns the original order instead of creating a new one. I wrote the migration, the server change and tests that simulated the retry.

Duplicate orders went to zero over the following month. The thing I learned is to reproduce with data from production before guessing at a fix.

Likely follow-ups

  • Why a database constraint and not a check in code?
  • How long do you keep the idempotency keys?
  • What happens if two requests arrive at exactly the same moment?
BehaviouralGoogleynessMedium

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

Reported at Google

What they are checking: Googleyness: collaboration, humility and doing the right thing for the team.

Model answer

In our fifth-semester project, one teammate stopped turning up to our meetings and his part, the database layer, was falling behind.

Instead of complaining to our professor, I messaged him privately. He told me he was struggling with SQL joins and was embarrassed to say so. We did two one-hour sessions where I walked through joins using our own tables, and I paired with him on the first few queries.

He finished his part on time, and later he was the one who fixed a tricky query bug before our demo. I learned that when someone goes quiet, there's usually a reason, and asking privately works better than pressure.

TechnicalNetworkingHard

What happens when you type a URL into the browser and press Enter?

Reported at Google, Microsoft, Amazon, Flipkart

What they are checking: Breadth across networking, the web and browsers. Go step by step, and go deep where you are strongest.

Model answer

  1. URL parsing: the browser works out the protocol (https), the domain and the path.
  2. DNS lookup: it finds the IP address of the domain, checking the browser cache, the OS cache, the router and then the ISP's DNS resolver, which may query root, TLD and authoritative name servers.
  3. TCP connection: the browser opens a connection to the IP on port 443 with a three-way handshake (SYN, SYN-ACK, ACK).
  4. TLS handshake: browser and server agree on encryption, the server proves its identity with a certificate, and they set up session keys.
  5. HTTP request: the browser sends GET /path with headers such as cookies and accepted formats.
  6. Server side: a load balancer passes the request to an app server, which may check a cache, query a database and build the response.
  7. HTTP response: status code, headers and the HTML body come back.
  8. Rendering: the browser parses HTML into the DOM and CSS into the CSSOM, runs JavaScript, then lays out and paints the page. Extra requests are made for images, scripts and stylesheets, often from a CDN.

Interviewers usually stop you at one step and ask for more depth, most often DNS, TLS or rendering.

Likely follow-ups

  • How does DNS caching work?
  • What is a CDN?
  • What changes with HTTP/2?
TechnicalCodingEasy

Given an array and a target, return the indices of two numbers that add up to the target.

Reported at Amazon, Google, Microsoft, Flipkart

What they are checking: Whether you move from the brute-force O(n²) solution to a hash map.

Model answer

Brute force checks every pair: O(n²). Better: as you scan, store each number's index in a hash map, and for each number check whether target minus that number has already been seen. O(n) time, O(n) space.

def two_sum(nums, target):
    seen = {}
    for i, x in enumerate(nums):
        if target - x in seen:
            return [seen[target - x], i]
        seen[x] = i
    return []

print(two_sum([2, 7, 11, 15], 9))   # [0, 1]

If the array is sorted, two pointers from both ends solve it in O(n) time and O(1) space.

Likely follow-ups

  • What if there are many pairs and you must return all of them?
  • Solve three-sum.
TechnicalCodingHard

Design and implement an LRU (least recently used) cache with O(1) get and put.

Reported at Amazon, Microsoft, Flipkart, Google

What they are checking: Combining data structures: a hash map for lookup and a doubly linked list for order.

Model answer

Use a hash map from key to node, plus a doubly linked list ordered by recent use. On get, move the node to the front. On put, insert at the front; if over capacity, remove the node at the back and delete its key from the map. Every operation is O(1).

In Python, OrderedDict is a hash map with a linked list inside, so it shows the idea compactly:

from collections import OrderedDict

class LRUCache:
    def __init__(self, capacity):
        self.capacity = capacity
        self.data = OrderedDict()

    def get(self, key):
        if key not in self.data:
            return -1
        self.data.move_to_end(key)
        return self.data[key]

    def put(self, key, value):
        if key in self.data:
            self.data.move_to_end(key)
        self.data[key] = value
        if len(self.data) > self.capacity:
            self.data.popitem(last=False)

Most interviewers will then ask you to write the doubly linked list yourself. Use dummy head and tail nodes so you never have to handle an empty list as a special case.

Likely follow-ups

  • Write it without OrderedDict.
  • How would you make it thread-safe?
  • How is LFU different?
TechnicalCodingHard

Numbers arrive one at a time. Return the median at any point.

Reported at Google, Amazon

What they are checking: The two-heap technique and keeping invariants.

Model answer

Keep two heaps: a max-heap for the smaller half and a min-heap for the larger half, balanced so the max-heap has the same number of elements or one more. The median is the top of the max-heap, or the average of both tops. Adding is O(log n); reading the median is O(1).

import heapq

class MedianFinder:
    def __init__(self):
        self.low = []    # max-heap, stored as negatives
        self.high = []   # min-heap

    def add(self, num):
        heapq.heappush(self.low, -num)
        heapq.heappush(self.high, -heapq.heappop(self.low))
        if len(self.high) > len(self.low):
            heapq.heappush(self.low, -heapq.heappop(self.high))

    def median(self):
        if len(self.low) > len(self.high):
            return -self.low[0]
        return (-self.low[0] + self.high[0]) / 2

Pushing into low and then moving its top to high guarantees every element in low is at most every element in high.

TechnicalStatisticsMedium

Explain correlation versus causation with an example.

Reported at Amazon, Google, Flipkart

What they are checking: Whether you will over-claim from data.

Model answer

Correlation means two things move together; causation means one actually causes the other.

Example: users who use the wishlist feature spend 3 times more. That doesn't prove the wishlist makes people spend more. Keen shoppers may simply be more likely to use every feature. This is a confounding variable: shopping intent drives both.

To show causation you need an experiment: randomly show the wishlist to half of new users and compare their spending. If that isn't possible, techniques such as comparing before and after with a control group (difference-in-differences) or matching similar users get closer, but I'd state the limitation clearly.

TechnicalExperimentationMedium

How would you design an A/B test for a new checkout button?

Reported at Amazon, Flipkart, Google, Microsoft

What they are checking: End-to-end experimental thinking.

Model answer

  1. Hypothesis: a bigger, green "Buy now" button will increase checkout completion.
  2. Primary metric: checkout conversion rate. Guardrail metrics: refund rate, page load time, average order value, to catch harmful side effects.
  3. Randomisation: split users (not sessions) randomly 50/50, so the same person always sees the same version.
  4. Sample size: calculate it before starting from the current conversion rate, the smallest lift worth detecting (say 2%), 95% confidence and 80% power.
  5. Duration: run whole weeks, usually at least two, to cover weekday and weekend behaviour.
  6. Analysis: check the split was actually 50/50, then test for significance. Don't stop early just because the result looks significant on day 3; peeking inflates false positives.
  7. Decision: ship if the primary metric improves significantly and no guardrail gets worse.

Likely follow-ups

  • The result is significant but the lift is 0.1%. Ship it?
  • What if mobile and desktop show opposite results?
TechnicalProduct senseMedium

What is your favourite product, and how would you improve it?

Reported at Google, Microsoft, Flipkart, Amazon

What they are checking: Product thinking: users, problems and trade-offs, not just features you like.

Model answer

My favourite is Google Maps, specifically for commuting in Indian cities.

Why it works: it solves a daily, high-stakes problem (being late) for almost everyone, the live traffic data improves as more people use it, and features like two-wheeler mode show it was designed for Indian users, not just copied from the US.

One improvement: shared autos and local buses in tier-2 cities. In my hometown most people commute by shared auto, and Maps simply has no information on them.

  • User: daily commuters in tier-2 cities without metro systems.
  • Solution: let users mark shared-auto stands and routes, verified by others, as Maps already does for places.
  • Success metric: increase in weekly active transit users in those cities, plus the share of route searches that end in a transit route.
  • Risk: data quality. I'd launch in two cities first and only show routes confirmed by several users.

Tips

  • Pick a product you actually use.
  • Name a specific user segment and how you'd measure success.
TechnicalAnalyticalHard

Daily active users of our app fell 10% this week. What do you do?

Reported at Google, Amazon, Flipkart, Microsoft

What they are checking: The classic root-cause question: calm, structured, hypothesis-driven.

Model answer

  1. Clarify: is it a sudden drop or gradual? Is it 10% compared with last week or the same week last year? How is a daily active user defined, and did that change?
  2. Rule out data issues: logging changes, a broken analytics SDK in a new release, delayed data.
  3. Check external causes: holidays, exams, a competitor launch, an outage at a cloud provider or app store.
  4. Segment: platform (Android/iOS/web), app version, country or city, new versus existing users, acquisition channel. If the drop is only in the latest Android version, it's probably a bug or crash.
  5. Walk the user journey: did app opens drop (a notification or marketing issue), or do users open but fail somewhere (a login or loading problem)?
  6. Check internal changes in the window: releases, experiments, pricing, notification changes.

Then I'd form a hypothesis, confirm it with data (such as crash rates for that version), fix or roll back, and set up an alert so we catch it faster next time.

TechnicalProduct designHard

Design a product that helps elderly people manage their medicines.

Reported at Google, Microsoft, Amazon

What they are checking: The product design framework: users, needs, solutions, prioritisation, metrics.

Model answer

1. Clarify the goal: I'll assume the goal is fewer missed doses, for elderly people living alone or with working children in India. 2. Users: the elderly person (may have poor eyesight, limited smartphone skills, possibly a basic phone), the family caregiver (often in another city, worried), and the pharmacist or doctor. 3. Pain points: forgetting doses, confusing similar-looking pills, running out of medicine, family not knowing whether medicine was taken. 4. Solutions: - Voice reminders by phone call in their language, which works on any phone. - A pill box with lights for each slot that confirms when opened. - A caregiver app showing taken and missed doses, with an alert after a missed dose. - Automatic refill reminders with pharmacy delivery. 5. Prioritise: for a first version, voice-call reminders plus the caregiver app. They're cheap to build, need no new hardware and address the biggest risk, missed doses. 6. Metrics: dose adherence rate (doses confirmed out of doses scheduled), weekly active caregivers, refill orders, and retention after 90 days. 7. Risks: privacy of health data, and over-reliance; serious missed doses should prompt a call from family, not just an app notification.

TechnicalMetricsMedium

How would you measure the success of a new "Buy Now, Pay Later" option at checkout?

Reported at Amazon, Flipkart, Google

What they are checking: Choosing a north star metric plus guardrails.

Model answer

Goal: increase completed purchases without increasing financial risk.

  • Primary metric: checkout conversion rate for users who are shown the option, compared with a control group.
  • Supporting metrics: share of orders using pay-later, average order value (it often rises), repeat purchase rate.
  • Guardrail metrics: default and late-payment rate, return and cancellation rate on pay-later orders, customer support complaints, and the cost per transaction charged by the lending partner.

I'd run it as an A/B test and segment results by new and existing users and by order value, because pay-later may help mostly on high-value items like phones. Success would be a meaningful lift in conversion while defaults stay within the threshold agreed with the risk team.

HRIntroductionEasy

Tell me about yourself.

What they are checking: Can you give a short, structured story that connects your background to this job? It sets the agenda for the rest of the interview, so whatever you mention here becomes the next question.

Model answer

I'm [name], a final-year B.Tech Computer Science student at [college], graduating in 2026 with a CGPA of [8.1].

Over the last two years I have focused on backend development. My main project is a hostel complaint tracker built with Node.js and PostgreSQL that 400 students in my hostel now use. I also did a two-month internship at [company], where I wrote REST APIs and cut a slow report query from 9 seconds to under 1 second by adding the right indexes.

Outside class I solve problems on LeetCode, around 300 so far, and I coordinate our college coding club, where I run weekly contests for juniors.

I'm applying here because I want to work on systems that real users depend on, and this role gives me that from day one.

Tips

  • Use present, past, future: who you are, what you have done, why this job.
  • Keep it under 90 seconds. Mention only things you are happy to be questioned on.
  • Do not repeat your resume line by line, and skip family details unless asked.

Likely follow-ups

  • Tell me more about the complaint tracker. What was hardest?
  • Why did you add indexes rather than caching?
HRSelf-awarenessEasy

What are your strengths?

What they are checking: Whether you know what you are good at and can prove it with an example, rather than listing adjectives.

Model answer

My biggest strength is that I break unfamiliar problems into small pieces and keep going until they work.

In my second year our team had to build an attendance app using face recognition, and none of us had used OpenCV. I split the work into three parts: capturing images, training the model, and matching faces in real time. I took the matching part, read the documentation and two tutorials over a weekend, and had a working version in five days. We demoed it at the department expo and it marked attendance for a class of 60 with about 95% accuracy.

I'd bring the same habit here when I'm handed a codebase or tool I haven't used before.

Tips

  • Pick one or two strengths that matter for the role.
  • Every strength needs a short story with a result.

Likely follow-ups

  • What would your teammates say is your strength?
  • What did you do about the 5% the app got wrong?
HRSelf-awarenessMedium

What is your greatest weakness?

What they are checking: Honesty and self-improvement. They want a real weakness that will not stop you doing the job, plus what you are doing about it.

Model answer

I used to find it hard to say no when people asked for help, and I would take on more than I could finish.

In my third year I agreed to help with three club events in the same month as my mid-semester exams, and my marks in one subject dropped. Since then I have started keeping a simple weekly plan in Notion. Before I agree to something new I check it against what is already there, and if it does not fit I offer a smaller piece or a later date.

This semester I managed the coding club contest and my project deadlines without missing either. I still have to watch it, but I catch it much earlier now.

Tips

  • Avoid fake weaknesses like "I'm a perfectionist" or "I work too hard".
  • Never name a weakness that is core to the job, such as weak coding for a developer role.
  • Spend most of the answer on what you changed.

Likely follow-ups

  • Give me another weakness.
  • How would you handle a manager who keeps adding work?
HRCareer goalsEasy

Where do you see yourself in five years?

What they are checking: Whether your plans fit this company and whether you are likely to stay long enough to repay the training.

Model answer

In five years I want to be someone my team relies on for a whole area of the product, not just individual tasks.

For the first two years I want to get really good at the technology I'm assigned, earn a certification in it, and understand how our client's business works. After that I'd like to lead a small module, review juniors' code and talk directly with the client.

This company's training and the range of projects here make that path realistic, which is a big reason I applied.

Tips

  • Show growth inside the company.
  • Do not say you plan to leave for an MBA or a startup.
HRFitMedium

Why should we hire you?

What they are checking: Can you match your skills to what the job needs, in a confident but not arrogant way?

Model answer

From the job description, you need someone who can write clean code in Java, work with databases, and learn new tools quickly.

I have used Java for three years and built two projects with Spring Boot and MySQL, one of which is used by 400 students. During my internship I learned a reporting tool I had never seen, in a week, and shipped a feature with it.

I also communicate clearly. I explain concepts to juniors every week in our coding club, which will help when I work with teammates and clients. I'm ready to start contributing early and keep learning.

Tips

  • Read the job description and reuse its words.
  • Give three reasons, each with evidence.
HRClosingEasy

Do you have any questions for us?

What they are checking: Interest and preparation. Saying "No" signals that you have not thought about the job.

Model answer

Yes, two questions.

First, what does the first six months look like for a fresher in this role? I'd like to know how training and project allocation work so I can prepare in advance.

Second, what do the freshers who do best here have in common? I want to know what to focus on from day one.

Tips

  • Ask about the work, training, team or success in the role.
  • Skip questions on salary, leave or work from home in early rounds unless the interviewer raises them.
  • Never ask something that is on the first page of their website.
0students
taking off