Google · Primly Community

Google interview rejection post-mortem, what I'd change if I went back

qa_quinn · 6 replies

Failed my Google onsite last spring for an L4 SWE frontend role. I've had enough time to actually process it, so here's the honest breakdown rather than the immediate coping-mechanism version.

The loop structure (for L4 SWE, 2025): Two coding rounds, one systems design, one behavioral (Googleyness + leadership). I had a fifth round that the recruiter described as 'additional data collection' which I think means they weren't sure after four rounds.

Where I actually lost it:

Coding round one: got the medium-difficulty problem fine. The follow-up asked me to optimize for space complexity and I fumbled the explanation even though I knew the answer intuitively. I was talking myself in circles. The interviewer stayed blank the whole time, which rattled me more than I expected.

Systems design: I knew frontend system design cold (virtual DOM, CDN strategy, lazy loading, component architecture) but I spent too long in the problem definition phase and ran out of time before getting to the interesting tradeoffs. Google interviewers apparently value depth over breadth and I breadth-ed myself to death.

Behavioral: I answered the 'tell me about a time you disagreed with a decision' question too vaguely. I was trying not to sound like I was criticizing a past employer. In hindsight, specificity would have helped me here. Vague answers don't score well against the STAR rubric.

What I'd change:

More timed mock sessions, especially with someone who stays quiet and just watches. The blank-face thing was something I hadn't prepared for.

Practice talking through my thought process at the same time as writing code. I usually code quietly and narrate after. That's backwards for Google interviews.

For behavioral: commit to one clear disagreement and walk through it fully rather than softening everything. They're not looking for a perfect diplomat. They want to see how you actually handle conflict.

The outcome: Got a generic feedback email with three bullet points that told me nothing specific. I know that's standard. Asked my recruiter for more detail, got a slightly warmer version of the same bullets. The process isn't designed for feedback, which stings when you're trying to actually improve.

Reapplying in fall 2026. Not giving up on it. Just going in with different prep.

6 replies

de_derek

The 'coding quietly and narrating after' thing. I did this exact same thing in my Google loop for a data engineering role and it cost me. One interviewer literally said in feedback (relayed via recruiter) 'candidate reached the solution but reasoning was unclear.' I was working fine, just silently. Practice narrating out loud while you code, not after.

staff_steph

Re: the blank-face thing. That's deliberate Google interviewer training. They're told not to give positive or negative signals because it biases the candidate and affects the data quality. It's legitimately disorienting the first time you experience it. The prep advice I've seen that actually helps: practice with someone you trust who will stay expressionless on purpose.

frontend_fran

Yeah I didn't know that was intentional until after. Would have helped to know going in. Makes sense from a consistency standpoint but it's brutal in the moment.

newgrad_neil

How long did you have to wait before being eligible to reapply? I've heard 6 months, I've heard 1 year, I've heard it varies by role.

frontend_fran

My recruiter told me 12 months for the same role family but suggested I could apply to a different team/area sooner. I'm not sure how strictly that's enforced. Probably worth asking directly rather than assuming.

qa_quinn

The feedback-that-tells-you-nothing thing is so consistent across the industry. I get that there are legal reasons but it's frustrating when you're trying to actually debug what went wrong. Props for doing your own honest post-mortem instead of just writing the loop off.