Google Backend Engineer 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

   In a clean-design discussion, answer this: Design classes for assigning YouTube users to experiments

   MediumLow Level DesignA/B experiment SDK

   How to answer: Model Experiment, Variant, Allocation, EligibilityRule, AssignmentService, and ExposureLogger; use deterministic hashing and log exposures once. Keep APIs small, invariants explicit, and tests first-class.

2. Q2

   For an L5+ style open-ended design round, answer this: Design an experimentation platform for Search

   HardHigh Level DesignA/B testing platform

   How to answer: Use deterministic assignment, experiment config service, exposure logging, metrics pipeline, guardrails, and analysis dashboards; handle mutually exclusive experiments. Call out SLOs, bottlenecks, and data consistency.

3. Q3

   In a clean-design discussion, answer this: Design a reusable API client for Gmail with auth refresh and request signing

   HardLow Level DesignAPI client with auth

   How to answer: Separate HttpClient, AuthProvider, TokenStore, RequestSigner, RetryPolicy, and Serializer; refresh tokens safely and avoid logging secrets. Keep APIs small, invariants explicit, and tests first-class.

4. Q4

   For an L5+ style open-ended design round, answer this: Design an API gateway for Photos backend services

   HardHigh Level DesignAPI gateway

   How to answer: Handle auth, routing, rate limits, request validation, retries/timeouts, observability, and versioning. Keep business logic out of the gateway. Call out SLOs, bottlenecks, and data consistency.

5. Q5

   Clarify assumptions, talk through examples, then solve this: Code a mapper from a raw YouTube API response to a stable internal model

   MediumCodingAPI response mapper

   How to answer: Validate required fields, provide defaults for optional fields, isolate external schema changes, and test unknown fields and backward compatibility. Explain before coding and state Big-O.

6. Q6

   For an L5+ style open-ended design round, answer this: Design an ad-serving system for Maps

   MediumHigh Level DesignAd serving

   How to answer: Separate request routing, candidate retrieval, auction/ranking, budget pacing, frequency capping, logging, and fraud detection; optimize p99 latency. Call out SLOs, bottlenecks, and data consistency.

7. Q7

   Clarify assumptions, talk through examples, then solve this: Infer character order from sorted Android labels in an unknown alphabet

   MediumDSAAlien dictionary

   How to answer: Build precedence edges from first differing characters, then topologically sort. O(total characters); detect invalid prefixes and cycles. Explain before coding and state Big-O.

8. Q8

   In a Googleyness/leadership style discussion, answer this: Tell me about a time you had to deliver a Ads project with ambiguous requirements

   MediumBehavioralAmbiguity

   How to answer: Use STAR: clarify the ambiguity, list options, align stakeholders, deliver an MVP, quantify outcome, and mention what you changed after learning. Tie the story to collaboration, ambiguity, and learning.

9. Q9

   Clarify assumptions, talk through examples, then solve this: Write code to call multiple Maps services concurrently and return partial results safely

   MediumCodingAsync fanout

   How to answer: Use async tasks/futures with per-call timeouts, collect successes and errors separately, limit concurrency, and preserve result ordering if required. Explain before coding and state Big-O.

10. Q10

    In a clean-design discussion, answer this: Design a low-level audit logger for Ads administrative actions

    MediumLow Level DesignAudit log component

    How to answer: Model AuditEvent, Actor, Target, Metadata, Sink, and Redactor; ensure append-only semantics and safe handling of PII. Keep APIs small, invariants explicit, and tests first-class.

11. Q11

    Clarify assumptions, talk through examples, then solve this: Implement autocomplete over a static set of YouTube terms

    HardCodingAutocomplete function

    How to answer: Build a trie or sorted array with binary-search prefix range; return ranked top N; test empty prefix, Unicode, and tie ordering. Explain before coding and state Big-O.

12. Q12

    Clarify assumptions, talk through examples, then solve this: Find the minimum number of connections between two users/devices/items in Ads

    HardDSABFS shortest hops

    How to answer: Use BFS from the source, marking visited nodes and parent if path is needed. O(V+E); consider bidirectional BFS for large graphs. Explain before coding and state Big-O.

13. Q13

    Clarify assumptions, talk through examples, then solve this: Generate all valid configurations for a small Gmail rule set with constraints

    MediumDSABacktracking combinations

    How to answer: Use DFS/backtracking, pruning invalid partial states early. Complexity is exponential; explain pruning and output-size limits. Explain before coding and state Big-O.

14. Q14

    In a Googleyness/leadership style discussion, answer this: Give an example of balancing ship speed and engineering quality for Search

    SeniorBehavioralBalancing speed and quality

    How to answer: State deadline and risks, define acceptable quality bar, ship safe slice, add follow-up debt plan, and measure post-launch outcomes. Tie the story to collaboration, ambiguity, and learning.

15. Q15

    Clarify assumptions, talk through examples, then solve this: Implement a batcher for Maps events that flushes by size or time

    MediumCodingBatching helper

    How to answer: Buffer events, flush when max size or max age is reached, make flush thread-safe, and test empty, timer, size, and failure behavior. Explain before coding and state Big-O.

Practice these with instant AI feedback in a live mock interview → Start a Google Backend Engineer mock

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

Indicative Backend Engineer pay in India: ~₹10–45 LPA (role-level range, not a Google-specific figure).

Other roles at Google

Backend Engineer interviews at other companies