News for hackers. Stuff that matters.
Re:The GitHub Job Interview by enry_straker on Sunday January 08, 2012 @07:49AM (#3439446)
That is a sensible idea - but i would go one step further.

Ideally you want to learn about a potential candidate's design/coding/debugging/bug-fixing/testing skills. Github project collaboration over a week or so would go a long way towards that.

But you also want to see how well the potential employee communicates with other members of the team, on a day-to-day basis. Some Developers, even good developers, have strong opinions that might rub other employees the wrong way. The key is to look at how well they work as a team.

Having them spend a day or so onsite with your existing team is invaluable. You might also want to consider paying them a nominal amount for the amount of time they would spend on the project. That just adds a professional touch to the whole experience.

Re:The GitHub Job Interview by rhizome on Sunday January 08, 2012 @10:59AM (#3439764)
"Consider" paying them?
Re:The GitHub Job Interview by slavak on Sunday January 08, 2012 @12:51PM (#3440043)
Note to self: Never work for enry_straker.

If I'm onsite with your team working on your code-base, someone damn well better be paying me for it. Not to mention those kinds of shenanigans are downright illegal in some parts of the world...

Re:The GitHub Job Interview by devs1010 on Sunday January 08, 2012 @12:59PM (#3440070)
This is what contracting is for, no one in their right mind with any sort of real experience is going to spend 2 days on-site working for someone for free.