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

Google Interview Experience

Author
  • Shared Anonymously

I recently had an interview with Google and wanted to share my experience, though it was far from pleasant.

I was contacted by a recruiter some time ago, who informed me that the initial rounds of the interview process would focus on data structures and coding. Accordingly, I prepared diligently for these topics. However, when I had my first interview about a month ago, it turned out to be centered around system design, catching me off guard. Despite performing reasonably well, it wasn't as great as I had hoped. I planned to make up for it in the subsequent interviews.

To my surprise, the interview process suddenly came to a halt, and I found myself ghosted by the recruiter. No further interviews took place. After some time, the recruiter informed me that the remaining interviews were being postponed for 2-3 months, which struck me as rather unusual and frustrating.

It seems that the feedback from the initial round might not have been favorable, given my lack of preparation for that particular aspect. Instead of taking responsibility, the recruiter provided an alternate explanation. The waiting period of over 4 months since the first interview, combined with the candidate "cool down" period, only adds to the perplexity of the situation.

This was my third attempt at Google, and while the recruitment process had been positive in the past, this experience has left me disillusioned. In light of recent events, including significant changes within Google and the impact of technologies like ChatGPT, i got to know a lot changes at Google.

Have others faced similar challenges in recent Google interviews? I would appreciate any insights or thoughts from those who have gone through a similar experience.

ReportMark as Helpful