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

Google | L4 | Hyderabad | Apr 2024 [Reject]

Author
  • Shared Anonymously

I recieved a mail regarding scheduling of call to discuss the opportunity details in January.

After a day or two, we connected on call and discused about the opportunity. I applied on Google Career portal as instructed by Recruiter. I asked for around 1 month for preperation.

Phone Screen Round
Duration: 65 mins, actually question was so lengthy so it got strretched.
Questions: 1
Problem: 85. Maximal Rectangle Actually question was extension of this problem.
Discussion: I explained my approach and edge cases handling. Then I wrote the code and dry run over the test case.
Feedback: Strong Hire, I took around 15 days for feedback.

Recruiter told me to prepare for Coding Rounds and asked for dates for upcoming rounds within 4 weeks. I asked for 3 weeks.

Coding Round 1
Duration: 45 mins
Questions: 1(Extension Question:1)
Problem: Create an API to get the average of latest k items in running streams And also having some outliers. (Interviewer was not able to explain the question)
Discussion: I gave the the approach for k items with edge cases,complexity and dry run within 10 mins. Interviewer was satisfied. Then interviewer added some outliers condition. But since Interviewer was not able to explain the question. I asked multiple times for sample dry run. But he was hesistant. So, lastly i interpreted on my own gave some thoughts and discussed the solution.
Feedback: No Hire.

Coding Round 2
Duration: 45 mins
Questions: 1(Extension Questions:3)
Problem: Maximum Sum Subarray such that start and end values are same.
Discussion: I gave the my approach for same with edge cases, time complexity and dry run.
Then interviewer modified the question

  • if array contains negative numbers.
  • if start and end values can be different.
  • what if we want O(1) space complexity.

Feedback: Hire.

Coding Round 3
Duration: 45 mins
Questions: 1
Problem: Question was same to this one.
Discussion: I gave my approach based on 0/1 KnapSack. I did the dry run as well. But I mistankely wrote i instead of i-1 in dp[i] = Math.max(dp[**i**], 1 + dp[i - gift[i]]); . And interviewer noticed this mistake and pointed this out and closed the interview doc suddenly. Rest of code was okay.
Feedback: No Hire. (This was very unexpected)

Googliness Round
Duration: 35 mins (Wrapped up early as Interviewer was impressed by resume and anwsers)
Discussion: Interviewer was quite friendly. He asked about my introduction. And asked about my projects and stipulated some question on challenges with projects. Then he asked about some made up situations as well.
Feedback : Recruter said I have passed the test, and feedback is positive.

Final Decision: Your feedback is on borderline. So, we can't proceed with my profile.

ReportMark as Helpful