I went through Google’s behavioral/HR round for a Backend Engineer position, and it put a surprising amount of weight on the details. The whole conversation was framed around the classic behavioral style of evaluation—how I’d respond, how clearly I’d explain my thinking, and how I’d connect my experiences to the kind of work Google cares about.
What stood out most was how much my answers depended on being precise rather than just sounding confident. I found myself re-checking how I described events: the sequence, the tradeoffs, and the outcomes. Even when the themes were familiar, the round felt like it rewarded thoroughness, because vague phrasing left too much room for misinterpretation.
6 months ago
My hardest moments weren’t just about solving the problem—they were about understanding the problem in the first place. I ran into a coding interview where the interviewer didn’t present much visually; they preferred to describe the question using words rather than typing or showing a board. That made it extremely difficult for me to fully grasp the constraints and edge conditions early enough to act confidently.
From there, the overall process felt punishingly tough. I experienced long stretches between rounds and minimal feedback, and the interviewers felt like a mix of unpredictable styles. Sometimes it was hard to know what mattered most, because the questions weren’t reliably “general” in the way I expected—they could come from an internal pool and still expect a specific kind of approach.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
