Google software engineer interview questions
Practice problem solving, coding communication, system design, and collaboration questions for Google software engineering roles.
Practice guide: Interview content varies by role, level, team, and location. These representative prompts are based on public company guidance and general interview patterns; Google does not endorse this guide.
6 questions, one at a time
Coding questions
Each problem has a full statement, examples, constraints, and a tested solution in Python, Java and C++.
System design questions
Turn requirements into APIs, data models, architecture choices, bottlenecks, and explicit trade-offs.
Behavioral questions
Prepare truthful evidence of decisions, ownership, collaboration, learning, and measurable results.
How the Google interview is structured
A practical preparation set aligned with Google’s public description of its hiring process. Exact interview formats vary by role and stage, so these prompts are practice material rather than a reported question bank.
That shapes how you should prepare. The rounds in this guide break down as 3 coding, 1 system design, 2 behavioral, and they are not interchangeable — a coding round rewards a working solution reasoned aloud, a system design round rewards explicit trade-offs, and a behavioral round rewards a specific story with a measurable result. The fastest way to lose a round you could have passed is to prepare for all three the same way.
What the coding round checks
Each problem has a full statement, examples, constraints, and a tested solution in Python, Java and C++.
- Fundamental pointer reasoning, correctness, and clear testing.
- Sliding-window reasoning, choosing what state to keep, and avoiding the off-by-one when the left edge moves.
- Interval reasoning, choosing a heap for the right reason, and precise boundary rules.
What the system design round checks
Turn requirements into APIs, data models, architecture choices, bottlenecks, and explicit trade-offs.
- Requirements, consistency choices, metadata design, sync conflicts, and reliability.
What the behavioral round checks
Prepare truthful evidence of decisions, ownership, collaboration, learning, and measurable results.
- How you clarify ambiguity, form hypotheses, and communicate while solving.
- Listening, constructive disagreement, and whether the relationship improved.
Follow-up questions to be ready for
Most candidates prepare a first answer and stop. The round is usually decided by what comes after it — these are the follow-ups the questions in this guide lead to:
- Can you do it recursively?
- What is the space complexity?
- What changes for a doubly linked list?
- What if you must return the substring, not its length?
- What if each character may appear at most twice?
- How would you handle a stream of characters?
- Can you also return which room each meeting uses?
- How would you solve it with two sorted arrays instead of a heap?
Mistakes that cost people the Google round
Collected from the questions in this guide. None of them is about knowing less — they are all about how an answer is delivered under time pressure:
- Losing the next pointer
- No edge-case test
- Reciting code without reasoning
- Moving the left edge backwards on a stale index
- Confusing a substring with a subsequence
- Rebuilding a set for every start index
- Using < instead of <= for back-to-back meetings
- Forgetting to sort by start time
Common questions
What does Google test in a software engineer interview?
A practical preparation set aligned with Google’s public description of its hiring process. Exact interview formats vary by role and stage, so these prompts are practice material rather than a reported question bank.
What is in this Google question list?
6 representative practice questions — 3 coding, 1 system design, 2 behavioral. Each one comes with what the interviewer is checking, a three-step plan for the answer, the follow-ups that usually come next, and the mistakes that cost people the round. Coding questions also carry a full problem statement, examples, constraints and tested solutions in Python, Java and C++.
Are these real Google interview questions?
No — and treat any site claiming otherwise with suspicion. These are representative prompts based on public company guidance and general interview patterns. Interview content varies by role, level, team and location, and Google does not endorse this guide.
What should I focus on first for Google?
Algorithms, Problem solving, System design, Googleyness and leadership. Work the question types in that order rather than grinding only coding problems: the rounds that trip people up are usually the ones they did not rehearse out loud.