Hacker News new | past | comments | ask | show | jobs | submit login

I think the GP's point was that if they are looking to get a job, they probably has many options of good places to work (even if perhaps not as good as yours) which would not require this of him, and therefore your audition can be seen as extra work which they do not need.

Now, if I were Very Interested in working at Discourse, Fog Creek, or any similar place of work, rather than just at any place with a nice paycheck, I think the audition is a great idea, and something people would be willing to do.

The GP's main objection is that you only get the best people who want to work at __your__ company enough to spend time on your auditions. There are likely many engineers like them who have a network of job opportunities compelling enough that the added draw of it being Stack Overflow, Discourse, or Fog Creek is not enough to merit the extra work.




It might also work if the audition was applicable to many potential employers, like how talent scouts in sports and the arts go to events where the potential talent performs rather than having the person audition for each potential employer. (I'm not an expert on arts or sports so I might be off on my analogy.)

I hear a lot about GitHub, blogs, and open source contributions which essentially act as your audition open to all talent scouts.

Perhaps if the audition challenge could be posted to the applicant's GitHub account then it would be a bit more useful to the applicant. The challenge could be skipped if a project in the GitHub account already demonstrates proficiency in the desired application domains.


The sports analogy is partially correct, but college prospects in all the major sports have to go to the talent recruiters before they are signed. (NBA tryouts, NFL Combine, etc.)




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

Search: