← Back to Directory

Google

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·Technical Phone Screen

Oct 2026
Two rounds for a Google SWE intern role, both went faster than expected. The second round got weird toward the end with a problem that turned into a collaborative back-and-forth, which left me unsure whether that was a good sign or a bad one.
  • Solve a combinatorics-based problem (non-standard, not a typical leetcode-style prompt).
  • Given a tree with a specific structural property, solve the core problem and then construct a tree that satisfies that same property.

“Finished with time to spare and got a trivial follow-up that was basically one line added to my solution.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026
Phone screen at Google for a software engineering role that threw me completely off with a file-based string problem I had no prep for. Spent most of the call fumbling through hints and never actually wrote any code, which still stings.
  • Given a 4GB file, find the minimum length of a substring that does not appear anywhere in the file.

“My first instinct was brute force with hashing and the interviewer basically shut that down immediately.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026
Did a two-round Google SWE intern interview and felt pretty good about the first one, then completely fell apart on the second. The second round was graph-based and I struggled badly enough that I actually told the interviewer I thought I'd bombed it, which I'm now second-guessing.
  • A graph-based algorithmic problem (specific problem not disclosed).

“Couldn't get through it cleanly.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026
Google SWE intern technical screen, one coding question with three follow-ups, OOP and data structures focus. Went reasonably well but ended with a small bug I couldn't squash before time ran out, so I'm sitting here wondering if that cost me.
  • Design and implement an OOP-based solution to a data structure problem, then extend it through multiple follow-up constraints.

“The interviewer read the whole thing out loud instead of sharing it on screen, which threw me off more than I expected.”

View Post

Google·Software Engineer·Technical Phone Screen

Oct 2026
First technical screen for a Google SWE internship. OOP and data structures, medium difficulty, with three follow-ups back to back. Went reasonably well but nerves were a factor and a small bug at the end left things feeling unfinished.
  • Design a solution to an OOP-based problem involving data structures, then extend your solution through multiple follow-up constraints.

“Hadn't touched OOP in about a year and the interviewer read the whole thing out loud instead of pasting it, so the first few minutes were rough just trying to hold all the pieces in my head.”

View Post

Google·Software Engineer·Onsite - Multi Round

Sep 2026
Did my Google SWE intern loop and came out of it genuinely unsure how to feel. Round one was rough in patches but round two went well enough that the interviewer said they'd support me, so now I'm just waiting and overthinking it.
  • Solve a medium-difficulty coding problem that involves handling two distinct conditions, one simpler and one harder, where the harder case can be reduced to the simpler one.
  • Solve a medium-difficulty coding problem, then modify your solution to handle a follow-up variant of the original problem.

“This is where things got messy.”

View Post

Google·Software Engineer·Technical Phone Screen

Sep 2026
Google SWE intern technical screen, one OOP and data structures problem at roughly medium difficulty with three follow-ups. Nerves were a factor and there was a small bug at the end, but the core solution held up.
  • Design a solution to an OOP-based data structure problem, then work through multiple follow-up extensions on top of your initial implementation.

“Hadn't touched OOP in about a year, which showed a little at the start.”

View Post

Google·Software Engineer·Technical Phone Screen

Sep 2026
Interviewed at Google for a software engineering role. The DSA portion went fine but the interviewer was visibly checked out the whole time, rolling their eyes and complaining about having to conduct a first-round interview. Technically I held my own. Everything else was a mess.
  • Solve a data structures and algorithms problem, walk through your approach with an example, and present your solution.

“Completed it fine.”

View Post

Google·Software Engineer·Onsite - Multi Round

Sep 2026
Two back-to-back coding rounds at Google for a SWE internship. The first went smoothly, the second was a logic-heavy problem that threw me off and I needed a hint to catch a bug. Still waiting to hear back and kind of spiraling about it.
  • Find duplicate elements in a collection and perform a set of operations on them.
  • Solve a logic-based coding problem with no conventional data structures involved, focused purely on reasoning through the problem's mechanics.

“Started brute-force, talked through sorting, got the complexity right when asked.”

View Post

Google·Software Engineer·Onsite - Multi Round

Sep 2026
Two rounds of coding interviews at Google for a SWE intern role. Both interviewers were relaxed and the problems felt manageable, though the second one had a weird moment where we were basically solving two different questions until I caught on.
  • Given a coding problem related to video platform infrastructure, solve it and then optimize for better time complexity as the constraints are modified.
  • Solve a coding problem efficiently, then determine whether the time complexity can be further improved.

“The interview ran way over time, like 25 minutes over, because the interviewer kept adding new scenarios.”

View Post

Google interview guides

Online Assessment

21 Google Online Assessment Reports 2026, Including AI Tasks

Data Scientist

Google Data Scientist Interview 2026: Unicode, Streaming Constraints, and Senior Coding Skills

Software Engineer

Google Software Engineer Interview 2026: A Real Onsite Coding Question and What It Tests

Product Manager

Google Product Manager Interview 2026: Product Strategy, Leadership, and Real PM Case Insights

Google interview FAQ

What rounds are in the Google interview?

Candidates most often report a product sense round (667 write-ups), a technical phone screen (660), a behavioral / leadership round (252) and an onsite coding round (214).

What does the Google product sense round cover?

Across 667 product sense write-ups, the most tagged question topics are Product Strategy (491 questions), Product Sense & Ideation (464) and Adaptability & Ambiguity (225).

What is asked in the Google technical phone screen?

Across 660 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (616 questions), Technical Trade-offs (522) and System Design (175).