Google Software Engineer interview questions

354 Software Engineers have shared notes from their Google interviews, with the questions they were asked in each round. That is 87% of the 405 Google interview notes on Screna AI.

354 Software Engineer interview notes

Google·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Google for a software engineering role. The whole session was basically one giant question about building a log processing platform from scratch, and they wanted you to go deep on every layer. Pretty intense but not unfair.
  • Design an end-to-end log processing system that ingests logs from many services and supports search and aggregation across the full pipeline.

“This was a beast of a question.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Google SWE interview that was basically a full OOD design session. They wanted a working wait-list system with real complexity analysis and extension discussion, not just pseudocode on a whiteboard.
  • Design and implement a complete wait-list system. It needs to support joining and leaving the queue, viewing the full ordered queue, and efficiently retrieving the top K or bottom K entries. Walk through your class design, the data structures you'd use, time complexity for each operation, and how you'd extend it for priorities, persistence, and concurrency.

“I started with a doubly linked list plus a hashmap for O(1) join/leave and O(n) traversal, which felt solid.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Google SWE coding round with a board-traversal problem that looked straightforward but had some tricky edge cases around move ordering. Not a lot of fluff, just got thrown into the problem pretty fast.
  • You have a 1D board with tokens and coins at various positions. Tokens can only move right, jumping exactly 3 cells per move. A token collects a coin if it lands on one. Given multiple tokens, find the maximum total coins collectible, and explain whether the order in which you move tokens matters.

“I went straight to greedy and got burned a little.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview with a classic frequency problem. Nothing too surprising but the follow-up on optimizing beyond the naive solution was where things got interesting.
  • Given an integer array and an integer k, return the k most frequent elements in the array.

“I jumped straight to the hashmap plus heap approach, which works fine at O(n log k).”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google software engineering interview with a pretty gnarly string/combinatorics problem. The question had multiple moving parts and I spent most of the time just trying to make sure I understood what was even being asked.
  • Given a string and a dictionary of valid English words, return true if every subsequence of length 3 or more can be rearranged into some valid English word. Walk through your approach including how you'd enumerate subsequences and check anagram validity, and analyze the time and space complexity.

“The anagram check part was fine, character frequency maps are pretty standard.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Google SWE interview, behavioral round focused on a single deep-dive project question. Pretty standard format but the level of detail they expected on individual contribution versus team contribution caught me off guard.
  • Walk me through a project you're most proud of. What was the problem, what did you personally contribute versus the team, what technical decisions and trade-offs did you make, what was the impact, and what did you take away from it?

“The part that tripped me up was the 'you vs the team' split.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Google for a software engineer role. Just the one question but they really sat with my answer, which made me more nervous than I expected.
  • Tell me about a time you worked in an environment where things were constantly changing.

“I fumbled the opening because I picked an example that was technically true but kind of boring.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview with a string manipulation problem that looked straightforward but had enough moving parts to trip you up if you weren't careful about the indexing logic.
  • Given a string, a validation string, and a length k, split the original string into substrings of length k. For each substring, compute a checksum by summing the character values, then use that checksum (mod the length of the validation string) as an index to pick a character from the validation string. Return the string formed by concatenating all the picked characters in order.

“The problem itself isn't conceptually hard but I kept second-guessing the modulo step.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Pretty standard behavioral round for a software engineer role at Google. Four questions, all the usual stuff about teamwork and stakeholder handling. Nothing that surprised me but I still fumbled a couple.
  • Can you describe a time when you stepped up to support your team?
  • What did you like and dislike about your previous team lead?
  • If someone on your team isn't a good fit, how would you handle it?
  • A stakeholder asks you to bump their request to the top of the queue. How do you respond?

“Blanked for a second trying to pick the right story.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral screen for a software engineer role at Google. Just the one question about team experience, pretty standard stuff.
  • Out of all the companies or project teams you've been part of, which one was your favorite and why?

“Picked a school project team thinking it would come across as more genuine than just listing a job.”

View Post