Re:Cracking the Coding Interview Tutorial
by danieltillett on Tuesday September 27, 2016 @04:52PM
(#12593091)
Ask how many people have been fired. I like to think the people I have are all very good because I fire all the bad ones. Much better to weed out because of on the job performance than select on the basis of some poor proxy for on the job performance.
Several citations in there, but it seems like a common sense thing to me. Why interview at all if you're so willing to take on the risk of a bad hire? Just take them out for lunch and ask them how they like coding.
It's also bad for recruiting purposes. If I have an easy interview I'll be reasonably assured that my future coworkers went through that same process -- what metric do I have to assume they're going to be good engineers to work with?