[meejah]

If someone demands hours of free labour for "code exercises" or whatever, the absolute bare minimum is that you put some portion of that back into meaningful code review.

So you should probably be spending _more_ time on the feedback for rejected candidates. Be specific, tie it back to your evaluation criteria that you wrote down before asking for the exercises to be completed.

[bcantrill]

We at Oxide don't ask for code exercises, but perhaps you're making a more general comment?

[steveklabnik]

I read the parent as metaphorical; if we did code samples, code review would be expected, so since we do not, an equivalent review would be nice.

I get the sentiment but it’s very tricky; most places do a screen and then an interview and so review takes place during said interview, we are heavier allocated on “the screen” in a sense. It would be even more work in our circumstances to do so, since we have more people in that stage of the process than others.

[meejah]

Yes, I was making a more general comment (I think it does still apply whether there's actual code-exercises or not though).

If it's "too much work" for you, might be time to re-examine how much work you're asking for.

I also think these sorts of things select for candidates that have lots of time for "applying to places" (which will naturally select against people already in jobs, or who already value work/life balance).

Your process doesn't look as onerous as some I've seen for sure -- but perhaps you _should_ add a "screen" portion and thereby not ask for the "long form" work from candidates you'd reject anyway (also buying more time for meaningful feedback to those you do ask the work of).