← Back to Directory

Google interview notes, page 82 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·Technical Phone Screen

May 2026
Google SWE coding round, pretty focused on array problems. The base question was straightforward but the follow-up with the replacement twist is where things got interesting and honestly where I think most people slip up.
  • Given an integer array, find the length of the longest strictly increasing contiguous subarray. Then, as a follow-up: if you can replace at most one element anywhere in the subarray, what is the longest increasing subarray you can achieve?

“The base case is fine, just a sliding window.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview at Google with a single market sizing question about Google Fi. Pretty lean on details but it's the kind of question that can spiral fast if you don't anchor yourself early.
  • Estimate the market size for Google Fi.

“The tricky part with this one isn't the math, it's deciding which market you're even sizing.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google interview with a classic fermi estimation question. Nothing too wild but it's the kind of thing that trips you up if you've never practiced talking through your assumptions out loud.
  • Estimate the total weight of a school bus.

“I started with the empty bus weight and worked up from there.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google product interview, one question about wearables. Not much context given so hard to say how it went.
  • What problems would you identify and solve using wearable technologies?

“Wide open question and I kind of froze trying to figure out where to start.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

May 2026
Coding round at Google for an ML Engineer role, one algorithmic problem that looked approachable until the O(N) constraint came up. The problem was more about seeing the pattern than knowing a specific algorithm.
  • Given an integer array, a 'good subarray' is one where every pair of adjacent elements differs by exactly 1 (either +1 or -1). Compute the sum of the element sums across all such good subarrays. The solution must run in O(N) time.

“My first instinct was to enumerate subarrays and it took me an embarrassingly long time to accept that wasn't going to hit O(N).”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview at Google with a product analytics case framed around Netflix, which was a bit disorienting since you're solving for a competitor's product. The question was meaty enough but the context switch threw me off early.
  • A million active subscribers have stopped logging into the platform. As a PM on the team, how would you investigate and address this?

“I started with clarifying questions about the timeframe and whether this was a sudden drop or gradual decline, which felt right in hindsight.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Google design manager interview with a meaty product strategy question about internationalization. One question, no fluff, just a big open-ended case that required me to think through market selection and UX changes at the same time.
  • How would you approach localizing a mobile app, including deciding which country to expand into and what product changes to make?

“I jumped straight into market selection criteria (market size, competition, regulatory stuff) and forgot to anchor on the app's current strengths first.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Interviewed for a PM role at Google, just one question about call volume came up and there wasn't much else to go on.
  • How many calls does the product receive per day?

“Classic estimation question.”

View Post

Google·Software Engineer·Online Assessment (OA)

May 2026
Google SWE behavioral online assessment, two sections: integrity/compliance scenarios and working through ambiguity. Pretty standard if you've done big-company hiring assessments before, but the questions are open-ended enough that vague answers won't cut it.
  • A colleague asks you to bend a policy to meet a short-term goal. How do you handle it, and what guides your decision?
  • You notice what might be a compliance violation by someone on your team. What do you do?
  • Tell me about a time you had to deliver results when the requirements or ownership were unclear. How did you figure out what to do first?
  • How have you adapted your approach when new information changed your understanding of a problem mid-project?

“This one's trickier than it looks because the 'right' answer isn't just 'I refused.' They want to know your reasoning process.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a product sense question that sounds open-ended but actually wants you to go pretty deep on metrics and prioritization. One question, but it had a lot of layers.
  • Pick a product you think has untapped potential. Propose three new features for it, and explain how you'd measure whether each one is actually working.

“I went in thinking the hard part was picking a clever product, but the measurement piece is where I got pressed.”

View Post