Earlier quoted context omitted.
How does this work in practice? If there are consistently used questions and specific criteria for assessing responses, can a candidate just learn the likely questions and what constitutes the "right" answer?
This is a good and important question. Also: while I have a lot of respect for people at Google trying to innovate on hiring, make no mistake: Google's heart is in the right place, but they aren't at the forefront of structured hiring, and their hiring processes are notoriously capricious. The reality is that generating good questions for a structured interview is difficult. You can't just pose a programming problem.…
The Utter Uselessness of Job Interviews
151–160 of 410 posts
Re: The Utter Uselessness of Job Interviews
#152I find it quite problematic that researchers get to talk about their own research and present it as facts without anyone taking a critical look. Over time I’ve become more skeptical about this kind of psychology research (as more studies fail to replicate) and, as is often the case, here the sample size is quite small (76 students, split across 3 groups), predicting something relatively noisy as GPA. It is unclear to…
People ask questions in interviews that they want to know the answer to and that could go either way. All questions have equivalent expected surprise, either both answers are unsurprising, or one answer is surprising, but you think you already know the answer is the other one.
If interviewers were asking questions like "is 2+2=4" they would have detected random interviewers way easier, but they wouldn't be trying very hard to get to know the person.
As for getting to know the person, the more surprising someone's answers are, if you believe they are telling the truth, the more distinguishes them from "average person who gave answers I expected", so you say you "got to know" them. This is unsurprising.
This isn't to defend unstructured interviews, other studies for a long time have shown them to be worse than structured interviews and test scores. If I had to guess the only reason the research in the article got published as novel was the random interview part.
Edit: Here's a table from a meta-analysis of lots of studies on correlation between different factors and job performance: http://imgur.com/a/YRFTh. Basically unstructured interviews aren't as good as structured ones, but they are better than nothing. Work samples are the best, structured interviews and IQ tests tie for second.
Note that this meta-analysis is combining a bunch of different fields to yield general observations, a specific field may have different results. But in expectation for a randomly selected field these are fairly solid results, and I don't expect fields vary from them too much.
Re: The Utter Uselessness of Job Interviews
#153How do you know that the person you'll be marrying won't cheat on you and won't leave you in hard times? If you apply the methods we use today for interviews you'll end up with a 50/50 chance at best, a coin toss. Yet why do some marriages last forever (till death do us apart) while others fail miserably or crumble even after 20 years? The search for the global optimum cannot be performed by asking a set of questions…
I think it would be cool if a company like Google published anonymized data about the correlation between interview "scores" and some post-hire metrics. My guess is the correlation would be poor to non-existent. Picking those metrics is difficult, perhaps an obvious one that is difficult to game is how long the employee stayed with the company. Another interesting one would be anonymous peer evaluations where it's guaranteed no one would see the data points so it wouldn't suffer from the problems 360 reviews have.
I think the best you can do is some sort of mix between a more structured portion trying to gauge where the candidate is in terms of knowledge and intelligence and a less structured portion where you try and get more of a "feel" for the candidate's personality. You have to realize that under the best of times it's not perfect. Rejecting someone can't code at all for a software position should be relatively easy. Ability to tackle bigger things can be gauged by looking into previous projects and through references. I think there's a big region though where the outcome is difficult to determine.
I think back to the very first time I was involved in a hiring decision. The guy was very smart, technically capable, engineering degree; PhD material. Seemed pleasant enough. Got hired and IMO definitely the kind of person a company like Google would hire with their process. He lost interest fairly quickly on the job. Working with him I found he had some very odd, not to say crazy, political opinions. Everything was too boring for him so he didn't really get that much done. Couldn't really work independently at all. He left the job, left the country, and I think he ended up being a cab driver. Not sure. Yet another example is someone fresh out of school with a CS masters degree who despite all the help of the team could simply not wrap his head around the project and become productive. On paper all the right credentials but first real world job and he couldn't cope for some reason. Ended up leaving. I've seen a few CS background people just not find their place. I'm sure we've all seen situations where we wonder how some person got hired and how come they're still there. Over time I think I learned to do a better job hiring/interviewing and have had a stream of pretty successful hiring decisions.
It turns out that it takes many months on the job to really know the fit. Even if the person is capable the specific job or team may not work out. Some people are very good at making it look like they're accomplishing things while they're not really. There's no way any company has a secret sauce of only hiring "great" people and even great people will do poorly under certain circumstances and conversely not so great people can be very successful under the right circumstances. Some people can grow really quickly while others can't.
Re: The Utter Uselessness of Job Interviews
#154But surely structured interviews just test a candidate's ability to improvise plausible stories? Whether they are truthful or not is a different matter..
Being able to improvise plausible stories is an important aspect of job performance, both internally and externally.
Re: The Utter Uselessness of Job Interviews
#155I have some major issues with their conclusions... and the title of the article (which is mostly nonsensical clickbait). The real conclusion should be that "unstructured interviews provide a variable that decreases the average accuracy of predicting GPAs, when combined with (one) other predictive variable(s) (only previous GPA)." This conclusion seems logical. When combined with an objective predictive measure of a p…
> There are numerous (more subjective) attributes that an unstructured interview does help gauge, from culture fit to general social skills to one's ability to handle stressful social situations. I'd hypothesize all of these are probably better measured in an unstructured (or structured) interview than in most (any) other way. To recommend the complete abandonment of unstructured interviews (which is done in the fina…
But, if you really believe that it's a huge leap to hypothesize that interviews would be a better measure of subjective social skills than metrics like GPA, I don't know what to tell you.
Re: The Utter Uselessness of Job Interviews
#156Earlier quoted context omitted.
How did you feel about your experience using structured interviews for hiring?
Truly structured interviews are better than even the most rigorous traditional interviews. They are also more expensive to design and much more painful to deliver. Some kind of interview is probably necessary for every serious tech hiring process. Organizations should be realistic about the low quality signal they'll get even from structured interviews. Take time away from interviews and feed that time to off-site wo…
-The more hoops a candidate has to jump through, the more likely they are to bail out of your recruiting funnel. This is especially bad for college/postgrad recruiting when you aren't the #1 employer in your field. Everyone wants to work for the Googles and Facebooks of the world. It's hard getting someone to spend a couple hours for your startup job.
-People cheat. We usually issue a short coding project, grade for correctness, then do a code review over Skype or face-to-face. Many candidates turn in the exact same responses. I've even seen people cheat and have a friend do the Skype session with a totally different guy flying out. Do you proctor your test in a secure center? Use an online service to lock down their machine and record? Both are pretty invasive. Switching up the questions constantly is tough and makes your signal noisier.
-Industriousness and raw intellect trump skills/knowledge most of the time. Sure there's a baseline level of skill required to train someone quickly enough, like I wouldn't hire someone who didn't know basic data structures, but work-sample tests are often biased to those with a very specific background. I don't want employees who are great at doing what I need today. I want ones who will be great at figuring out what to do years down the line.
Re: The Utter Uselessness of Job Interviews
#157How do you know that the person you'll be marrying won't cheat on you and won't leave you in hard times? If you apply the methods we use today for interviews you'll end up with a 50/50 chance at best, a coin toss. Yet why do some marriages last forever (till death do us apart) while others fail miserably or crumble even after 20 years? The search for the global optimum cannot be performed by asking a set of questions…
This is ridiculous. Mechanical approaches can be gamed, but so can gut instinct. You just have to look at the White House to see that. A lot of gut-instinct voters got hoodwinked by a skilled self-promoter. And he's a gut-instinct guy himself, so he's getting led around by whoever's got his ear.
Gut instinct, though, is worse in several ways. One is that it's not transmissible. As a company grows, how do you scale? Another is that it's not necessarily repeatable. Was that person bad, or is your gut off because you're tired, depressed, or upset? A third is that it can't be consciously improved. If your mechanical process has a flaw, your team can discuss it and come up with solutions. But if your gut judgment isn't good enough, what can you do?
I am a big fan of gut instinct as a component of a hiring process. Often, thanks to experience, we perceive things we have a hard time articulating, and it's wise to pay attention to that. But I think it's a giant mistake to treat our subconscious as some sort of mystic oracle that we must worship and never question.
Re: The Utter Uselessness of Job Interviews
#158Laszlo Bock (former SVP of People at Google) did a great job summarizing decades of research around structured interviewing in his book 'Work Rules!' For a quick reference, the two defining criteria for a structured interview are: 1.) They use one or several consistent set(s) of questions, and 2.) There are clear criteria for assessing responses That second point is really important. You can't only ask candidates the…
Most importantly most companies interviewing don't get to pick from the pool of applicants that google gets to. And even more importantly most companies don't even get to pick from the pool of applicants that a typical funded (or soon to be funded) startup will get.
While I am sure there are things that can be learned from 'Work Rules' the question is how much of that applies to the vast majority of companies in America.
Re: The Utter Uselessness of Job Interviews
#159Laszlo Bock (former SVP of People at Google) did a great job summarizing decades of research around structured interviewing in his book 'Work Rules!' For a quick reference, the two defining criteria for a structured interview are: 1.) They use one or several consistent set(s) of questions, and 2.) There are clear criteria for assessing responses That second point is really important. You can't only ask candidates the…
> Laszlo Bock (former SVP of People at Google) did a great job summarizing decades of research around structured interviewing Most importantly most companies interviewing don't get to pick from the pool of applicants that google gets to. And even more importantly most companies don't even get to pick from the pool of applicants that a typical funded (or soon to be funded) startup will get. While I am sure there are t…