← Back to Directory

Google interview notes, page 8 of 215

FAANG / Big Tech

Most of these Google write-ups come from Software Engineers (1,167), then Product Managers (686) and Data Scientists (125). The most reported rounds are the product sense round (667), the technical phone screen (660), the behavioral / leadership round (252) and the onsite coding round (214).

2146 interview notes · updated Oct 2026

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 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 school project teams you've been part of, which was your favorite and why?

“I picked a college project team which in hindsight maybe wasn't the strongest move for a Google interview.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google coding interview, graph problem that looks straightforward until you actually try to enumerate everything. Not a lot of context to go on but the problem itself is the kind that trips people up if they haven't seen it before.
  • Given a directed acyclic graph, find all possible topological orderings of its nodes.

“My first instinct was to just run Kahn's algorithm and call it done.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Google for a software engineering role. Just one question but they really sat in it with you, lots of follow-ups about specifics.
  • Tell me about a time you were juggling multiple projects at once. How did you decide what to prioritize, and how did you handle it when something was going to slip? What did you drop, delay, or hand off, and how did it turn out?

“I had a decent story ready but fumbled the stakeholder communication part.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a single product design question centered on board meetings. Pretty open-ended, which I wasn't fully prepared for.
  • Design a product for board meetings.

“I went straight to listing features and the interviewer just kind of waited.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Google SWE coding round, pretty much a classic grid problem with a twist at the end that I didn't fully see coming. The follow-up about large-scale grids is where things got interesting.
  • You're given a city map as a grid where 1 represents a building and 0 represents empty land. Two buildings belong to the same community if they are directly adjacent in four directions. How many independent communities exist in the grid?
  • Follow-up: what if the grid is too large to fit in memory? How would you handle it?

“It's Number of Islands, basically.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM screen, just one question but it took up the whole conversation. Pretty classic product sense setup but I kept second-guessing myself on how much to lean into the 'improvement' part versus just picking something interesting.
  • What is your favorite non-Google product, and how would you improve it?

“I picked something I actually use daily which felt smart at first, but then I realized I'd spent so much time explaining why I love it that I barely left room to talk about improvements.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Google SWE coding round with a DP-flavored array problem. Pretty classic Google style where the base case seems manageable and then they hit you with a follow-up that actually requires you to think.
  • You have a 1D array of positive integers and start at index 0. At each index you can either take the value as profit and jump forward by that value plus one, or skip it and just move to the next index. What's the maximum total profit you can collect before going past the end of the array?
  • Follow-up: how does your solution change if the array can also contain negative numbers?

“Spent a bit too long trying to think of a greedy approach before accepting it's just DP.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google coding interview, one algorithmic problem on subsequences. Pretty sparse on details but the problem itself is a classic dynamic programming type that can trip you up if you haven't seen it.
  • Find the longest alternating subsequence in an array.

“I knew there was a DP angle here but spent too long trying to build a full table before realizing the greedy approach is cleaner.”

View Post

Google·Software Engineer·Online Assessment (OA)

Apr 2026
Got recruited for a software engineer role at Google and the process has multiple stages: a behavioral group hiring assessment, virtual onsites covering AI/ML and culture fit, then in-person coding rounds if you make it through. Right before the virtual onsites, an unexpected online assessment invite showed up with no real explanation, just a vague 'optional' label from the recruiter.
  • Does performance on the optional online assessment actually factor into the hiring decision?
  • What happens if you skip the optional online assessment entirely?
  • What is the difficulty level of Google's optional online coding challenge?

“The recruiter called it optional but that word does a lot of heavy lifting.”

View Post

Google·Product Manager·Onsite - System Design / Architecture

Apr 2026
Got a system design question at Google for what seemed like a senior product or engineering role. One question, broad scope, and I left feeling like I either nailed it or completely missed what they were looking for.
  • Design the architecture for a self-serve insurance product.

“I started with the user journey because I had no idea where else to begin.”

View Post