All companies

THE INTERVIEW BRIEFING

Google Interview Guide

Prepare for Google with a focused mix of coding, design, and communication. Start with your job description and confirm the interview loop with your recruiter.

10 Question notes 6 Practice picks 23 Interview reports 5 Levels mapped

01 / MAKE YOUR NEXT SESSION COUNT

Your preparation, made concrete.

AlgoDaily practice • not reported questions
0130 min suggested

Tree traversal under pressure

Return a binary tree in level order. Compare an iterative queue with recursion and test an empty tree and a long chain.

What a strong answer demonstrates

A correct traversal, bounded auxiliary memory, and a clear explanation of the trade-off.

0230 min suggested

Find the right array pattern

Merge two sorted arrays. Then adapt your solution when one array has enough unused space to hold both. Explain how you avoid overwriting unread values.

What a strong answer demonstrates

A maintained invariant, correct boundary handling, and justified complexity.

0320 min suggested

Behavioral storytelling

Describe a technical decision you changed after receiving feedback. Explain your contribution and the outcome.

What a strong answer demonstrates

Specific actions, honest reflection, and measurable impact.

BEFORE YOU PRACTICE

Ask your recruiter.

Get the details that a generic company guide cannot know.

  • Which team and level is this opening for, and what does success look like?
  • What rounds, durations, and evaluation criteria should I prepare for?
  • Which languages, tools, and AI assistance are permitted?
  • Will design focus on frontend, backend, infrastructure, or another specialty?
  • Are there accommodations or preparation materials I should request?

Google practice problems

Company-linked challenges and related lessons from our library. Not a prediction of your interview.

Questions candidates have reported

Aggregated from candidate submissions and public sources.

Q1
Lonely Number: Given a list of number from 1 to N. All of them written three times, except one number (written 1 or 2 times). Find the unique number.
Q2
Find Shortest Palindrome Possible: Find the minimum number required to insert into a word to make it a palindrome.
Q3
How Deep Does It Go: Find the deepest node of a binary tree. If multiple nodes are at the deepest level, then return the rightmost node.
Q4
Given a sorted matrix where the number below and right of you will always be bigger, write an algorithm to find if a particular number exist in the matrix. what is the running time of your algorithm?
Q5
Given a graph as input, write a method returning boolean true if the graph is bipartitie, else false.
Q6
Reorganize array of numbers in "s1 < s2 > s3 < s4 >.... " fashion. the numbers may include duplicates.
Q7
How would you find the longest substring of a string containing only one character?" this was then expanded to two characters, etc
Q8
You are given a starting position on a chessboard, as well as an end position. if you are only allowed to walk diagonally, how many steps do you need to take to get to the end position?
Q9
Given a bunch of points and a convex polygon in r^2. determine if each point is inside the polygon.
Q10
Write an api to start google now, when saying "ok google".

Engineering levels & compensation

Historical figures from existing records; date and location may be unspecified. Verify current ranges on Levels.fyi.

Level 1

L3 · SWE II

$182,560

$121,029 base · $41,690 stock · $19,841 bonus

Level 2

L4 · SWE III

$255,980

$147,683 base · $78,940 stock · $29,357 bonus

Level 3

L5 · Senior SWE

$348,283

$178,805 base · $133,186 stock · $36,292 bonus

Level 4

L6 · Staff SWE

$461,567

$206,367 base · $187,333 stock · $67,867 bonus

Level 5

L7 · Senior Staff SWE

$625,529

$256,059 base · $286,176 stock · $83,294 bonus

Real interview experiences

23 reports from candidates who interviewed at Google.

What people at Google say

Reviews originally posted on Glassdoor.

Work life balance can be what you want it to be on most teams. (Some teams are in more competitive sectors and require more crazy hours all the time - but very few of them). If you work 40 hour weeks without putting in anything extra,you'll fall behind them as they advance and you stand still - and maybe that doesn't matter, so it works out for everybody. But at least know where you would realistically stand. If you excel and work your butt off, you'll be compensated and promoted.
They take very good care of their people. Lots of challenging work. More manual work than expected. People feeling very entitled, even though they are very nice. Scale and complexity of most of their systems. A significant portion of the people are focused on promotion.
Excellent stock & bonus, if you live on your salary you'll be making some serious bank towards retirement. Competition both to get in and to get promoted is severe and steep. You'll be making slow progress, if any, towards goals of advancement in title and responsibilities.
Amazing people to work with, exciting technology, high impact work. For a company that is all about scale, its biggest problem is scaling to the # employees and the expanding breadth of scope. Some areas are very top heavy. Don't lose the engineering focused culture of trust and openness.
Perks and benefits are awesome. Great people there, I made some friends for life. Systems are overengineered to an extent that making progress is very slow and painful. It's part of the company culture at this point, so when new systems are created they typically suffer from the same problem. Prevent your teams from reinventing the wheel over and over again. Replace the bottom layers of the stack (Kernel, Linux distro, base system daemons) with upstream. Embrace OpenCompute for servers, racks and other DC components.
Inside the workplace

About Google

A day at Google