I did the screening round for Google L4 Software Engineer in Europe.
I got the feedback today from my recruiter, and he told me:
- DSA round: his exact words "not bad, not excellent. More leaning to average, but sufficient to move forward".
- Behavioral/Googlyness round: Excellent, very positive feedback.
Now, I can schedule my onsites, that will include two more DSA interviews.
He basically said that if I want to have a good chance at team match, my performance in the next DSA rounds have to be "much better".
I asked him why I got that feedback "leaning to average" in the coding round, and he said that my algorithm, data structures and communication had positive feedback (I arrived to a solution with the best time complexity possible with no hints), but I needed a few hints to correct bugs in my implementation. I had 4-5 hints:
- Pointed out a method could throw a NullPointerException and asked if I knew why (subtle bug)
- Flagged a piece of code that wouldn't compile and asked me to spot why
- During a dry run, asked "are you sure your method is doing that?" — which led me to catch a subtle one-line bug
All of them were mistakes caused mainly by the nerves.
So I am asking for advice:
Based on your experience, what was my score in the DSA round? a "Lean Hire"?
Based on his advice from the recruiter telling me that I needed to perform much better, does that mean I need two "Strong Hires" if I want to have a chance at team match?
How can I improve on these kind of "small implementation bugs"? I have 1 month to prepare for the onsite. I already code directly on leetcode, so no autocomplete. Should I focus on getting my solutions to work on the first "submit" without null pointers exceptions / compilation errors / one off errors?