Google·Software Engineer·Technical Phone Screen
- How would you define a vulnerability?
“Seemed basic but I stumbled a bit trying to sound precise.”
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
“Seemed basic but I stumbled a bit trying to sound precise.”
“I went straight to user segmentation, which felt right, but I think I spent too long on the problem space and rushed the actual solution.”
“My first instinct was just enumerate all valid subarrays and sum them up, which is obviously not O(n).”
“I picked one project and tried to go deep instead of name-dropping three different things.”
“I stalled for a second because the premise is so absurd it's hard to know if they want you to play it straight or zoom out into pure strategy mode.”
“I went straight into logistics and ticketing, which in hindsight was too narrow.”
“Started with brute force because I panicked a little and needed to say something.”
“I went straight to personalization and content freshness, which felt safe but maybe too safe.”
“Three separate correctness conditions and I had to untangle which bugs corresponded to which.”
“I went straight to engagement metrics and kind of dug myself into a hole.”