4 ms·
The key thing is that you filter out anyone you aren't willing to risk paying $800 or more to do the testing before asking them to commit to the extra time. Th
by daotoad 7y ago
The key thing is that you filter out anyone you aren't willing to risk paying $800 or more to do the testing before asking them to commit to the extra time.
This is pretty onerous, but it should be pretty damn good at rejecting bad candidates.
I do wonder how many good or great candidates you lose with this method, though.
- rsyring 7y agoI've wondered that myself. I don't know of a good way to evaluate that. I've thought about looking at bounce rate on the job description page or even showing a popup on bounce detection asking for feedback on the job description and application process, but haven't executed on either yet because I'm not convinced the effort would be worth it. If someone is going to bounce, how likely are they to take the time to tell us why. It's also more than just the $800 we pay out. I personally proctor and grade the tests. That takes me 4-6 hours. Given my billing rate and roll in the company, that's arguably a greater cost to us than what we pay out to the candidate.
- sciurus 7y agoThey'e also likely filtering out anyone who currently has a job, or a family, or even is interviewing at other companies. The process described here and in the posting at https://www.level12.io/careers/full-stack-web-app-developer-senior/ https://www.level12.io/careers/full-stack-web-app-developer-... is on the order of 30 to 40 hours. That's a massive time commitment.