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
Hard
Software Engineer Locked

Compute minimax grid path and network delay

This question evaluates algorithmic problem-solving in shortest-path and path-optimization contexts, specifically minimax pathfinding on a grid and si...

Coding & Algorithms
20
0
238 people solved
Jan 22, 2026
Google logo
Google
Medium
Software Engineer

Check if all substrings are dictionary words

You are given a string s (letters only) and access to an English dictionary dict (a set of valid words). Return true if every contiguous substring of ...

Coding & Algorithms
33
0
319 people solved
Mar 11, 2026
Google logo
Google
Medium
Software Engineer

Design at-least-once notification delivery

System Design: At-Least-Once Notification System Context Design a multi-channel notification platform (email, SMS, push, in-app) that guarantees at-le...

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

Assess behavioral competencies across scenarios

Behavioral Competency Prompts (Software Engineer, HR Screen) Provide specific work situations that demonstrate each competency below. Use concise STAR...

Behavioral & Leadership
6
0
92 people solved
Sep 6, 2025
Google logo
Google
Easy
Software Engineer

Describe conflict resolution and stakeholder management

Behavioral Prompt Describe a time when you faced a serious conflict at work (e.g., disagreement on technical direction, priorities, scope, or executio...

Behavioral & Leadership
8
0
73 people solved
Jan 11, 2026
Google logo
Google
Easy
Software Engineer

How would you lead a team through delivery issues?

Interview Prompt (Behavioral & Leadership) You are interviewing for a software engineering role. The interviewer runs a mixed behavioral round: one ex...

Behavioral & Leadership
5
0
51 people solved
Nov 17, 2025
Google logo
Google
Hard
Software Engineer

Navigate conflict, difficult people, and culture issues

Answer the following behavioral questions with clear examples (preferably using the STAR method: Situation, Task, Action, Result). Be explicit about y...

Behavioral & Leadership
3
0
35 people solved
Jan 4, 2026
Google logo
Google
Medium
Software Engineer Locked

Simulate meeting-room bookings and return busiest room

This question evaluates a candidate's competence in scheduling and resource-allocation algorithms, focusing on simulation of interval-based bookings, ...

Coding & Algorithms
15
0
159 people solved
Mar 1, 2026
Google logo
Google
Hard
Software EngineerNew Grad Locked

Simulate In-Place Cellular State Updates

This question evaluates a candidate's ability to implement grid-based state transitions and manage in-place updates with strict space constraints, ass...

Coding & Algorithms
7
0
41 people solved
May 4, 2026
Google logo
Google
Hard
Software Engineer

Design school-to-guardian messaging with acknowledgments

System Design: Guardian Acknowledgement Messaging Platform Context Design a system that enables school staff to send messages to students' guardians, ...

System Design
5
0
86 people solved
Sep 6, 2025
Google logo
Google
Hard
Software Engineer

Design A/B testing platform

Design an A/B Testing Platform (Architecture + Experiment Science) Context You are designing an A/B testing platform for a large-scale consumer web/mo...

Analytics & Experimentation
7
0
82 people solved
Sep 6, 2025
Google logo
Google
Hard
Software Engineer

Design viewing history and resume service

Design: Watched-Video and Resume Playback Service Context Design a backend service that records each user’s watched video list and lets them resume an...

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

Design autocomplete with Trie

Design and implement an autocomplete service backed by a prefix tree (Trie). The service stores a dynamic dictionary of words, each carrying an intege...

Coding & Algorithms
12
0
171 people solved
Sep 6, 2025
Google logo
Google
Hard
Software Engineer

Make algorithm code production-ready

Productionizing a Sliding-Window String Algorithm Context: You have implemented a correct sliding-window algorithm for a classic string task (e.g., lo...

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

Recommend top-K movies from similarity graph

Movie Recommendation: Top K You are building a simple movie recommendation feature. Input - A set of movies 0..(M-1). - An undirected similarity graph...

Coding & Algorithms
68
1
529 people solved
Dec 15, 2025
Google logo
Google
Medium
Software Engineer

Maximize coins collected by tokens jumping +3

You are given a single-player board game represented by a string board of length N (1 ≤ N ≤ 100). Each character is one of: - '.': empty cell - 'T': a...

Coding & Algorithms
5
0
53 people solved
Feb 13, 2026
Google logo
Google
Medium
Software Engineer Locked

Find shortest relationship path using BFS

This question evaluates proficiency in graph representations and traversal algorithms—specifically BFS and adjacency-structure construction—for comput...

Coding & Algorithms
21
0
143 people solved
Feb 12, 2026
Google logo
Google
Hard
Software Engineer

Find secret word with match-count feedback

Problem You are given a list of unique lowercase words, all of the same length (e.g., length = 6). One of these words is a secret word. You can intera...

Coding & Algorithms
14
0
147 people solved
Feb 11, 2026
Google logo
Google
Medium
Software Engineer Locked

Design structure for insert and k-th largest

This question evaluates data-structure design and algorithmic efficiency for dynamic order-statistics over a multiset (duplicates allowed), focusing o...

Coding & Algorithms
12
0
86 people solved
Feb 11, 2026
Google logo
Google
Medium
Software Engineer

Handling an Ambiguous "Family Tree" Prompt

Behavioral/Leadership: Handling an Ambiguous "Family Tree" Prompt Context: In a technical screen, the interviewer says only "there is a family tree" a...

Behavioral & Leadership
2
0
52 people solved
Aug 10, 2025

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