> Otherwise it is half a day of unpaid labor.
The same true for an interview
> Do you have empirical evidence that it can be completed in the given time slot?
As a candidate once you see the specification and you think it's not worth it you can easily can say no to it.
> Is there a guarantee that an actual person will review the submitted code and provide feedback? AFAIK, most companies won't give candidates any feedback / validation of submitted work
That is why I only willing to do these kind of challenges once I had the first round of technical interview and I know I would like to work there
>> The same true for an interview
Who does half day interviews? In my 3 years as a professional software dev, I've perhaps spent a cumulative 2 hours in interviews with a company. I know that some companies have extensive interviews. But they aren't as laborious as intensely grinding on a mentally challenging project in an industry such as software.
b) Do you make it clear what you consider as "good design"? OOP/Imperative or Functional coding style? Even in OOP, is it sufficient if the candidate just does SOLID or do they have to implement GoF patterns? This is very subjective and never made clear in these tests.
c) Is there a guarantee that an actual person will review the submitted code and provide feedback? AFAIK, most companies won't give candidates any feedback / validation of submitted work