A false negative in a job filter results in a phone screen with someone who can't do fizzbuzz.
A false positive results in a candidate who can e.g. write a kernel memory allocator walking from your process because you're too much of a pain to deal with.
Too many interviews, or losing the best possible candidates. I know which one I prefer --- especially because I know when I'm getting too many interviews, and can tune other things (most notably: where I post about jobs) to adjust that. I can't know who I'm losing as a result of my recruiting process being cumbersome.
Perhaps the reverse way to look at the situation is that job adverts are so uninformative about the place where one might work, that it is the employers who should present a video about why one might want to work for them. It shouldn't be one of those glitzy HR ones, but rather one made with a cameraphone introducing the people the prospect will be working with, and some idea of what type of problem is being solved.
The other thing that jumps out at me is that instead of a cute challenge, it's probably more useful to provide a bug in 50 lines of code that you expect to "jump out" effortlessly for the qualified candidates, while less qualified might struggle a little.
A false positive results in a candidate who can e.g. write a kernel memory allocator walking from your process because you're too much of a pain to deal with.
Too many interviews, or losing the best possible candidates. I know which one I prefer --- especially because I know when I'm getting too many interviews, and can tune other things (most notably: where I post about jobs) to adjust that. I can't know who I'm losing as a result of my recruiting process being cumbersome.