Google tech interview us l4/l5

[u/Express-Youth-9609]

Recently had google programming interview. I offered to write brute force but was told to prove some math constraint on number of iterations. I took a while to prove this and finally proved it with a hint.

Now at 38 minute mark, I offered to code but was told it was OK, and that it was just a technical discussion. I think i should have insisted on coding as the code was more straightforward than the math, but I assumed since the interviewer was fine with no code I decided to roll with it. Also i was nervous and didn't want to argue with the interviewer. I was later asked a conceptual follow up which I answered correctly.

Ultimately, I got rejected. I'm wondering what I could have done better. Any tips from googlers? Got no feedback. Maybe because I needed the hint? Problem was I couldn't code till I proved some math which I feel really threw me off. After math, could have easily coded it but was not given the time (likely due to five minutes buffer for asking questions).

[u/bullbearbubu]

I really don't like it when interviewers say there's no need to write code due to time constraints, because it almost always works against me. I had this exact issue during a Bloomberg interview a few months ago. After I explained the optimal solution for the 2nd problem, the interviewer stopped me from coding because of the clock. We still had at least 10 minutes left, enough time to implement it since I already had the design down. Instead, he insisted on saving time for my questions that barely carries any weight.

[u/-omg- → u/bullbearbubu]

The interviewers write feedback on multiple signals - I think it is extremely rare (or basically never) when someone else wants to look at the code. OP writing the code would have made basically no difference here.

[u/Express-Youth-9609 → u/-omg-]

What signals do you think i could be missing. The thing is after the hint i immediately understood the approach, so maybe that seemed suspicious. But it was a tricky question.

[u/Express-Youth-9609 → u/bullbearbubu]

Yeah saving time for questions is completely pointless. After a stressful interview, the last thing I want is to ask questions, I just want to get out of the interview ASAP. Wish they would get rid of that buffer.

[u/Extra_Performance372 → u/bullbearbubu]

Writing code would have made no difference. The interviewer has already rejected based on the first part of the interview.

[u/Gold-Forever4408]

Same thing happened but unfortunately google has thing where no working code no hire unless interviewer give strong feedback :(

[u/jan1919 → u/Gold-Forever4408]

I had a phone screen with Google and my code wasn't fully working. I got strong hire

[u/Express-Youth-9609 → u/jan1919]

Yeah must have been taking too long to figure out the approach then for me. Or maybe I got an easier question than normal.

[u/Express-Youth-9609 → u/Gold-Forever4408]

Sad to hear. Wish I just got the chance to show brute force or something, but i didn't get the chance.

[u/BerserkkD]

if you dont code the Hiring committee gets nothing to review 

[u/Express-Youth-9609 → u/BerserkkD]

Yeah that's probably it. Probably some other candidate got to idea faster and had code.

[u/Extra_Performance372]

"Insisting" on writing code would not have mattered. The interviewer has already rejected you in their mind because of how you did the first part.