[hvidgaard]

> I don't think false negatives are good. How many positions go unfilled for months and years? A lot. At a larger company, it won't take long before they remove the position entirely. They might not be wrong to do so either. Eventually your bus factor goes to zero, and whole teams go away.

I'd rather that happen, than hire unqualified people. Hire and then fire someone is damn expensive - months of salary and a lot of hours wasted. If you don't get them out of the door fast enough, the damage they can do with incompetency is even greater.

[safety-third]

I have personally hired false positives. Like you say, they are expensive. I have never once hired someone who was literally incapable of doing the job. It's never because of work directly. A person who was incredibly professional in the interview turned into a massive asshole at the office. One fought good coding practices because he thought it was over-engineering. Another spent all day playing online poker on their phone. One spent their entire time at the office making Forth interpreters.

Doing 7 hours of whiteboarding interviews for every candidate won't flush out any of these. Not a single one. If you can tell me the magic 8 ball I need to shake to fix this, I am wide open to suggestions.

[celticmusic]

> One fought good coding practices because he thought it was over-engineering.

You would have considered me a false positive then, despite the success of my career.

[perl4ever]

Nobody is perfect for every job.

A phone app is one thing, ERP or accounting is another, avionics is another.

[celticmusic]

ahahahahahahahahahaha, the arrogance in this comment cracks me up. You have no idea the software I write, don't make assumptions.

[perl4ever]

The software you write makes you perfect for every job...and you are amused by my arrogance?