Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

http://www.stackoverflowcareers.com/blog/2014/05/20/getting-...

Try segmenting potential hires into different categories and using different strategies for each group. You should also clearly communicate the process, so they don't get the wrong idea.

>Additionally, the people who tend to drop off because of this extra effort tend to be senior applicants

Is this before or after the phone screen? If they think the work-hire test is going to be in addition to a phone screen and an on-site whiteboard session, they'll drop. If they're senior devs, you should be able to tell from their resumes. Do a phone screen, and if they pass, explain that they can either do a work-hire test or a whiteboarding session. Explain that the work-hire test should be doable in 4 hours, so they don't envision a week long project. Also explain that it's a substitute for the whiteboard portion of the on-site. People who tend to hate whiteboard coding will choose the work-hire test and vice versa.

If you're trying to find diamonds in the rough among junior talent, sending out a first-pass work-hire test might work. You'd still get better results if you explained that it was short and a substitute for the onsite whiteboard session.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: