> but bias against other desirable candidate qualities such as experience Won't you see, in the code submission, at least some evidence of experience? The way

> but bias against other desirable candidate qualities such as experience Won't you see, in the code submission, at least some evidence of experience? The way the candidate organises their code; the overall style; the third-party libraries they choose to use (or not to use); the tests they write (or don't write) — doesn't it all, combined, speak of experience or of lack thereof? There are still other stages of the interview, where you can assess candidate's experience more directly, by asking about what they worked on. I agree that it's useful to know when a task that should have taken x long takes 5x or 10x; but it may be because the candidate set a higher bar for themselves.