2 ms·
There is unfortunately a fairly high probability that a given interview candidate for a coding job can't actually code (at all, not just poorly or slowly). So h
by dboreham 10y ago
There is unfortunately a fairly high probability that a given interview candidate for a coding job can't actually code (at all, not just poorly or slowly). So hiring people try to come up with processes and tests to avoid being the idiot who hired someone who couldn't code.
Obviously requesting that the candidate actually produce new code is a fairly good way to ensure success in this goal.
otoh it is likely to irritate and inconvenience the candidate and probably remove some proportion of the better applications from the pool.
I prefer to ask candidates to talk about a project they found interesting or challenging or noteworthy, and go from there asking questions, specifically what was their individual contribution and so on.
Personal references are also useful.
Ultimately I suppose though if I had no available candidates where I could get a first-hand trusted reference, nor any recent project to discuss, about the only option I'd have left would be to ask them to write code. I don't recall it ever coming to that though.
Faced with this situation you could try suggesting that you prefer not to spend significant time working on an apprentice-piece project and would the interviewer accept your hobby project instead or some recent work project if disclosure restrictions allow you to talk about it and show code.