Google Software Engineer Interview Questions

Google Software Engineer interview questions typically test core algorithmic problem solving, clean coding under time pressure, and — for mid-to-senior levels — system design and scalability thinking. The process is multi-stage: a recruiter screen followed by one or two timed technical screens (often live coding on a shared Google Doc), then a virtual or onsite loop with several 45-minute interviews that mix coding, design (L4/L5+), and behavioral “Googleyness” assessments. Interviewers evaluate general cognitive ability, role-related technical depth, leadership, and culture fit, and candidates should expect iterative feedback and a hiring-committee review before team matching. ([leetcopilot.dev](https://leetcopilot.dev/blog/google-coding-interview-guide-2026?utm_source=openai)) For interview preparation focus on timed practice of data-structures and algorithms, simulate coding on Google Docs, and prepare concise STAR-style stories that show impact and collaboration; senior candidates must add targeted system-design drills that discuss trade-offs, reliability, and scaling. Allow several weeks of structured practice, rehearse clear verbal explanations, and be ready to ask clar

301 Questions 1 Company08.01.2026
Showing 20 results
Role
Google logo
Google
Medium
Software EngineerIntern

Answer project deep-dive and Why Google questions

Scenario This round is conversational (no coding). The interviewer asks about: - One or more personal projects (deep dive) - Internship experience and...

Behavioral & Leadership
11
0
93 people solved
Jan 6, 2026
Google logo
Google
Medium
Software Engineer Locked

Implement matrix transforms and discuss eigenvalues

This question evaluates understanding of matrix manipulation and numerical linear algebra, including in-place matrix transforms and rotations, sparse ...

Software Engineering Fundamentals
4
0
56 people solved
Feb 7, 2026
Google logo
Google
Medium
Software Engineer Locked

Boolean Expression Tree with Leaf Flips

This question evaluates a candidate's ability to work with tree data structures and apply efficient update propagation techniques. It tests practical ...

Coding & Algorithms
6
0
26 people solved
Jun 9, 2026
Google logo
Google
Medium
Software Engineer

Design an elevator control system

Design the software for a multi-elevator control system in a high-rise building. Specify classes, scheduling algorithms for car assignments, handling ...

Coding & Algorithms
9
0
106 people solved
Sep 6, 2025
Google logo
Google
Hard
Software Engineer

Design line-preserving file chunker pipeline

System Design: Pack Text Lines into Exact 100 MB Output Files Design a data pipeline that reads many text files of varying sizes and emits output file...

System Design
6
0
107 people solved
Sep 6, 2025
Google logo
Google
Medium
Software Engineer

Find Players with Uniquely Determined Rankings

Find Players with Uniquely Determined Rankings Problem There are n players numbered 0 through n - 1. Each result (winner, loser) states that the winne...

Coding & Algorithms
1
0
10 people solved
Apr 19, 2026
Google logo
Google
Medium
Software Engineer

Determine validity after digit-constrained deletions

Determine validity after digit-constrained deletions You're given a string S of length n consisting only of '(' , ')' , and digits '0'–'9'. For every ...

Coding & Algorithms
14
0
161 people solved
Aug 8, 2025
Google logo
Google
Medium
Software Engineer

Choose Fast or Cheap Models

You are building an AI-powered product and must choose between two inference options for each request: - Option A: higher cost per token, but lower la...

ML System Design
12
0
100 people solved
Jan 10, 2026
Google logo
Google
Medium
Software Engineer Locked

Design nearest-available-taxi lookup with updates

This question evaluates the ability to design scalable, low-latency geospatial lookup services under high update and query rates, assessing skills in ...

System Design
14
0
197 people solved
Jan 10, 2026
Google logo
Google
Hard
Software EngineerSenior+

Convert Valid Snake Case to Lower Camel Case

Convert Valid Snake Case to Lower Camel Case Given a valid snake-case identifier, convert it to lower camel case. The input consists of one or more lo...

Coding & Algorithms
3
2
18 people solved
Apr 16, 2026
Google logo
Google
Medium
Software Engineer

Troubleshoot CPU, latency, and DNS issues

A) A Linux server’s CPU usage suddenly spikes. What immediate checks and commands would you run (e.g., top/htop, pidstat, perf, iostat), how would you...

Coding & Algorithms
6
0
104 people solved
Sep 6, 2025
Google logo
Google
Medium
Software Engineer Locked

Implement text wrapping, waitlist, and intervals

This question evaluates skills in string parsing and word-wrapping logic, data-structure design for FIFO queue management and deletions, and interval ...

Coding & Algorithms
19
0
152 people solved
Feb 12, 2026
Google logo
Google
Easy
Software Engineer Locked

Compute decayed power levels in a graph

This question evaluates knowledge of graph algorithms and distance-based propagation, testing concepts such as shortest-path distance computation, mul...

Coding & Algorithms
18
0
151 people solved
Feb 12, 2026
Google logo
Google
Hard
Software Engineer

Answer core teamwork and conflict stories

You are in a behavioral interview. Prepare to answer the following prompts using concrete examples from your experience. Prompts 1. Describe a challen...

Behavioral & Leadership
20
0
169 people solved
Jan 22, 2026
Google logo
Google
Medium
Software Engineer

Find the Largest Monotone Increasing Number

Find the Largest Monotone Increasing Number Problem Given a non-negative integer n, return the largest integer less than or equal to n whose decimal d...

Coding & Algorithms
6
1
18 people solved
Jul 4, 2026
Google logo
Google
Medium
Software Engineer

Check Whether Digits Are Monotone Increasing

Check Whether Digits Are Monotone Increasing Problem A non-negative integer has monotone increasing digits when every adjacent pair of digits is non-d...

Coding & Algorithms
4
0
18 people solved
Jul 4, 2026
Google logo
Google
Hard
Software EngineerNew Grad Locked

Compute Turnstile Crossing Times

This question evaluates proficiency in queue simulation, event-driven scheduling, and handling priority and tie-breaking rules while achieving linear ...

Coding & Algorithms
5
1
50 people solved
May 4, 2026
Google logo
Google
Hard
Software Engineer

Design a distributed rate limiter

Design a Rate Limiter with Burst Allowance and Distributed Coordination Context You are designing a rate limiter for an API gateway that serves high Q...

System Design
14
0
137 people solved
Sep 6, 2025
Google logo
Google
Medium
Software Engineer

Handle Teammate Who Feels Pressured

An interviewer asks: suppose one of your teammates is often underperforming and tells others that your pace and work style make them feel pressured. H...

Behavioral & Leadership
9
0
118 people solved
Feb 22, 2026
Google logo
Google
Medium
Software EngineerSenior+ Locked

Design a large-scale distributed rate limiter

This question evaluates system design competency in distributed systems, focusing on scalability, multi-tenant isolation, rate-limiting algorithms, co...

System Design
15
0
164 people solved
Jan 12, 2026

Frequently Asked Questions

How difficult are Google Software Engineer interview questions?
Google Software Engineer interview questions are typically challenging and focus on problem-solving under time pressure. Interviewers commonly evaluate algorithmic thinking, correctness, complexity analysis, and clear communication rather than memorized solutions. Difficulty varies by level: entry-level roles emphasize core data structures and coding fluency, while mid-to-senior levels include harder algorithmic problems and system-design trade-offs. Expect many problems to fall in the medium-to-hard range on public practice platforms, with follow-ups that push optimization or edge-case handling. Success usually depends on rigorous practice, clear explanation of trade-offs, and demonstrating the ability to recover and iterate when given hints.
What is the typical Google Software Engineer interview process and where do software-engineering topics appear?
A typical Google Software Engineer process begins with a recruiter screen and one or more technical phone or online coding screens, then advances to a multi-session onsite or virtual onsite loop. Software-engineering topics appear throughout: coding interviews assess algorithms, data structures, and complexity; behavioral rounds probe collaboration and leadership (often called “Googliness”); and for more senior roles you’ll see system-design interviews that evaluate architecture, scalability, and trade-offs. Teams may also request an online assessment or take-home exercise for certain roles. The process often concludes with team matching and a hiring-committee review.
How long should I prepare for Google Software Engineer interviews and what timeline works best?
Preparation time depends on background and target level, but a structured plan over six to twelve weeks is common for most candidates. Early weeks should reinforce fundamentals—arrays, trees, graphs, hash tables, and complexity—while middle weeks should emphasize timed problem sets and mock interviews to build speed and communication. If you’re targeting L4 and above, reserve additional weeks for system design and architecture. Integrate behavioral story preparation and resume-deep-dive practice throughout. Shorter, intensive sprints can work for experienced candidates with regular practice; consistent, deliberate practice beats last-minute cramming.
What key subtopics should I focus on for a Google Software Engineer interview?
Focus on algorithmic fundamentals and their practical application: arrays and strings, trees and graphs, dynamic programming, greedy strategies, hash-based techniques, and sorting. Develop strong complexity reasoning and be comfortable with edge-case handling, correctness proofs, and incremental optimizations. For mid-to-senior roles, add system-design fundamentals—API definition, data modeling, storage choices, caching, sharding, consistency models, load balancing, and reliability trade-offs. Also practice writing clean, testable code in a plain editor, debugging on the fly, and explaining trade-offs clearly; behavioral skills and clear storytelling about past projects are evaluated alongside technical depth.
What standout tips should I follow and what common pitfalls should I avoid during Google Software Engineer interviews?
Standout tips include clarifying requirements before coding, speaking your thought process clearly, writing a correct baseline solution first, and iteratively improving it while discussing trade-offs. Practice coding in a plain editor or Google Docs to mirror the interview environment, and run through mock interviews under timed conditions. For system design, structure your approach from requirements to API and data model before discussing scalability and failure modes. Common pitfalls are jumping into code without clarifying constraints, ignoring edge cases or complexity, failing to test examples aloud, and treating interview problems like puzzles instead of engineering tasks. Prepare behavioral STAR stories tied to measurable impact.

Explore more Google Software Engineer interview questions

Real questions from candidate reports, grouped by topic, role and company.

By category
Other roles at Google
Software Engineer questions at other companies
Browse all