31 ms·
Been there, done that. Spent considerably more than 50 hours on it too. Not because I broke the rules but because they made it a point to specifically emphasi
by stakhanov 8y ago
Been there, done that. Spent considerably more than 50 hours on it too. Not because I broke the rules but because they made it a point to specifically emphasize that I should take my time rather than submit something half-assed. -- I will not be so naive in the future.
Now I specifically ask how many other candidates for the same spot are in the stage of the take-home exercise. If it's more than half a dozen, forget it.
It depends on a number of further factors: Anything up to 48 hours I might do for free. For anything more, I would push pretty hard on them paying for my time to make sure they have skin in the game. A number of reputable companies do this now.
- xvector 8y ago> Anything up to 48 hours I might do for free. I wouldn't even suggest this. Anything over 1 hour is biting into my own valuable time. Your take-home challenge should not take longer than a coding challenge I'd do for another company (and those are around 30 minutes). If they don't care to spend phone or on-site time interviewing me after this, then they were never worth applying to in the first place.
- stakhanov 8y agoI should clarify: By 48 hours I mean that my comfort zone would be a 48 hour timespan from getting the assignment to handing it in, which might be 10hrs spent actually working on it. Some companies do impose a limit like that, to reign in people who would break the rules and put massive numbers of hours in to get an edge over people unwilling to do that. ...this limit is something I agree with as good practice. Also, as a bit of context: I tend to work remotely. When interviewing for a remote job, I don't think I would prefer it if they were to fly me in. That would most definitely be even more time wasted, plus the time I spend on a plane is doing nobody any good, neither them nor me.