Google Asked me this
I was asked a geometry query problem about finding all points within a given circle, proposed a square‑enclosure solution, and was ultimately rejected.
How Google runs its interviews, round by round, from the candidates who went through them: the questions asked, how hard they were, and who got an offer.
Worked out from the 305 Google write-ups on this site.
Bangalore (22) · USA (9) · Bengaluru (8) · Hyderabad (7) · US (5)
I was asked a geometry query problem about finding all points within a given circle, proposed a square‑enclosure solution, and was ultimately rejected.
I attended a Google Front‑end Development Engineer onsite interview, failed the DSA round, and did not receive an offer.
I interviewed for a Google L3 role, which included behavioral questions and a single coding problem about implementing multiple timers on a single hardware timer.
I interviewed for a Google Cloud AI Engineer role; the onsite DSA round featured a custom array problem and I was not selected due to bugs in my code.
I interviewed for a Google L4 DSA round, tackled several graph‑based problems, and was rejected after the first round.
I had a phone screen with Google that included a behavioral round and a coding round on graph algorithms; I struggled with the BFS approach and ran out of time on the...
Very subjective process
I completed the Google L3 phone screen and Googlyness round, solving a shift‑timeline coding problem and answering behavioral questions.
I interviewed for a Google L4 SWE position, completed a technical round with a BFS grid problem and a Googliness round, but was ultimately rejected.
I completed a Google L3 phone screen, solved a squares-counting problem with hints, and discussed follow-up variations.
I had a virtual interview with Google in August 2026 that included a screening coding round and several Googliness questions.
I interviewed for a Google L4 Software Engineer role in India, cleared the online assessments and behavioral round, but was rejected after a DSA interview and a...
I had a 45 minute Google phone screen where I discussed AI usage and solved a squares‑counting problem, but the interview did not reach a final decision.
I completed four interview rounds for a Google Software Engineer L3 position, solved all technical questions, and received an offer after the hiring committee.
I completed a one‑hour team‑matching interview for a Google L3 role, during which the hiring manager asked three behavioral questions....
Across 305 Google interview experiences shared on Interview Experiences, the questions asked were mostly data structures & algorithms (77% of reported questions), behavioral (17% of reported questions), system design (4% of reported questions).
Candidates rated most Google questions as medium (51% of rated questions). Easy: 7%, Medium: 51%, Hard: 41%.
31% of the 99 candidates who reported their result received an offer. People who share their experience are not a random sample, so treat this as a rough guide.
Questions reported more than once include "Find Triplet in Stream with Threshold", "Top K Frequent Elements", "Shortest Time to Any Favorite City", "Stack-Based Problem", "Group Buddy Strings".
There are write-ups for SDE 2 (71), SDE 3 (32), SDE 1 (30), Software Engineer (8), SDE Intern (4), Senior Software Engineer (3).
The median candidate had 3.9 years of experience.
Write up your rounds while you still remember the questions. It is exactly what the next Google candidate is searching for.