← Back to Directory

Google interview notes, page 174 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·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview with a food truck scaling case. Pretty open-ended, which I wasn't fully prepared for.
  • If you had a thriving food truck business, how would you scale it up?
  • How would you decide when to add more trucks versus hiring more staff, and how would you prioritize between those two?

“I went straight to 'open more trucks' and the interviewer just stared at me waiting for more.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE phone screen with one coding problem that had a follow-up twist I never got to actually code. The core question was manageable but the time pressure was real.
  • Given a piece of text and a dictionary of token-to-ID mappings, implement a greedy longest-match tokenizer. For each position in the text, find the longest token in the dictionary that matches, output its ID, and if nothing matches, output the character literally.

“Went with a hashmap for the dictionary and a forward scan at each position, which felt right.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview with a single estimation question about Instagram's daily post volume. Pretty standard product sense screen, nothing too wild, but these market sizing questions always stress me out more than they should.
  • How many posts are uploaded to Instagram in a single day?

“I started from monthly active users, tried to segment by how often casual vs.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google software engineering interview, system design flavored technical phone screen that went pretty deep into Linux internals. One question, but it had a lot of moving parts and I felt like I was constantly playing catch-up.
  • Walk me through everything that happens under the hood when a user types `ls` in a shell and hits Enter. Cover the shell's behavior, how the binary gets located and executed, the relevant system calls and kernel filesystem interactions, how directory entries and file metadata get retrieved, and how flags like `-l`, `-a`, and `-R` change any of that.

“This question is deceptively wide.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE coding round with a string matching problem that looks deceptively simple until you realize the edge cases stack up fast. Classic Google style where the problem statement is clean but the implementation isn't.
  • Given a dictionary of words and a 'jammed' string where keys on a keyboard can repeat characters (but never drop, insert, or reorder them), return all words from the dictionary that could have produced the jammed string.

“The core idea clicked pretty quickly: each character in the original word just needs to match a consecutive run of the same character in the jammed string, in order.”

View Post

Google·Software Engineer·Onsite - Multi Round

Jun 2026
Interviewed for a software engineer role at Google, one technical round and one behavioral. The technical went okay but I left a case unfinished, and the behavioral felt shaky throughout. Didn't move past round one.
  • Solve a medium-difficulty coding or design problem, walking through your approach and implementation.
  • Describe a situation that demonstrates your values or leadership, with follow-up questions probing for more detail.

“Spent a solid chunk of time upfront clarifying the problem, which I think was the right call.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Google system design round for a software engineering role. The main question was one of those 'evolve your working solution into something real' prompts, which sounds straightforward until you realize how many dimensions they actually expect you to cover.
  • You've written a working sliding-window string solution. Now walk through how you'd turn it into production-ready code, covering API design, input validation, encoding, memory constraints, thread safety, observability, testing strategy, complexity guarantees, Unicode support, security, and deployment/rollback plans.

“I had the algorithm part down cold, which gave me false confidence.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview with a product strategy question about launching an analytics tool that works across mobile, web, and other deployment types. Pretty open-ended, which I wasn't totally prepared for.
  • You're the PM for an unreleased analytics product that can aggregate data across mobile apps, websites, and other deployment types. How do you approach the launch?

“I jumped straight into go-to-market stuff and the interviewer kind of just...”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a security engineer role at Google, got asked about SSL handshake mechanics. Pretty standard stuff but worth thinking through carefully before you go in.
  • Can you walk through how an SSL handshake works?

“Knew this one but fumbled the ordering of the steps under pressure.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google SWE interview focused on string processing problems, specifically the kind that push you toward recursion or DP. Pretty standard for this level but the depth expected on state definition and complexity analysis was no joke.
  • Solve a string processing problem using recursion or dynamic programming. Examples include edit distance, longest common subsequence, regex or wildcard matching, word break, or palindrome partitioning. You should be able to define the DP state, write the recurrence relation, handle base cases, and explain your memoization or tabulation approach, plus give time and space complexity.

“This is the kind of question that feels manageable until they ask you to formally define the state.”

View Post