Preparing for an interview? Check out Cracking the Coding Interview
Published on

Google L5 | Bangalore

Author
  • Shared Anonymously

I have completed all the interview rounds with Google. Sharing my experience here.

First coding round: No hire

  • Could not understand the question itself. The requirements were not at all clear and I realized it quite late in the call. Hence, as expected, it went terrible for me.
  • Question was related to graph. Had to rank people based on input results. Not every person's rank was deterministic.

Second coding round: Leaning Hire

  • I was expecting a strong hire here as I completed the question within 35 mins, but interviewer mentioned that I did not write test cases, just discussed it. So I was rated "Leaning Hire", even though everything was on point. I felt dissapointed after knowing this.
  • Question was solved using sliding window concepts and some customizations on top of it. Gave a linear approach to solve.

Third coding round: Stong Hire

  • This went really well. Was able to answer all follow ups as well. Question was a classic Trie example with a follow up using sorted string array.

System design round: Leaning Hire

  • This is my weak part. Interviewer was quite friendly and conversation went well overall. The discussion revolved around caching.

Googleyness: Hire

  • Standard googlyness questions. As per recruiter, had a good feedback overall.

Team Fit Calls:
I went through couple of team fit calls(both for SRE) but did not have a match yet. One of team needed higher experience and other found some one else.

I am already serving notice with couple of offers in hand. I still have 15 days and have conveyed the same to recruiter, not sure if this helps though.

ReportMark as Helpful