Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I Didn't Get Hired to Google

googleyasheck.com

Post reply on HN
Print view View original

41–50 of 101 posts

Re: I Didn't Get Hired to Google

#41

Post by [deleted] »

jps359 wrote: post #16
jasode wrote: 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.

[deleted]

Re: I Didn't Get Hired to Google

#42

Post by iplaw »

mwill wrote: post #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?

I wondered the same. I'm betting that there is more to the story.

Re: I Didn't Get Hired to Google

#43

Post by guitarbill »

jaimebuelta wrote: post #32
tyingq wrote: 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:/…

I find quite interesting the trend of "preparing for an interview at company X". I think that, ideally, interviewing should be discovering if there's a match, not set up a challenge for someone to achieve. Technical interviews should be more about doing due diligence over someone having the knowledge they say they have... not some sort of game people write books on how to train for it...

> Technical interviews should be more about doing due diligence over someone having the knowledge they say they have... not some sort of game people write books on how to train for it...

Yet they aren't, technical interviews are mostly bullshit CS questions which you barely use in day-to-day programming. And it isn't like CS knowledge is all you need to be a good programmer. Technical interviews are exactly what you say they are, a game.

And every game has rules that can be exploited. This guy's mistake was to try and completely break the game, which would have left Google with no alternative but to invent a different game.

Re: I Didn't Get Hired to Google

#44

Post by maverick_iceman »

segmondy wrote: post #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 migh…

Why not? I went through half of CLRS in three months, don't see why someone would be unable to ramp up their CS knowledge in a year.

Re: I Didn't Get Hired to Google

#45

Post by gvb »

GotAnyMegadeth wrote: post #20
jasode wrote: 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".

PPS or even better "I didn't even get a Google phone screen."

Re: I Didn't Get Hired to Google

#47

Post by philh »

minimaxir wrote: post #30
jasode wrote: 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…

I do wonder what the parallel equivalent of headline clickbait in code is. Functions with very few LOC? :P

    /* You won't believe the one weird trick this function uses to compute inverse square root */

Re: I Didn't Get Hired to Google

#48

Post by maverick_iceman »

RealityVoid wrote: post #39

Does anyone know if rejection letters from Google pre-phonecall-phase are normal? I mean, I've applied a couple of times (I might look faded compared to other brilliant people that apply and I had nowhere this guy's drive and level of involvement but thought that it is worth a shot) and every time I didn't hear anything back. I though they just contact you in case of a positive.

It is more likely if some Googler referred you like this guy. If you just apply by yourself you may not get any reply.

Re: I Didn't Get Hired to Google

#49

Post by asidiali »

mwill wrote: post #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?

That caught me off guard as well. First thought was maybe Google hired him to do the blog for some developer PR, but not sure how much sense that makes.

Re: I Didn't Get Hired to Google

#50

Post by iplaw »

RawData wrote: post #28
jaimebuelta wrote: post #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)

The guy has an awesome CV and 15+ years experience as a self-employed developer/entrepreneur...

And applying for an entry-level development position. He is not lacking in hubris, so imagine the managerial nightmare he'd likely impose for a collection of non-managers.
Post reply on HN