Many don't. You can always just refuse and move on. I've wasted a lot of weeks on these things. They are a major risk for the applicant because the slow the jo

Many don't. You can always just refuse and move on. I've wasted a lot of weeks on these things. They are a major risk for the applicant because the slow the job search down considerably. The large time investment makes the application process prohibitive for people already working full-time, which is bad for the hiring team because employed people looking for a change are often the most competent candidates. I would never agree to a coding challenge anymore without some assurance I'm on the short list of candidates. i.e. Ask to schedule a code review meeting with the hiring team, or insist on a traditional interview before you do the challenge. If that's a problem for them, then you can be sure that they aren't going to hire you no matter what you submit.