(1) Sort resumes in order from least amount of pages (on the top) to the most amount of pages (on the bottom). The resumes with the lesser amount of pages get priority (I've seen 12 pagers... the quals on it were from a complete bozo). I'll throw out anything over 3-4 pages.
(2) Throw out resumes that list every programming language since 1982 (this halves the resume stack) or a list of languages the person is "familiar with" (when will head hunters stop telling their applicants to list this crap?)
(3) I could care less about GPA as long as its over 3.0; I look for diversity at this point. Was this person an English major or a CS major? Does this person code outside of work? Are they experimenting with other languages/technologies? Does this person travel quite a bit?
(4) Now its time to more carefully read the resume. I'll actually look at the experiences to make sure they're being honest and not making stupid claims like, "Save over $10mm in costs from writing code X".
(5) Next up is the phone interview where I ask simple questions to make sure the applicant can communicate clearly, knows what regex is (this questions throws a lot of applicants to the way-side), and verify a few claims on their resume. I had one person claim they knew about DOA web-services and another guy who had "HTTP" listed on his resume and didn't even know what an HTTP verb was. Another more clever guy was actually Googling shit as I was asking him a question (I can hear your keyboard!).
(1) Sort resumes in order from least amount of pages (on the top) to the most amount of pages (on the bottom). The resumes with the lesser amount of pages get priority (I've seen 12 pagers... the quals on it were from a complete bozo). I'll throw out anything over 3-4 pages.
(2) Throw out resumes that list every programming language since 1982 (this halves the resume stack) or a list of languages the person is "familiar with" (when will head hunters stop telling their applicants to list this crap?)
(3) I could care less about GPA as long as its over 3.0; I look for diversity at this point. Was this person an English major or a CS major? Does this person code outside of work? Are they experimenting with other languages/technologies? Does this person travel quite a bit?
(4) Now its time to more carefully read the resume. I'll actually look at the experiences to make sure they're being honest and not making stupid claims like, "Save over $10mm in costs from writing code X".
(5) Next up is the phone interview where I ask simple questions to make sure the applicant can communicate clearly, knows what regex is (this questions throws a lot of applicants to the way-side), and verify a few claims on their resume. I had one person claim they knew about DOA web-services and another guy who had "HTTP" listed on his resume and didn't even know what an HTTP verb was. Another more clever guy was actually Googling shit as I was asking him a question (I can hear your keyboard!).