2 ms·
personally, i can see why people want this, but as an engineer i'd only do it if i was either pretty desperate (like, not having a job), or if there was a chanc
by andrewcooke 13y ago
personally, i can see why people want this, but as an engineer i'd only do it if i was either pretty desperate (like, not having a job), or if there was a chance to learn something pretty cool. if the trial week were as interesting as, say, the matasano crypto challenge, then i'd do it even if i wasn't looking for a job. but i guess making something like that is difficult.
now i suspect most companies would like candidates who think that working there is "pretty cool" in itself. but let's be honest - jobs aren't like that. they have good bits and bad bits. and picking out just the good bits for a week, for someone who doesn't understand the context, is hard.
so it seems to me that there's a disadvantage to the company - they are discouraging people who are good enough to not be desperate and attract people who think that a typical job (sorry, but most are, by definition) is "pretty cool".
or maybe they just get younger, less cynical employees ;o)
- mason55 13y agoYeah I've considered doing this a bunch of times but my biggest problem is coming up with small chunks of work that require little-to-no domain knowledge and can be done in a day/weekend/week. We've switched to having candidates do two take home problems that are derived from actual problems we faced and it's worked very well. It cuts down on the number of bad candidates that get to the office and waste an hour of time and it gives a chance to candidates who are good coders but bad whiteboarders.