Re:How to rip apart a programmers CV
by rpedela on Sunday July 06, 2014 @12:00PM
(#7994814)
In this particular case, I received ~20 resumes for 1 job and 80% were not Ruby-only resumes. So yes the Ruby-only screened them out. However I would have gone back and contacted them if none of the other 80% of candidates worked out.
[ Parent
| on HN ]
You will get better results if you build a process that doesn't screen people out because of their resumes. That doesn't mean you don't screen candidates, and it doesn't mean that you don't have a funnel that knocks out a big chunk of them before you get on the phone.
It just means: don't select people for their getting-a-new-job skills. Those skills aren't relevant to software development work.
Based on your other comment, does this mean you use a commercial or custom general mental ability test in the funnel before screening and interviews?
It would be helpful to know more about what you do versus what you don't.
Re:How to rip apart a programmers CV
by saturdayplace on Wednesday July 09, 2014 @01:14PM
(#8010833)
You can read about tptacek's company's process here: http://matasano.com/careers/. It really does seem like a good way to learn whether a candidate will be able to perform the job.