Google interview questions
588 coding problems in the Placed library have been reported in Google software engineering interviews, along with 17 behavioral questions. Every one can be run as a timed mock interview with a voice interviewer and a scored report.
Patterns that come up most
- Hashing32
- 1d dp31
- Greedy29
- Two pointers24
- BFS22
Problems to start with
- Two SumEasy
- Valid ParenthesesEasy
- Reverse Linked ListEasy
- Best Time to Buy and Sell StockEasy
- Longest Substring Without Repeating CharactersMedium
- 3SumMedium
- Container With Most WaterMedium
- Longest Palindromic SubstringMedium
- Word SearchMedium
- Merge K Sorted ListsHard
- Trapping Rain WaterHard
- N-QueensHard
That is 12 of 588. Pro adds a company filter to the full library. See pricing.
Google runs an AI-assisted coding round
In that round you work with an AI assistant and are graded on how you direct it and check what it gives you. Placed has a track for it.
Try an AI-assisted roundBehavioral questions
- Ownership & Initiative
Tell me about a time you inherited a codebase, process, or product in bad shape. How did you decide what was worth fixing versus tolerating? What concrete improvements did you drive, and how did you measure progress?
- Ownership & Initiative
Tell me about the most impactful thing you've built or changed without being told to. How did you identify the opportunity? How did you get it prioritized when it wasn't on anyone's roadmap, and what impact did it have?
- Dealing with Ambiguity
Tell me about a time you had to make a significant technical decision with incomplete information and real pressure to move forward. What did you do to reduce the uncertainty before committing? How did the decision turn out, and what would you do differently?
- Dealing with Ambiguity
Tell me about a time you were handed a vague problem — not a task, not a spec, just "figure this out." How did you scope it? What was the first week like, and how did you know when you were on the right track?
- Dealing with Ambiguity
Tell me about a time you debugged an issue where the root cause was genuinely unclear for a while. What was your process for narrowing it down? At what point did you know you'd actually found it rather than a surface symptom?
- Collaboration & Influence
Tell me about a time you had to get a team to adopt a technical decision you believed in, without having authority over them. What made it land — the evidence, the framing, the trust, something else? What didn't work?
- Collaboration & Influence
Tell me about a time you mentored a more junior engineer through a non-trivial problem. How did you decide when to hand them the answer versus let them struggle? What did they learn, and what did you learn from mentoring them?
- Collaboration & Influence
Tell me about a time you worked closely with a PM, designer, or data scientist whose approach to the problem was very different from yours. How did you calibrate to each other? What came out of that collaboration that neither of you would have produced alone?
Practice a behavioral round and the interviewer asks follow-ups on your answers.
Company tags come from publicly shared interview reports. They are not confirmed by Google and do not imply affiliation or endorsement.