Depends on your definition of committed. If being committed to you means taking the better part of a day, weekend, etc. to exhaustively go through a "code challenge" for one job opportunity, that's one thing. For the average job seeker, if you've got ten recruiters that you're in contact with and one of those ten want you to dedicate that much time to their position and the other nine want to put you on the phone with an engineer and bring you on-site, how attractive is that one job? For someone already working more than full-time, probably not very.
I think the long and short of it is that being committed to a job has nothing to do with whether you'll tolerate a code challenge. Being "committed enough" to finishing a task to unlock the gate to actually speaking with a company's engineering team is completely orthogonal to how much you care about what you're paid to do when you have a job.
I think the long and short of it is that being committed to a job has nothing to do with whether you'll tolerate a code challenge. Being "committed enough" to finishing a task to unlock the gate to actually speaking with a company's engineering team is completely orthogonal to how much you care about what you're paid to do when you have a job.