2 ms·
> I think we over focus on these scary edge cases where some trickster is trying to con their way into the job. The worst case is you just fire them when they a
by gumby 7y ago
> I think we over focus on these scary edge cases where some trickster is trying to con their way into the job. The worst case is you just fire them when they are unable to do the work, and that's on them.
The problem is once you offer them a job you stop searching for a candidate. Then you get a bad hire and even if it's quick you won't really know for a while, so then you're really behind.
It's bad enough when you hire someone who really wasn't qualified but didn't do anything bad. Now you have to get rid of someone who probably left a previous position and, like above, you have to go get someone to do the job you were hiring for in the first place. Worst of all possible worlds.
Perhaps the calculus is different in a big company, but for a startup your approach sounds pretty bad.
- staticassertion 7y agoFor what it's worth, I'm not convinced that my approach will actually let more "bad" people through. My personal opinion is that you will improve both your rate of good candidate hiring and lower your rate of good candidate rejection. I believe that the existing system intends to optimize heavily for "reject bad candidates" and actually fails at that too. Give candidates a take home, then review it with them. I have a lot of reasons for believing this approach would be far superior to the "sit in a room and get interrogated for 7 hours" approach.
- vonmoltke 7y ago> hire someone who really wasn't qualified but didn't do anything bad This sounds like a contradiction to me. How are you defining "unqualified" and "bad" here?