And, that's not very different from someone spending more than the expected 40 hours at work. One can't do much about that if that person genuinely loves coding all day and does not mind working 60 hours a week.
Finally, in the follow-up call, I do ask the candidate how long the assignment took and how she spent her time across multiple tasks. Obviously if someone spent 10x the expected time, then that's another data-point to the final decision.
As to the time commitment, I would say finding the time to do these coding challenges is no harder than finding the time to come in and interview. And not every company even does a take-home coding challenge. The last 2 companies I've worked at did not.
My point is not that there's no signal there. My point is that the incentives encourage candidates to spend arbitrarily large amounts of time on these challenges and to not mention the fact, which distorts the signal.
> Send the candidate a take-at-home coding assignment. This should ideally take only 2-3 hours and should be directly related to the kind of work she will be doing at work.
I used to be a fan of this, but I'm not so sure anymore. The reason is that if you give me a test that "should" take 2-3 hours to complete, I know I'm going to be competing with people who are spending large multiples of that amount of time on it.
Unfortunately, I don't have a solution to offer for this problem.
Edit: compete -> complete. Freudian slip?