Over a million developers have joined DZone.

Thoughts on Google Worship

As much as I admire someone for setting and reaching for a goal, I'm torn about a developer who's taking seven months off to reach his goal of becoming a Google engineer.

· Agile Zone

Learn more about how DevOps teams must adopt a more agile development process, working in parallel instead of waiting on other teams to finish their components or for resources to become available, brought to you in partnership with CA Technologies.

This week, a GitHub repo called google-interview-university popped up on the radar when it hit Reddit and Hacker News. Go ahead and check it out.

The tl;dr is that an early-forties self-taught developer named John with an Econ degree and about fifteen years of varied startup experience has compiled a lengthy and thorough study guide of sorts that he is using to try to get a job at Google. It contains hundreds of links that run the gamut — tips from Google recruiters, books to read, articles on data structures, questions to ask in the interview, and even a link to a PDF file that says "future Googler" with the colorful Google logo suitable for printing (you know...because you should print a sign) — all courtesy of a man who uses the domain googleyasheck.com.

According to his LinkedIn, John has been studying full-time since April of this year to reach his goal of becoming a Google engineer.

Insert sound of brakes screeching. 

A guy that has been programming since the TRS-80 days and doing stuff with the web since 2000 and runs his own startup is taking off seven months to try to get a job at Google?

I'm not sure exactly what is wrong with this picture, but something feels wrong.

It could be that someone is investing an awful lot of time into a goal that, when they reach it, might be entirely unfulfilling. This isn't meant as a knock on Google at all - but clearly, Google isn't going to be a great fit for everybody.

Maybe it's that an experienced person already in the industry who is probably qualified for a substantial number of programming jobs and even less technical roles (Product Manager jumps out at me) at hundreds of other companies still may need (or felt the need) to spend over one thousand hours studying just to get past a few hours of interviews with Google.

And what if it doesn't work out? I'm absolutely rooting for John no matter what (I can't imagine his enthusiasm and newfound fame won't help), and I guess if he has a bad day on the phone screen and fails, he could still take his knowledge to some other elite companies that could hire him.  

Reaction from the web has ranged from laments on the effect of Google's "CS trivia" interviewing style on the industry to cringeworthy Google fanboyism to admiration for a guy who is working hard to achieve a goal. All have some level of validity.

I see Google worship on a fairly regular basis on Reddit, and I've previously written about this fixation many new college grads have on the "Big 4" (or Big 5) companies. It's rare to hear of senior level candidates having the same enthusiasm, and rarer to see someone taking months off of work to try and qualify for a new job.

As much as I admire someone for setting a goal and working towards it, I'm torn.

Discover the warning signs of DevOps Dysfunction and learn how to get back on the right track, brought to you in partnership with CA Technologies.

Topics:
google ,job search ,agile ,software engineer

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}