News for hackers. Stuff that matters.
Re:Why Google's hiring process is broken by ChuckMcM on Tuesday May 17, 2011 @07:23PM (#2558403)
Lots of interesting stories.

Disclaimer, I worked at Google for 4 years ('06 - '10) and interviewed a lot of folks (it was always a part of the job) and did a number of phone interviews too.

The process then (as perhaps now) was broken and some folks within Google understood that. The process and goals were pretty simple, hire smart people that get things done.

The process was aimed at finding smart people who get things done. That, like the phrase "largest integer" is easy to say and rolls off the lips but when you need to actually write out what it means gets a bit squirrely.

The first challenge is what does "get things done" mean? Well for college students it means you got your diploma and at the same time you contributed to some FOSS project. For people with 0 - 5 years experience it means you shipped a product where you did most of the coding. For people with 5 - 15 years experience it means you shipped a product where you did most of the coding. For people with 15 to 25 years experience it means you shipped a product where you did most of the coding.

Did you see what I did there? Google wanted smart people but the definition of smart was "you write a lot of code" and "get things done" was "that code shipped in the product/project." Fundamentally they didn't have any way to judge or evaluate the 'goodness' of what someone did if it wasn't writing code. Designers don't write a lot of code and they don't generally have a good metric for what constitutes good which can be empirically tested. The process has a hard time accomodating that. And if you're "good" at spotting problems in a process or getting folks organized around some better way of doing things? That's not measurable either.

There was a company, BASF, a chemical company which had an advertising campaign around the fact that they were part of the process and materials that made quality products, their tag line was "We don't make the products you buy, we make them better." [1] And I noted that Google was exceptionally bad at hiring "BASF" people, which is to say people who bring the quality of other work up, or products up, or processes up.

The people who did those roles in Google all started out as coders and that is how they got hired. It was only after they were working there that they (and Google) discovered they had this leveraging effect.

In order to keep bias out of the process, Google isolates the steps where bias can creep in; separated the folks who decided hire / no-hire from the folks who decided on compensation; the folks who decide to hire and the folks who decide which project they work for. For all my time there, you could not interview for a specific job, you interviewed to get 'in' and then your name showed up on a list and the allocation process would determine which project got you.

Often a candidate would ask during the interview "What would I be working on?" the only truthful answer was "That is impossible to say."

Before you even get to that point though you get into "the system." Since Google keeps a record of everyone they have interviewed or has shown up as a lead and not interviewed. There is a long, long list of people (I once joked that it was everyone in the market). If you are an employee and you might know that person, common employer, common university, etc. The system could automatically send you an email asking for your opinion on the candidate.

This isn't really any different than any other company, person X shows up in the candidate list, people who work at the company who worked at person X's company are asked if they knew this person when they were there. But it can have unintended consequences.

Lets say there is a person X, who gets hired, from company Y, and person X really didn't fit in at Y and felt really abused by the company. Now new candidates from Y generate an email to X with the standard "You worked at Y when candidate Z did etc etc." Now person X is still pissed off about how Y treated them and so they respond to all of those emails with "Yeah, candidate Z was a crappy engineer, everyone had to carry for them they never did anything useful." Maybe someone else from Y says "candidate Z was great, everyone turned to them for advice." The process of separating the interviewers from the decisions means that this feedback bubbles up all equally weighted. Hard to know that employee X has said the same thing about every candidate that has come from Y, and if the committee sees two comments one positive and one negative and there isn't anyone on the committee who knows any different then how do you evaluate?

The simplest solution if either has an equal probability of being the 'correct' assesment is that you pass on them because you can't know if you have bad data. And that was a part of the process that was fundamentally broken.

Because Google gets a metric crap load of resumes and candidates all the time, passing on someone who is +1/-1 like that makes sense because you can't know which of the two feedback comments more accurately reflects the real candidate behavior. The result is that hiring someone with a grudge can poision the feedback pool for a bunch of possible hires. If you weren't Google and didn't have this huge backlog of candidates, you might dig deeper to find out which one was the more accurate representation, but if you are Google you just move on. Externally that sometimes appears that you just stop answering the phone.

It also means that you miss out on quality people who would be good for the company and ultimately Google will have to find a way to address that issue (if they haven't already) because they are running out of people to interview.

As with most things Google, you combine a data-driven, automata friendly process with fuzzy data and alternate agenda actors, at the scale Google runs at, and you get lots of weird artifacts.

[1] http://www.youtube.com/watch?v=6ksUNyhQjLE

Re:Why Google's hiring process is broken by bluelu on Wednesday May 18, 2011 @03:51AM (#2559412)
I applied once in 2008. My recruiter was very friendly and did a great job. (I met him and another one at a presentation, and only 3 days later I had 2 onsite interviews). However, one interviewer didn't like me. When we had the open questions, he directly asked me, if the only reason I would like to work at google was because of the money. He clearly had already judged me. Then after 12 days, I got a call from someone from google from Ireland, which I didn't know, telling me that it was a very difficult decision but they wouldn't offer me a job, but I could reapply in 2 months! Naturally, I didn't do that. I still occasionaly get emails from google recruiters, but I decline.

I joined another compnay after that and did quit the job 3 months later to start my own company. If I would have joined google, I might have never done this if I would be for google. Who knows. I couldn't be happier today. And I'm probably as biased in the interviews today ("get things done"), as google was when they were interviewing me.

Re:Why Google's hiring process is broken by rakkhi on Wednesday May 18, 2011 @07:04AM (#2559719)
Had a similar experience. Google recruiter contacted me about security role on Android team, NFC and mobile payments stuff, sounded good up my alley. Sent programming skills email, I honestly said I suck at coding I work on security design and architecture. I do some coding on my own time but not upto enterprise grade. Quick chat with the next level recruiter, we don't really hire for a specific role but we will put you forward for an interview, iterate I don't code. Interview, guy is quite nice, what do you enjoy, I say what I enjoy, you didn't mention coding in that. That's right. You were put forward for a software engineering role. #facepalm. I'll see if I can get you interviewed by a security guy. Cool. About a month later email, no role for you. Lol.
Re:Why Google's hiring process is broken by rachelbythebay on Wednesday May 18, 2011 @12:09AM (#2559021)
They might also have problems keeping the "BASF" people that somehow managed to get in anyway. If hiring is job 1, retention probably should be job 0.

(BTW, your internal epitaph was posted as requested. Hope things are well with you...)

Re:Why Google's hiring process is broken by Noink on Wednesday May 18, 2011 @09:17AM (#2560024)
> The simplest solution if either has an equal probability of being the 'correct' assesment is that you pass on them because you can't know if you have bad data. And that was a part of the process that was fundamentally broken.

This is the same way some have argued elections are broken: you don't end up with the best people, you end up with the least-bad people. Since people aren't one-dimensional, those are very different concepts. Least-bad involves very little risk; you eliminate everyone who displays any risk factors at all. You also necessarily eliminate creative geniuses with a spotty record.

Re:Why Google's hiring process is broken by googInterviewee on Tuesday May 17, 2011 @07:41PM (#2558459)
Would you mind if I contact you with some questions? They don't relate to anything confidential, but they aren't the sort of things I can ask a recruiter.
Re:Why Google's hiring process is broken by ChuckMcM on Tuesday May 17, 2011 @08:33PM (#2558581)
My contact information is generally available in my profile. I realize that permission to contact is only implicit by that, I'll update my profile.
Re:Why Google's hiring process is broken by perokreco on Tuesday May 17, 2011 @09:12PM (#2558669)
Your email does not appear automatically, you need to write it yourself in your about section
Re:Why Google's hiring process is broken by sahillavingia on Tuesday May 17, 2011 @09:11PM (#2558665)
Your email doesn't show up in your profile.
Re:Why Google's hiring process is broken by ChuckMcM on Tuesday May 17, 2011 @10:22PM (#2558805)
Learn something new every day, I've added it to my 'about' section.
Re:Why Google's hiring process is broken by salemh on Tuesday May 17, 2011 @09:54PM (#2558761)
Some string / wildcard Google searches comes up with at least one email.