3 ms·
The most common complaint with interviewing is that it's too slow, too exhausting, and doesn't test relevant skills. So interview faster and interview easier.
by muzani 6y ago
The most common complaint with interviewing is that it's too slow, too exhausting, and doesn't test relevant skills. So interview faster and interview easier.
First off, offer above average market rate. It doesn't have to be high, but it keeps everyone's minds off money and their main focus is to work rather than using you as a stepping stone. Make this rate clear. Make the interview process clear. People dread being dragged through 5 interviews only to get lowballed.
First level: filter. Ideally do it in the application form. Pick something that correlates to skill level. Lots of small questions is better than one big question because it reduces the randomness. Like I've seen things like "explain grep", "use functional programming to solve this problem", or "how do you keep up with the latest tech trends?" It should filter about 3/4 of your applicants. Your personality/attitude interviews should go here too.
I'd recommend finding one good question that takes a few hours. It can be take home or on site or whiteboard. Since you only have one, make it good. It should test that they can read instructions, ask if instructions are unclear, and code. If your goal is to fix bugs, take an old, bugged snippet of your code and watch them figure it out.
Try to do that process as fast as possible, ideally within a week or two. The more skilled someone is, the faster they'll get jobs.
If you want an even lazier system, just pay for Codility for a bit and make them do some tests. It tests quickly enough, has a broad range of questions, catches cheating, tests that they can read instructions, and there are even some bug fixing challenges.