Solicited by Google recruiters but never applied: a) I don't think Google is a place for me in terms of age and society. b) I don't come from a CS background, am self taught but have over 12 years of professional experience behind me - I know what I am doing but can't rant of algorithms off the top of my head.
I don't come from a CS background, am self taught but have over 12 years of professional experience behind me - I know what I am doing but can't rant of algorithms off the top of my head. During an interview when I couldn't answer a question about CS theory I drew on something I learned as an English major: the analogy. I said: "Imagine that you aren't a tech company hiring a developer. You are a band hiring a lead g…
Poll: Have you ever applied to work at Google?
51–60 of 103 posts
Re: Poll: Have you ever applied to work at Google?
#52How about "I applied, was given an offer, but rejected it"?
Re: Poll: Have you ever applied to work at Google?
#53Its a pretty interesting story so I thought I'd share:
I applied through the traditional on-campus recruiting at UC Berkeley. Got past the first round of interviews on Berkeley's campus and then was taken to the Mountain View campus for 4 interviews and a bunch of events. That night, I got a call saying that the interviewers really liked me and recommended that I be hired. At most companies, that would mean that I was made an offer. Instead, they have these "hiring panels" where executives from various departments take a look at your resume, the notes from interviewers, and your transcript / other related documents. 3 weeks later I got an e-mail saying I was rejected during one of these panels. These people never met me; in fact, the 6 people who had met me all recommended that Google hire me. It was kind of weird, since no other company I had applied for had a process where people who hadn't interviewed you made the final decision on whether you should be hired.
Obviously, I am a little frustrated by it - so take this with a grain of salt. However, I think that my experience was emblematic of a few specific issues with the hiring processes there (though they have some amazing processes as well):
1) People who've never met you should not be pontificating in large panels about whether you would be a good fit. That just doesn't make sense.
2) Google has a very strong academic focus on hiring. It is clear when you interview with them that they care a lot about top-brand schools and top GPA's. They seem to believe that the best students will make the best employees. I am not sure, but I think the reason I got rejected may have to do with two C's on my college transcript (which is not indicative of my inability to Ace calculus but rather my lack of interest in attending class). Personally, I think the academic focus is much to their detriment - and a major part of the reason they've struggled at social. That said, Google has some brilliant people who I'm sure I would've loved to work with :). Take this answer for what it is but hopefully you'll find it valuable.
Re: Poll: Have you ever applied to work at Google?
#54Don't we also need: I applied and heard nothing back I applied, had a phone interview and was rejected I applied, interviewed in person and then was rejected I applied, was offered the position and turned it down. PS I fall in the applied and heard nothing but crickets back column -- i feel so ashamed, HN hold me and tell me it will all be okay :(
A great story of persistence, until the last bit. Were you just playing a game of tit-for-tat hard-to-get against Google hiring managers? Joking, but I am actually curious why you finally said no.
Re: Poll: Have you ever applied to work at Google?
#55Solicited by Google recruiters but never applied: a) I don't think Google is a place for me in terms of age and society. b) I don't come from a CS background, am self taught but have over 12 years of professional experience behind me - I know what I am doing but can't rant of algorithms off the top of my head.
Google hired me with 10 years professional software development experience and no CS degree. Google hired my friend with similar years of experience and no high school diploma.
Re: Poll: Have you ever applied to work at Google?
#56Anyway, I'd prefer to work on doing my own thing, and build an awesome startup, than go to work for any big company, Google or otherwise. Hell, even Lulu felt big and bureaucratic to me when I was there, and they were only about 100 employees at the time.
Re: Poll: Have you ever applied to work at Google?
#57Re: Poll: Have you ever applied to work at Google?
#58Earlier quoted context omitted.
I'll mention a related question I've been pondering on lately: how does one assess his own skill level? When one has people around who are clearly more able programmers, one can take the chance to learn from them and try to achieve their skill. But when you believe you might be the top programmer around your office, how do you determine whether you're really good, or you're just in a not-so-great environment? A lot o…
"The reason for failing to be hired is invaluable feedback on your shortcomings, which are much harder to self-assess." Good luck trying to get any useful feedback from a Google or Facebook rejection. Often it's just random.
Re: Poll: Have you ever applied to work at Google?
#59Earlier quoted context omitted.
I don't come from a CS background, am self taught but have over 12 years of professional experience behind me - I know what I am doing but can't rant of algorithms off the top of my head. During an interview when I couldn't answer a question about CS theory I drew on something I learned as an English major: the analogy. I said: "Imagine that you aren't a tech company hiring a developer. You are a band hiring a lead g…
I absolutely love that analogy, especially as an amateur self-taught guitarist + programmer. I'd still not be too inclined to apply anywhere with a heavy CS slant, even though all the theoretical stuff interests me a lot.
I'm with you there...I don't think I'd fit in at a hardcore engineering shop like ITA where you'd have to live and breathe algorithms. But at places where you're just building and maintaining straightforward web apps, you don't need to be able to give a lecture on computer theory, you just need to know how to code, and how certain practices affect security, scalability, performance, or maintainability. These are the places where you'll find CS guys who like to talk a big game, but the codebase is messy and full of hacks. In my experience, the CS guys at these places spent all of their time learning theory and how to architect on whiteboards at school, but they never learned how to write good code. This is where I shine, because when the lights go down and the crowd goes silent, no one cares about how many chords you know, or whether you can play a harmonic minor scale...they just want to know if you can hit notes.