Furthermore, I have no interest in reducing the risk for the employer: I expect them to do that. I reduce my own risks. If I'm the employer, then of course my perspective will shift 180deg.
FFS, it's a job, not a hobby!
How about a one week stipend. You're view point is too company-centric, I MUCH prefer to work for people-centered companies. Either way you need something a little more symmetric if you don't want to become standard laughing stock among developers. (Or maybe you and your-co are so badass you can't do wrong and developers intrinsically trust you so it doesn't matter.)
Many information systems can be implemented in a week. You could set up email, an e-commerce site, a CRM, SCM, or even substantial portions, if not an entire ERP system depending on the size of the company.
A week is a long time if you know what you are doing.
By not letting someone acclimate to your tech environment, your potentially shoving them off on the wrong foot (not to mention stressing them the fuck out,,,which WILL kill their productivity). A mistake that could cost you months of 50% productivity because you didn't (as a company) empower your developers to do their best work.
When I see managers pulling some "whip them harder" management styles, I can't help but be left with the want to remind them about the french revolution. Pointy-haired bosses will soon figure these things when "their" work force becomes a bit too empowered.
Well, the candidate would be giving away a week of his time, which can be a bit problematic. How would you arrange this if the candiate was already employed?
He'd take a week of unpaid vacation from his current workplace, and give it away on a chance he might want to switch jobs and be accepted? Besides, 1/4 of your monthly salary is definitely a noticeable loss.
What if this was a common practise? "Oh well, this didn't work out. I'll take another week of unpaid vacation to try out for that other company then"..
A lot of people think of work as "sitting in a cube."
Working for some place means exchanging your time for money. Whether that time is spent coding with a burning passion, moving a company in a desired direction, or looking at lolcats is another matter.
A lot of people think of work as "sitting in a cube."
The question is, "How do we determine if the candidate's definition of work matches the employer's definition of work?"
Maybe what you think you are doing when you are working is actually causing more problems and moving the company backwards because they are going to have to undo all the crappy code you wrote. I'm not meaning to attack you, I'm just trying to illustrate a point. Know what I mean?
Maybe such an engagement could work out where, "If we hire you, we pay you for the week. If we fire you, we keep the money and you are out."
This reduces the risk for the employer while also giving the employee a chance to examine the company and be paid if the work is satisfactory.