Comment Google interviews: Dehumanizing waste of time (Score 4, Insightful) 358
Usually double-blind is a good thing, like when doing a scientific study or reviewing one. But in the case of Google, the hiring method (for software engineers) involves a sequence of engineers asking you to solve toy problems and scribbling notes on a single sheet of paper. That single sheet of paper is mostly what the hiring committee sees, along with your resume (which nobody looks at any more than superficially) and maybe some comments from your recruiter. There is absolutely no consideration of things like personality, team work, cross-polination from other fields, or even CS disciplines outside of software engineering (they do 90% algorithms, 10% computational complexity, 0% operating systems, 0% computer architecture, 0% programming language theory, 0% anything else).
I have a PhD in computer engineering, and I currently I work as a CS professor at a major SUNY research center. Based on Google’s request (they called me!), I interviewed at Google's NYC office for a software engineering position (although my research area is computer architecture, which they didn’t quite seem to understand). I went there, I was friendly and didn’t stick my foot in my mouth, and I answered all of their algorithms questions (some I could have done better, but I think I did a good job). A few weeks later, I get a call from my recruiter. They were declining to make me an offer for two reasons. One was some vague statement about me not fitting with their culture. No idea why. The other was that I had appeared to have jumped around jobs too much. That last one made no sense. I worked one industry job for almost a decade, then I went to grad school (where I worked a research assistant and did a couple of internships), and then I got hired as a professor. How does that constitute jumping around too much?
I checked out Google’s hiring practices on glass door (before I interviewed, of course), and I see a similar trend. Google has no compunctions against wasting people’s time. They regularly cold call people to interview and then decline to make an offer, even for people with doctoral degrees and/or substantial industry experience. I have two good friends who work at Google, and they’re brilliant at computer science theory, but even so, I still really don’t know what Google is looking for.
Of course, maybe I just suck, and Google figured it out. I doubt it, though. I have a PhD for Ohio State, my dissertation is 120 pages (not including references), I currently have 13 major publications, three at top-tier conferences, first author on 9. I recently won an NSF CAREER award ($450,000 over 5 years). I started the Open Graphics project, which is basically dead right now but did produce real open source graphics hardware. And before all that, I worked in a small company where I had to do everything from tech support to IT to software development in a dozen languages to chip design. Among many other things, I designed a graphics accelerator ASIC that’s present in most air traffic control towers around the US (among so many other things I can’t keep track of). In the early 90’s I released ANSITerm for the Atari ST, which was very popular at the time and is still a very popular BBS terminal program among retro computing enthusiasts. I’m pretty sure I don’t suck.