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

> a fairly traditional hiring process that's the same for hiring a programmer or a machinist: Resume screen, phone screen, on-site, offer.

Some years ago, I was looking for a job, and an employed friend of mine sent me a problem and said "this is our hiring challenge. Try it out".

I completed it, and she asked for my resume, and turned in both to whoever the relevant person was at her company.

She then reported back to me "he said this is the best response he's ever seen to the challenge, but we're looking for someone with more experience". I was not contacted by anyone else.

And years later, when I ribbed her about this, she told me "he regretted that, later".

I note that by putting the resumé screen first, you're committing yourself to the idea that whatever you're looking for in the resumé screen is more important than anything you might learn in the phone screen or the on-site. Do you believe that? Are the phases looking for the same things? If not, is that intentional?



I did resume screening for about fifteen years for different small companies, it’s first because if I phone screened everyone who sent an letter or email expressing interest there would be no time for anything else and I would be wasting a lot of candidate time when I could look a resume and know if someone was ballpark decent and just let both of us off the hook early with rejection (a lot of people swing for the fences with applying for jobs) if this was easily ascertainable from the resume. I am assuming candidates are making the best argument for themselves in their resume.


My last company put the automated HackerRank test first, because if we filtered by phone call or resume first, there would be no time.

HackerRank was so great at saving everyone's time. One third of candidates never opened the link. Open third opened but didn't do any exercise.


Indeed, I wasn't touting it as a best practice, but as an example of a fairly mainstream traditional practice.




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

Search: