3 ms·
A resume is a list of qualifications, and to see how a candidate frames themselves. They also set expectations for me, the interviewer for the questions I would
by 3am 12y ago
A resume is a list of qualifications, and to see how a candidate frames themselves. They also set expectations for me, the interviewer for the questions I would like to ask (they say they're a Node and Clojure expert? I will tailor my questions to verify that).
It's also a way (in addition to the cover letter) to quickly judge their communication skills.
I wouldn't hire someone without 1) a cover letter 2) a resume 3) a phone screen 4) review of their projects (ie github) 5) a team interview 6) references. Granted, I don't have to do it at scale.
It's time consuming, but not as much as a bad hire.
- ghaff 12y agoI tend to agree that a lot of the hate on resumes seems to be missing the point. Sure, if I know or know of someone, maybe a resume doesn't add a whole lot. But they provide: - A first pass at there being some match between experience/background and those needed for the position. - Some guidance for the interview process. Frankly, a lot of the details on the resume don't really matter all that much to me but, overall, it usually gives me a sense of which avenues are worth probing in more detail and which ones I can skip over fairly quickly. Sure, I could draw a lot of this out during the interview but it's easier to read over a couple of pages in advance and spend a few minutes thinking about how to spend the interview slot.