3 ms·

This should never ever happen. How long ago was this? I work at Google. I can try to follow up for you.

by ma2rten 10y ago

poikniok 10y ago
Are you sure about this? I believe for liability reasons no feedback should ever be given, aside from the generic "you were very good / very close" just to make people feel better about themselves.
Terr_ 10y ago
If you mean communication over the process, don't worry, I got the "regretfully decline to proceed"-type phone call afterwards. What I meant is that I can't recall any feedback like "personable, but algorithms needs work" or "code too messy" or "couldn't answer domain questions" etc. Just a general "sorry, please try again later." To be fair, this was a verbal conversation from 7 months ago, so it may be there was something like that but I was too preoccupied with the bad news to write it down.
- ma2rten 10y ago
  I see. I misread your comment, because there was another comment which said they never heard back from Google after their onsite. In that case it's true, you generally don't get any feedback after you interview at big tech companies. I would recommend to do a mock interview to prepare and get honest feedback.
- joshvm 10y ago
  I did get (prompt) feedback. I got an initial email with the rejection, and my recruiter scheduled a follow up call. I wasn't given anything specific, but I was given fairly strong hints like "I think you know that the 3rd and 5th interviews were your best". I was told that they thought my communication was clear, and that while they didn't have any issues with my code, I could have been faster and a bit more fluent converting my solutions into code. Probably boils down to what your recruiter is willing to give you, and how much you can correlate what they say to your interviews. All in all a pleasant experience, though the luck of the draw part became very obvious. Were I to go for it again, I know exactly how I'd prepare for it. The key (in my experience) is to be able to hammer out that first coding problem in under 25 minutes. If you get to the 'second stage' where you're chatting to your interviewer and trying some additional toy problems, you're doing well.

This should never ever happen. How long ago was this? I work at Google. I can try to follow up for you.

by ma2rten 10y ago

This should never ever happen. How long ago was this? I work at Google. I can try to follow up for you.

Are you sure about this? I believe for liability reasons no feedback should ever be given, aside from the generic "you were very good / very close" just to make people feel better about themselves.

Terr_ 10y ago

If you mean communication over the process, don't worry, I got the "regretfully decline to proceed"-type phone call afterwards. What I meant is that I can't recall any feedback like "personable, but algorithms needs work" or "code too messy" or "couldn't answer domain questions" etc. Just a general "sorry, please try again later." To be fair, this was a verbal conversation from 7 months ago, so it may be there was something like that but I was too preoccupied with the bad news to write it down.

ma2rten 10y ago
I see. I misread your comment, because there was another comment which said they never heard back from Google after their onsite. In that case it's true, you generally don't get any feedback after you interview at big tech companies. I would recommend to do a mock interview to prepare and get honest feedback.
joshvm 10y ago
I did get (prompt) feedback. I got an initial email with the rejection, and my recruiter scheduled a follow up call. I wasn't given anything specific, but I was given fairly strong hints like "I think you know that the 3rd and 5th interviews were your best". I was told that they thought my communication was clear, and that while they didn't have any issues with my code, I could have been faster and a bit more fluent converting my solutions into code. Probably boils down to what your recruiter is willing to give you, and how much you can correlate what they say to your interviews. All in all a pleasant experience, though the luck of the draw part became very obvious. Were I to go for it again, I know exactly how I'd prepare for it. The key (in my experience) is to be able to hammer out that first coding problem in under 25 minutes. If you get to the 'second stage' where you're chatting to your interviewer and trying some additional toy problems, you're doing well.