A Wretched Google Interview Experience
symbo1ics.com
A Wretched Google Interview Experience
1–10 of 359 posts
Re: A Wretched Google Interview Experience
#2However IMHO the author should have told them NO, and why, much earlier.
Shame on you google - take dozen emu eggs, break into a bowl, whip up and apply to face.
Re: A Wretched Google Interview Experience
#3Fascinating reading - makes me realise just how rusty my theoretical CS knowledge is (I haven't used lisp or some of that sets notation since 1990!) However IMHO the author should have told them NO, and why, much earlier. Shame on you google - take dozen emu eggs, break into a bowl, whip up and apply to face.
And of course there's always the "if you say 'no', there's always someone who will take your spot happily."
Re: A Wretched Google Interview Experience
#4Fast forward 3 years, and I had another poor interview experience with google. I flew up there this time, and got to interview in person. It was fun to see the google plex. I had 5 interviews in person scheduled. I felt like I ace'd 3 of them, 1 of them I did OK, and 1 I bombed. 2 days later google informed that that I was not a "culture fit".
I am not sure what the deal was. I felt like I had rapport with all of the interviewers, and I also had 2 internal recommendations. So, maybe that was some canned response way of saying no. Or maybe it was literal.
At any rate, I will never try to apply to google again, even though I too am contacted by a google recruiter no less than every 6 months. Sigh.
Re: A Wretched Google Interview Experience
#5I know a couple of googlers, talented programmers, but they ended up as "yet another CRUD" python devs there.
Re: A Wretched Google Interview Experience
#6Re: A Wretched Google Interview Experience
#7So, did you not sign the NDA where you agree not to discuss the content of the interviews, or are you just throwing caution to the wind here?
Re: A Wretched Google Interview Experience
#8Fascinating reading - makes me realise just how rusty my theoretical CS knowledge is (I haven't used lisp or some of that sets notation since 1990!) However IMHO the author should have told them NO, and why, much earlier. Shame on you google - take dozen emu eggs, break into a bowl, whip up and apply to face.
Saying "no" is a hard stance to take. Google undoubtedly does have some very smart people and some very interesting work, so it's difficult to throw that away because one perceives them as brain damaged when it comes to relationships and interviewing. And of course there's always the "if you say 'no', there's always someone who will take your spot happily."
Re: A Wretched Google Interview Experience
#9So, did you not sign the NDA where you agree not to discuss the content of the interviews, or are you just throwing caution to the wind here?
Seriously, if a company I interview at is genuinely threatened by me talking about my interview and questions, maybe they should reconsider their viability as a business--things being so precarious and all.
NDAs for employees generally seem to be bad signs for places worth doing business at.
Re: A Wretched Google Interview Experience
#10I'm glad that Google doesn't just blindly look at credentials alone. If you got a PhD, and got featured in a CS publication, but couldn't answer their questions, then you probably shouldn't be accepted. That said, OP just had bad bad luck. My phone screen question was FAR easier (I still messed up on it, and got to the on-site too).
Disclaimer: I went to a Google interview last week (got rejected)