4 ms·
Interviewing is actually very easy. Every job I post gets 100s of applicants - so finding them is not a problem. I've got a piece of software that lets me A/B
by edoceo 11y ago
Interviewing is actually very easy. Every job I post gets 100s of applicants - so finding them is not a problem. I've got a piece of software that lets me A/B these candidates resumes & profiles side-by-side so I rank-sort them quickly. And all "interviews" are small-boxed projects that I ACTUALLY PAY FOR THE WORK.
See, most interviews are along the lines of:
Q: Are you smart and good looking?
A: Yes!
This is why I don't really intervew all. When I take the "best" ranked applicants I give them actual work; small slices from our actual code base. I provide them a complete, functional dev environment with one restrciton: cannot commit to git. I can see their work directly, I work with them directly and get real-time data on what it's like to work with them, how they handle a project, how they communicate blockages, how they figure out our existing systems.
In four to eight hours of work I know who is the right fit for our team. My cost to find and filter is very very low and rather than waste 2-4 hours per interview for 10 candidates I pay for 16-24 hours of work for 2 or 3 candidates. The hard costs are the same, it consumes less of my (or my engineers) time and the candidate fit is very good.
- madcaptenor 11y agoSee, most interviews are along the lines of: Q: Are you smart and good looking? A: Yes! In my current company we hire a lot of developers through contracting companies. These people often have very difficult-to-read resumes - mostly because they are trying to get through filters that work based on searching for keywords, but they're rarely well-written documents even within this constraint. Fine, we're not looking to hire a writer. But a lot of these have "Communication Skills: 9/10" on them. Whether this is added by the candidate or the contracting company, I don't know.