Live data from Hacker News

In Head-Hunting, Big Data May Not Be Such a Big Deal

nytimes.com

91–100 of 285 posts

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#91
post #25
post #3

The original article - http://mobile.nytimes.com/2013/06/20/business/in-head-huntin... Distraction free reading and without all the annoying cruft of Quartz. Fascinating use of "Big Data" to cut through the bullshit. Wonder if it will change anything. I suspect the "tough" interview plays well into a company's PR.

Is Google's HR data set really "Big Data" or just "data?" Seems like it would fit into a normal database. Or maybe even an unwieldy Excel spreadsheet.

They've reported receiving 1million applications per year. If even a fraction of those get interviewed (with 1-5 interviews per candidate) that's a good chunk of data. Correlate that with regular performance reviews of 30k employees... I'd say that's a small Big Data problem.

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#92
Why so serious? Isn't hiring about maxing out the potential of a company?

Anyone can help maximing it out. I know for myself that having 'clue' reduces self-esteem. Which can be balanced by having the right co-workers. End result: Maxing out the potential.

A(Technical intelligence) + B(Social Intelligence) = (Innovative potential)

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#93
post #72

Earlier quoted context omitted.

Not to go all senselessly pedantic, but doesn't Excel have a limit of like 55,000 rows?

If you're being pedantic, it's 1,048,576 rows from Excel 2007, 65,536 rows before that.

2^20 rows! :)

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#94
post #91
post #25

Earlier quoted context omitted.

Is Google's HR data set really "Big Data" or just "data?" Seems like it would fit into a normal database. Or maybe even an unwieldy Excel spreadsheet.

They've reported receiving 1million applications per year. If even a fraction of those get interviewed (with 1-5 interviews per candidate) that's a good chunk of data. Correlate that with regular performance reviews of 30k employees... I'd say that's a small Big Data problem.

30k? Data. Not Big Data

And "Small Big Data" is probably data as well.

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#95
post #66
post #52

Earlier quoted context omitted.

Data-backed estimation is completely different from random guesses you will make during an interview. Not only that, even if your guesses are decent, multiplying them can drive you orders of magnitude in the wrong direction.

The underlying data might be different but the process is the same, you need to figure out what are the contributing factors, how they relate and establish an upper and lower bounds for the values you're assuming. Once you have data you can make corrections to those bounds, but other than that the process is the same. It's a skill that a lot of first time startup founders lack. They have no-idea how to estimate the m…

Process is not the same, in one case you have real data, in the other one you pull the data out of your arse.

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#96

> Years ago, we did a study to determine whether anyone at Google is particularly good at hiring. We looked at tens of thousands of interviews, and everyone who had done the interviews and what they scored the candidate, and how that person ultimately performed in their job. We found zero relationship. Can we see the study? Also note that performance on the job is a noisy measurement, because people who get to work o…

> I wouldn't be surprised if interview scores were a better measurement of "true" skills.

Possibly, but in a sense "true" skills don't really matter. What matters to Google, ultimately, is Google's opinion of the worker. It's almost certainly skewed / flawed / distorted in some way from the individual's true skills, and that's unfortunate but mostly a fact of life.

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#98
post #3

The original article - http://mobile.nytimes.com/2013/06/20/business/in-head-huntin... Distraction free reading and without all the annoying cruft of Quartz. Fascinating use of "Big Data" to cut through the bullshit. Wonder if it will change anything. I suspect the "tough" interview plays well into a company's PR.

Actually here is the real original article:

http://www.nytimes.com/2007/01/03/technology/03google.html?e...

Which there have already been a few HN discussions about:

https://www.google.com/search?client=safari&hl=en&ei=ZfzCUYa...

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#99
A problem I see with many of these sorts of questions is that they often require the candidate to have some supposedly common knowledge which is not required for the job itself. Cryptic word games surely are much more difficult for a non-native speaker of the language in use. Questions related to facts about cities probably require local geographic knowledge. Surely the evacuation plan for SF must consider the capacity of various bridges? Someone who has lived in northern CA for most of his life would have a much easier time thinking through the logistics of moving people off a peninsula. And, of course, there's the Monopoly question (which I had to Google).

I like estimation questions in general for many of the reasons other commenters have cited. However, I wish those using them would consider the knowledge implicitly required of a candidate.

Re: In Head-Hunting, Big Data May Not Be Such a Big Deal

#100
There are questions that are actually fun and I can sort of see them starting a conversation with the right kind of interviewer that tells both parties a lot about who they're dealing with. From the article:

  > How much should you charge to wash all the windows in Seattle?
Basic economics estimating - probably not that useful and a bit dull, but hey why not. At least the problem has several angles to it that might be fun to explore.

  > Design an evacuation plan for San Francisco
That's a nice one. Kind of open-ended, a lot of things to consider, a lot of ideas to be had.

  > How many times a day does a clock’s hands overlap?
Why? What happens to the interview after you counted them (possibly on a whiteboard)? It's a dead end and the question is dull.

  > A man pushed his car to a hotel and lost his fortune. What happened?
Now this has the potential to be great or absolutely horrible, depending on the intent behind the question and the nature of the interviewer. If it's taken as a "fill in the blanks" kind of challenge it would be a fun way to explore the candidate's imagination. But I'm guessing it's not. It's probably one of those "clever" questions that have only one "right" answer that makes no real sense except creating a few moments of uncomfortable silence.

  > You are shrunk to the height of a nickel and your mass is proportionally reduced so 
  > as to maintain your original density. You are then thrown into an empty glass blender. 
  > The blades will
Again, this could be a fun physics and chemistry question and I see a couple of possible solutions that might or might not work out - might be fun exploring them. But again, it sounds more like a trick question with one standardized answer. Bad.

The problem with trick questions and standardized answers is that the nature of the question makes the candidate uneasy and even if they eventually figure it out, nobody will have learned anything during the process. It's more like a hazing, not a hiring interview.

Post reply on HN