As someone trying to hire, I find myself going through resumes for the firs ttime... And honestly, my primary metric is if the word "rails" appears anywhere (I

As someone trying to hire, I find myself going through resumes for the firs ttime... And honestly, my primary metric is if the word "rails" appears anywhere (It's a ruby on rails job). I might even let that go if I saw a cover letter explaining why they liked rails (but maybe don't have professional experience in it). Honestly this is a pretty low bar. And the way I've been doing it, the phone screen that follows is pretty softball. But after that, I give out the coding exercise... If you complete it, you get an in person interview for the most part. But all the rest of it - looking at resumes, the phone screen - sort of seems like a waist of time. I don't care how big a game you can talk, if you can't do the coding exercise (which, btw, is the most common outcome - they beg a couple extensions and then give up), then... oh well.