Earlier quoted context omitted.
>I suspect the "tough" interview plays well into a company's PR. from: "The trick Max Levchin used to hire the best engineers at PayPal" Levchin realized the best engineers wanted to be challenged both in their jobs and in the interview process. “We cultivated a very public culture of being incredibly hard to get in. Even though it was actually very hard to get good people to even interview, we made a point of broadc…
There are approximately 7 people on earth with an IQ of 190 or higher, so I'm calling bullshit on that requirement.
In Head-Hunting, Big Data May Not Be Such a Big Deal
111–120 of 285 posts
Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#112Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#113Earlier quoted context omitted.
30k? Data. Not Big Data And "Small Big Data" is probably data as well.
He's not talking about 30k rows, he's talking about 30k people. It could easily be big data if you monitor & document their every working moment, but they probably aren't doing that so you're probably right.
It really doesn't look like something big.
Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#114Earlier quoted context omitted.
> "That's a challenge. I'm going to go interview there just to prove to these suckers that I'm better." Well that, or: http://en.wikipedia.org/wiki/Dunning–Kruger_effect
Dunning Kruger does not mean that unskilled people think they do better than skilled people. On average, the more competent people at any skill will rate their abilities higher than the less competent people. See this graph[0] from the original study[1] for a better explanation. [0]: https://fbcdn-sphotos-b-a.akamaihd.net/hphotos-ak-ash4/p480x... [1]: http://ttsg.org/pdfs/Dunning-Kruger%20Effect.pdf
Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#115Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#116There 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…
> A man pushed his car to a hotel and lost his fortune. What happened? horrible question, it took me a few seconds to figure out they are talking about the game Monopoly.
Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#117Earlier 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.
I quote my friend who works in "Big Data": "sometimes I think Big Data is just Excel on 128GB of RAM"
Difficulty in "big data" should be about its horizontal breadth (covering many aspects of a system) rather than its vertical depth (covering one aspect of a system in great resolution).
Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#118There 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…
> A man pushed his car to a hotel and lost his fortune. What happened? horrible question, it took me a few seconds to figure out they are talking about the game Monopoly.
Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#119I had fun and wouldn't mind it again, it didn't feel like a bunch of stupid random brain teasers like I've experienced before (how many t-shirts would it take to make sea worthy sail? why are manholes round?) etc.
Re: In Head-Hunting, Big Data May Not Be Such a Big Deal
#120Contract to hire is one way, another is what they have done previously as a good predictor. It is a risk for sure but that really is the only true way in the end.
Plenty can be gained from just letting the interviewee talk and maybe looking at some of their code they have done previously while they talk about it. Whiteboard coding should not apply as it is completely out of element for many coders.
The type of person they are can't really be detected correctly until they are in the team and delivering because everyone is selling themselves on an interview.