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

Google Interview Experience.

Author
  • Shared Anonymously

I had the opportunity to go through the interview process at Google, and I'm sharing my experience here. Before I begin, I have never lost the identity of who I actually am, and I never will. Anyway, the recruiter proposed a Mock interview before the screening, and I gladly accepted.

Mock Interview Details:

  1. Initial Reaction: We exchanged greetings, but I was taken aback by the lengthy question. I had to read it multiple times to understand all the details properly.
  2. Question Level: LeetCode Hard. Topic: Dynamic Programming + MonoTonic Stack.
  3. Feedback: After the interview, I asked my interviewer for feedback and areas of improvement. In his exact words, he said, "Your communication was top-notch. You arrived at the optimal solution very quickly, which was impressive. You also asked pretty good questions. If possible, try to draw/illustrate on the doc itself rather than your notebook."Additionally, when I provided feedback to him, I requested better structuring of the questions, using bold fonts for examples, as the length of the question surprised me initially. I explained the psychological angle about how different font faces could help with visual clarity and quick identification of the question and example sections. He smiled and agreed with the suggestion.

Round1 was scheduled for the next week, and here are the details:

  1. Initial Reactions: His first question was, "Have you been to Europe?" while yawning. I replied with a No and asked if he had gone through my resume, to which he answered No.
  2. Question Level: LeetCode Easy. Topic: HashMap.
  3. Feedback: I completed my interview 20 minutes before the scheduled time. When he asked if I had any questions, I inquired about Quantum and the AI R&D team at Google. To my surprise, he provided negative feedback to my recruiter.

After the round, I had a call with my recruiter, and I requested a retake for this round due to the interviewer's apparent lack of sincerity. I expressed my concerns to my recruiter, saying, "The person who took my interview yesterday was yawning while I was explaining my answers. If he had no interest in conducting the interview, perhaps he should have allowed someone else to do it. I request a retake for this round, but please ensure that the next person is qualified and genuinely interested in taking my interview. Schedule it with someone experienced in conducting interviews and who is passionate about it. Interviewer should understand that there's somone's dream on line when conducting interviews."

My recruiter agreed to the retake, but unfortunately, there was an unexpected(I can't tell) issue with the Visa for that country, and they had to halt the progress of my interview. When my recruiter told me about it, I replied, "Never mind. I will look for other locations."

About Me:

I am a CS graduate from India, and I am an affiliate member of Massachusetts Institute of Technology's Alumni Association. Throughout my academic journey, I have been recognized for my academic excellence, and I have also received awards in Football and Javelin throw at the state level. Besides excelling in sports and academics, I have been honored with multiple awards in extracurricular activities, and I achieved a national rank within the top 10 in the International Informatics Olympiad.
Previously, I received a training at MIT on Machine Learning and Mathematics for four months.

Although I had the opportunity to join Stanford for research under a scientist, I chose to decline the offer as my desire was to work at Google initially.

Currently, I am engaged in cancer and genetics research, collaborating closely with scientists from Stanford. This field is one that I am deeply passionate about, and my goal is to contribute to the discovery of a definitive cure for cancer and to make significant advancements in research and development. I am also looking to work at Apple just in case.

Bottom Line: Give your best.

ReportMark as Helpful