On the other hand, I agree wholeheartedly with people who reject "homework assignments" layered on top of a standard interview process.
The onus is on people who want to take advantage of work samples to:
* Ensure that the time they're asking of candidates is offset by lowered time demands elsewhere
* Ensure that they're using the work samples objectively, so that people aren't asked to do coding work as part of a crap-shoot application process.
The process we used at Matasano and NCC was less demanding than typical job interview processes. The challenges were simple and self-contained, and when they were completed we could tell you with a decent degree of confidence whether you were likely to be offered a job at your (shortened) on-site interview.
What do you end up with if you filter out companies that ask for work samples?
The major pain point in interviewing (at least for me) is the massive time sink for a very small chance of success. I'm spending a few hours on the application, then a few more doing phone screens, then a weekend doing a work sample, then I blow a VACATION day (which has monetary value and of which I have only 10 per year), and at the end of it all who knows what my odds even are? Multiply that by, lets say 10 companies per year, and: I've invested 31 days of my life, have no vacation left, and I still may end up with nothing.