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

Google | L3 | Onsite

Author
  • Shared Anonymously

I had 3 onsite coding rounds recently.

  1. I came up with the optimal solution in 1 min. The code was a bit lengthy and got a little clumsy. I missed one small edge case in this round but when interviewer told me to dry run it in an example i took care of it. Recruiter shared a rough feedback - code complicated, Edge case handling missed.
  2. I was asked one question and a follow up for it. For original question I coded the optimal solution & the follow up question was a bit lengthy and different from first one. So, i just pseudo code for it. I had 2-3 mins to code it out & i think i missed one or two things in the pseudo code.
  3. In this round i came up with nlogn approach instantly after some observations. The question was a bit open ended and had to ask a lot of clarifying questions. I established my assumptions for the question, pointed edge cases and told nlogn solution. He asked to optimise is to n. I was not able to completely find the solution approach but he gave me some hints to see through it and then finally i wrote the solution for it. Handled edge cases gracefully but missed a simple logic check in one of the function. Although the interviewer seemed pretty good and i was constantly trying to think of some approach for the problem.
  4. Googliness pending.

What rating will i get in these rounds based on your understanding?

ReportMark as Helpful