Live data from Hacker News

I Didn't Get Hired to Google

googleyasheck.com

11–20 of 101 posts

Re: I Didn't Get Hired to Google

#11
No surprise. You can learn a lot in a year, but you can't level up your computer science knowledge in a year. Some people might be offended or disappointed by this comment, but don't. Just keep your heads down, learn a lot, expose yourself to lots of different things and the experience will come with that.

With that said, I'm not surprised that he didn't get a phone interview. Even if Google knew about him, they might want to let people know that their interview process can't be gamed. If I was hiring, I might be concerned that someone who put in that much effort, might stall once they get hired. I want someone who has put that kind of effort not leading up to the interview, but over the years due to genuine curiosity due to love of computing and not because they want to get a job.

Re: I Didn't Get Hired to Google

#12
Posts of people crying so much about not getting hired by a company (usually Google) are top cringe.

It's like writing on Facebook that you feel miserable because a girl rejected you.

Just move on, kid.

Re: I Didn't Get Hired to Google

#13
post #4

He made an extensive repository of information on how to get hired at Google[1], gave talks on the subject[2], and studied full time for 8 months[3]. And it's not that he interviewed and didn't get the job...they didn't even let him interview, not even the phone screen. That's pretty rough. [1] https://github.com/jwasham/google-interview-university [2] https://googleyasheck.com/presenting-at-code-fellows/ [3] https:/…

pretty depressing

Re: I Didn't Get Hired to Google

#16
post #6

Title says: "I Didn't Get Hired. Here's Why." Body says: "Why didn't I get hired? I don't know why." Real question to HN readers: Do you believe this type of inconsistency also affects writing code ? In other words... if a hiring manager notices this muddled writing in a blog post, is it fair to think the programming output will also be muddled? (e.g. function names, architecture, engineering the organization of micr…

It's just a typical click-baity title. I don't think it has anything to do with ability to write code.

Re: I Didn't Get Hired to Google

#17
Two things:

He lists himself as an 'Autodidact', I wonder if he has a BSc and if not, if that contributed to not getting a phone screen. If it did, thats pretty rough since he also lists 15 years of experience.

Also I'm very curious about this comment on the post:

Honest question: who told you to make this blog? Email me john@techcrunch.com

Not quite sure what he's implying by 'who told you', anyone know?

Re: I Didn't Get Hired to Google

#18

You didnt get hired at google because you have no life, no sense of self. Your entire blog is about how you make yourself hireable by google. Who cares what google wants. What do you want?

Surely you can communicate that sentiment without wording it quite so harshly?

Re: I Didn't Get Hired to Google

#19
I wonder if his lack of CV (of any kind), no matter how much he studied was what made recruiters discard him right away.

You can learn a lot in a year, but you can't create a CV containing a career that may look attractive.

(Google process is pretty much optimised to quickly discard applications)

Re: I Didn't Get Hired to Google

#20
post #6

Title says: "I Didn't Get Hired. Here's Why." Body says: "Why didn't I get hired? I don't know why." Real question to HN readers: Do you believe this type of inconsistency also affects writing code ? In other words... if a hiring manager notices this muddled writing in a blog post, is it fair to think the programming output will also be muddled? (e.g. function names, architecture, engineering the organization of micr…

The current HN title "I Didn't Get Hired to Google" makes it sound like someone quitting a job because it turned out their job was just googling things. Perhaps it should be "I Didn't Get Hired By Google".

PS or even better "I didn't get hired by Google".

Post reply on HN