On top of the other comments here about how capitalism is bad and coding interviews are generally bad, I wonder what your parameters are. Does the job description actually include your stack? Are you interviewing people who casually list JavaScript or python but don't have relevant coding experience? How much time is given and what is the extent of the question?

If you're not paying people for their time, and you're asking them to do an at home assignment that has potentially no relevance to their expertise or the job they will be doing, all within a short timeframe what do you expect?

Unpopular take, but I think a short practical question, or maybe some verbal pseudocode stuff is fine, but I've had to run interviews as well so I get the struggle of finding a good fit.

As an aside, I've known some good code monkeys that can't design or explain anything, but given a direction they will hammer out a mvp in record time. Sometimes you have to pick the right tool for the job. Good coders aren't always good designers and vice versa. That's my hot take for the day.