I generally agree with that sentiment too -- having seen what a bad hire can do first-hand. However, I feel like the industry has gone too far in that direction, and may in fact be selecting for a different kind of mis-hire.
When you spend an entire interview doing college computer science quiz type questions, and none of it on process, code review, coding style, development philosophy, approach to testing, etc.... you end up selecting for people who are good test-takers, but may not be any good at writing maintainable code. Or debugging. Or troubleshooting production issues. etc... etc...
I actually agree with you. This is why I never make a hiring decision based on a single trivia question, but I do ask trivia questions that are all over the map on a topic in order to find something the candidate is good at. Honestly, if you can answer any of my trivia questions in a deep and meaningful way that demonstrates insight into the topic then I'm satisfied.
When you spend an entire interview doing college computer science quiz type questions, and none of it on process, code review, coding style, development philosophy, approach to testing, etc.... you end up selecting for people who are good test-takers, but may not be any good at writing maintainable code. Or debugging. Or troubleshooting production issues. etc... etc...