My Google HR Response
Thoughts? Do you hire non-degree holders?
---
Hi (HR person),
Thank you for your reply. I had to think about this for a bit, as Google is the first company/client I have ever had ask about my degree (or lack of).
Unlike other disciplines like mechanical engineering or architecture, we programmers can start at an early age building virtual things, exploring complexity and simplicity. Many of us spend a considerable amount of time studying the science, rather than just coding.
I have had a lot of exposure to CS graduates over the past year, at a highly regarded UK university. Of those I encountered, most of students were doing it because they were bright and didn't know what to do with themselves. Some "downgraded" (as they saw it) from maths or physics because it was harder than they thought. Of the remainder, half were ego driven coders and half were actually any good. The very few that were good nearly dropped out because they were not excited enough (and some of them even ended up coding cool things alongside me).
You can't build amazing things without science, and the Internet means I don't require a degree to learn the science to build cool things. I can do that on my PC, right here, very cheaply and efficiently.
I do accept that the cost of exploring what excites you most without the formal structure of a degree has its costs (such as being filtered out of Google's hiring process) ... despite this I wouldn't go back and earn a degree if I had a time machine, so that's a cost I happily accept.
One of the beautiful things about programming is its immediate availability to all who want to learn ... even those who decide to do things differently.
I hope Google would in future take a longer look at people learning on their own steam, in their own time and out of love.
Regardless, I've very much enjoyed talking with you and I hope you find great candidates for the positions.
Thank you for your time! (me)
26 comments
[ 3.1 ms ] story [ 68.1 ms ] threadBottom line if they are letting alot of talent slip thru the nets due to this rigid policey then eventualy they will create competition.
One does wonder when you read all these stories of big companies formed by people who quite doing there degree's half way thru and then read about a big company insisting that all employee's have a degree. Just have to laugh and move on.
I was once at a interview were the HR people were assholes like that though the IT manager in a seprate interview was blown away with my skill's and demostrated abilities and offered me more than what I was asking for, I turned them down due to the experience I had in the HR interview prior to the technical interview and told them why as well. Took a lesser paid job at a company called RAND who I had also interviewed with that same day. Had HR not been so rude and downright insulting due to my age etc, then I would of taken there job offer. Retrospectivly though I did make the best choice in the end, which was comforting.
I am a little biased as another dropout but many technical job adverts here in the UK not only specify a degree but that it must be at least a 2:1 from (whatever HR/the manager thinks is) a "respected university"!
5 years ago I applied for a technical support job at an extremely low salary (I was relocating and applying for anything I saw) and got a phone call saying they'd got my CV but needed to know if I had a degree. I'm sure finishing my degree in formal derivations of algorithms would have been highly useful for a job crawling under desks looking to see if any cables had fallen out. Luckily in the month it took them to phone me and ask I'd found a much better job.
Basically at the time (2007 - 2009) they had a very firm "No degree, no job." And a more insidious, "if you get acquihired in and the job you are in would normally fall under this rule, and you don't have a degree, we manage you out of the company."
Given the size of some of their later acquistions I don't know if they could stick with that model or not.
That said, I don't know what they're doing for people who apply the "regular" way.
1) Make sure he had a LinkedIn presence
2) Create a Github account and put one or more projects in it, preferably written in one of Java, Python, or C++
3) Register with StackOverflow and build up some karma.
Then let the trawler pick you up the next time it goes by :-)
When I was choosing a degree I often heard that people with Classics degrees found it easy to get recruited as programmers. I have no idea how true that is but my former boss took that route. I dropped out of my CS degree and often wish I'd studied something language-related instead.
(I didn't really know what CS was before I started studying it - what I really wanted was to learn to take my programming to the next level of turning little 100-line programs into real projects, which I know now is almost unrelated to theoretical CS and really just needed a little more reading and a lot more practice. This was in the days before StackExchange and Github, or I might have worked it out in time to save myself from being yet another CS dropout.)
Also, my father has told me (being more of that generation), and I have read, that many early entrants into the CS field had backgrounds in linguistics.
That said, the described Google policy of degree trumping ability, I find disappointing.
However, from a point of analysis, it's a simple filter, and after applying it, a "premier" venue like Google will still have a significant oversupply of highly qualified candidates.
But... it puts me in mind of Google's reputation for support: You only get a response if you're one of "the important people".
Don't count on your "looks", Google; they don't last forever.
Still if Bill Gates applied, I guess he'd get rejected as well. Same with Zuckerman, many others as well. Guess your qualified to start a big empire yourself by not having one.
That said, as a Googler, I understand why they will hire non-SWE with phds in chemisty, neuroscience, or particle physics or what have you -- it's because Google has unique problems to think about that are not just pure software engineering. For instance, how do you scientifically evaluate the current search quality and ensure that it continues to improve? Google is very research-oriented and data-driven, and this spills over into the SWE work so it's not always 100% about building good software.