Re:The anatomy of the perfect technical interview from a for...
by vladimirralev on Thursday August 15, 2013 @02:59PM
(#6219870)
That sounds accurate, but
1. You need large samples of hires because you must know what features actually correspond with good performance
2. You need to have a near perfect understanding of statistics
Once Google and friends collected a large enough sample they concluded their puzzles are not a good indicator. Similarly, people tend to have bias towards certain skills without any statistical evidence that they are correlated with performance. And statistics is all about removing the bias, which has proven time and time again is very hard. Otherwise you would be just gambling on instinct, which at best is just a sanity check.
Re:The anatomy of the perfect technical interview from a for...
by dylangs1030 on Thursday August 15, 2013 @03:17PM
(#6219961)
I agree strongly. But part of the problem with this solution is that you might be caught with a stream of merely adequate people you won't hire because you're afraid of false positives. I also think it's sometimes okay to hire merely adequate people, if you know ahead of time you can quarantine their usefulness to one area they seem stellar at.
My personal threshold attempts to minimize false positives even to the extent that I will pass on people that would probably have done a good job. I tune it this way because I think that bad hires are one of the worst things that can happen to a team. But, each individual has to calibrate this for themselves.
I'm not looking to solve the problem, I'm looking to make the best possible decision based on the information I have available.