[jcdavison]

I fell like it is common, not sure I would say it is typical. I avoid it at all costs. Usually, if I complete the project the and the host company doesn't like it, I don't get any feedback on the code and my time gets mostly wasted. If companies would give some degree of feedback on the code I'd be more into it. "No" isn't the kind of feedback that I value.

I try to stick closer to companies that have a balanced interview process and a smaller live coding challenge, think 20-45 min can really suss out a person's technical level anyways.

Just my $.02

[kasey_junk]

I've done a lot of work in this area (including quais-rigorous experimentation with hiring pipeline processes) and I have found that live coding challenges are anti-correlated with good hires. I was surprised by this as I quite like them.

What people like us, who do like them, don't realize is how much stress it puts on people who don't like them. This stress does not usually have any real world correlation with the job you are hiring for, so it severely biases against candidates who would be great but fail due to stress. It also biases towards people who can come up with glib fast solutions, which also frequently isn't correlated with being able to solve long complex problems.