4 ms·
I've been asked to do coding interviews for freelance gigs a couple of times recently. This does not make sense to me. The whole point of freelancing is that ei
by jillesvangurp 7y ago
I've been asked to do coding interviews for freelance gigs a couple of times recently. This does not make sense to me. The whole point of freelancing is that either of us can terminate the contract on short notice if for whatever reason we don't like each other. Usually, if it comes up, I just recommend the company that if they have another qualified candidate (i.e. better qualified than me), they should do their best to hire them. It's a good way to cut the bullshit and get it in people's heads that they need to work hard to get me if they want me to commit to their project. If based on my profile they are not super eager to talk to me, I'm wasting my time because either they need somebody with a different profile or they are B's trying to hire C's. In both cases, that's a good reason for me to not engage any further.
I've been in the interviewer role as well and I tend to not rely on coding exercises, whiteboard BS, etc. I usually just wing it knowing full well that interviews are in any case a bit of a crap shoot in terms of objective results. My goals when interviewing are very simple: 1) verify that what is in the person's CV holds up and try to get them to talk about what they did, how they did it, etc. 2) inject a few technical questions to see if they can come up with some good answers or whether they start bullshitting. 3) Figure out what they don't know and how they would deal with having to learn something new. 4) Figure out how well their experience aligns with my team's needs. I'm OK with a less than perfect match if a person has the potential to learn new stuff. Especially with junior roles, that's the most important thing because they probably don't know much yet.
But really, I tend to go with my first impressions here and have learned the hard way that ignoring those leads to bad hires. Yes, there's a risk I'm wrong about not hiring somebody. But if it feels wrong, it's not going to happen. Usually, I know within a few minutes what it's going to be; the rest of the interview is then either about making sure the candidate is sold on the job or giving me enough material to defend the choice not to hire to my managers, HR, etc. Coding exercises don't really factor into this. If I have any doubts whatsoever about a person's ability to actually produce code, I'm not going to hire them.
Unfortunately hiring is hard. There are a lot of mediocre candidates out there with a lot of mediocre recruiters representing them. I vastly prefer warm introductions through trusted friends and colleagues. So, as an interviewer, I deal with screening a lot of obviously not great candidates. The flip side is that when somebody good comes along, you need to be able to act fast because they'll have other options. Coding exercises are an obstacle for both sides.