Hacker News new | past | comments | ask | show | jobs | submit login

Here's my approach, which may or may not be of interest.

All CVs are read by me -- presuming it is my budget -- and one other from the team; that team member is at liberty to discuss a CV with another if they wish, but ultimately it is their vote. Occasionally, we go back to the candidate for more info.

CVs are graded: yes, no, or maybe. Two yes-votes and the candidate gets an interview. No yes-vote and that's the end of it. All others, we discuss starting with a "defence" from the yes-voter. At the end, only those with two yes-votes get an interview.

(I always keep records of this process for later review for when we get it wrong.)

That's the sifting process.

The interview is then focussed on what we do and what the prospect believes they can bring to the party. The CV is rarely put on the table. They are at liberty to take the conversation wherever they want. They can ask whatever they want; it is made clear that there is no expectation that they know anything concrete about the business or how we work. Questioning, inquisitive minds are good.




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

Search: