Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I remember reading Heroku does similar. Using applicants in a project works well.

I have always tried to push my potential employers to use me on a small real life project. I know it's time consuming (and you end up working for em for free) but it works both ways. I get to know what kind of work environment they have and they get to know me in a real deal. I find it much more comfortable because the puzzles always seem to be a hit and go. The solution may click or it may not.

I know it's a start but if this catches in the industry I expect employers to even pay for your 30-40 hours interview.



I expect employers to even pay for your 30-40 hours interview.

It's great if the new employer pays you. But what about your current employer, the one at which you've just had to spend half your annual allotment of vacation days in order to audition for a new job that you might not get?

Auditioning is definitely the best way to, well, audition people. But it puts a constraint on your candidate pool, and depending on your company and your industry that constraint can be a problem. In 37signals' situation this doesn't matter - they're built entirely on open-source tools, they don't require relocation, they can hire freelancers from a pool of freelancers that they themselves created and fostered and routinely market to, they are so famous and impressive that even in a tight labor market people will line up to try and impress them, et cetera. But there are many companies that aren't 37signals, though the 37signals evangelism team is certainly trying to change that. ;)


We do follow something quite similar. The write up on how our process works is here: http://www.craigkerstiens.com/2011/12/02/how-heroku-works-hi...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: