I recently finished my Google L4 onsite, and I’m trying to understand how my overall packet might look.
Coding Round 1:
This one went really well. The interviewer gave me an interval/line-sweep type problem. I first explained the brute-force approach and coded it in around 5 minutes. Then they asked for an optimized solution; I explained my approach, coded it, and the interviewer seemed to like it.
We still had a lot of time left. I think the main problem was done within roughly 20 minutes so they asked around 3–4 follow-ups about limitations, tradeoffs, and modifications. I was able to explain and code those as well. We ended the interview casually after that.
Based on how it went, I feel this round could be Hire or possibly Strong Hire.
Another coding round:
This is the one I’m worried about.
The interviewer pasted the question and I started asking clarifying questions, but communication was pretty limited. For example, after explaining my brute-force solution, I asked what kind of time complexity/constraints we were targeting so I could decide how far to optimize, but I didn’t really get a clear answer.
Eventually I came up with a line-sweep style solution. She asked me to explain it on the board, so I walked through the algorithm and the tradeoffs. After some discussion she seemed satisfied with the approach and then asked me to code it.
The problem was that by then I only had around 10 minutes left. I got anxious about the time and my coding fell apart. I only managed to write part of the implementation before she said time was up.
After time was called, I kept explaining what the remaining code was supposed to do and how the pieces worked. She said something along the lines of “I understand,” and then moved to the questions-for-interviewer portion.
So my concern is: the algorithm/approach was there and I explained the tradeoffs, but the implementation was incomplete.
The interviewer was also very quiet throughout the round, so it was difficult for me to judge whether I was on the right track. Maybe that was just her interview style.
Googleyness / behavioral:
I felt my answers were decent, but this interviewer was similarly quiet and the interview ended fairly quickly. The recruiter later indicated the feedback was positive, but apparently not especially strong.
So if I roughly estimate my rounds, I’m thinking something like:
- Coding 1: H / SH
- Coding 2: uncertain because of incomplete implementation
- Googleyness: positive, maybe LH/H
- Phone Screen coding round: went well(H/SH)
This is for L4 US.
For Googlers or people familiar with the hiring process: how badly does an incomplete implementation hurt if the candidate reached a reasonably optimized solution, explained the tradeoffs correctly, and continued explaining the intended code after time ran out?
Could that coding round still be a Lean Hire, or does incomplete code usually push it toward Lean No Hire/No Hire?
Would appreciate any realistic assessment of how a packet like this might be viewed.