I got rejected... Here's how it went
Question 1: fizz buzz PRINT not store. Answered it straight...
Question 2: fizz buzz don't use modulo or division. Also keep O(n) time complexity. Also keep constant space. I struggled a little as in I thought out loud, but got a solution (a bit different from Leetcode because LC asks to preserve the fizz buzz in an array which is easy. Google wanted to just PRINT it out). Did walkthrough. Everything within time.
1 Took too long - I kinda understand but not really... But for 45 min I thought I did okay? Can someone shed light on this? Q1 looked like LC easy and Q2 as LC medium?
2 incorrect solution - Not true. I even ran my code after the interview. It was fine. When I put it on Leetcode and tweaked the array thing I got 97% faster than other results.
3 Needed hints - Not true...at least the South East Asian accent was so hard to hear that whatever he said only added more stress. I couldn't understand anything. Also he was very silent overall...and he seemed generally unfriendly.
Overall I'm so devastated...if I were going to be rejected, I would want to deserve it...I don't think I deserved it in this case.
It happens. Interview involves some luck.
As I keep quoting from a blog:
The thing is, Google has a well-known false negative rate, which means we sometimes turn away qualified people, because that's considered better than sometimes hiring unqualified people. This is actually an industry-wide thing, but the dial gets turned differently at different companies. At Google the false-negative rate is pretty high. I don't know what it is, but I do know a lot of smart, qualified people who've not made it through our interviews. It's a bummer.
But the really important takeaway is this: if you don't get an offer, you may still be qualified to work here. So it needn't be a blow to your ego at all!
As far as anyone I know can tell, false negatives are completely random, and are unrelated to your skills or qualifications.