[windle]

I've met total posers that can whip up the little snippets that people have time for in an interview... and I've met great coders who crash and burn a live code session due to interview stress.

I've consistently found open-source code to be a much better sample since the person being interviewed is not under such pressure when writing it. And yes, the pressure from being in a room with 3 ppl watching you is very different from "deadline pressure" to complete a task when employed.

I don't think the github resume is going to be the standard for quite awhile, but I know it makes my job when hiring much easier when we can discuss code and techniques used in an open-source project the interviewee wrote, than arbitrary questions that only prove he's recently memorized an algorithm book.

The real thing developers should think about, is the competition. This is what made "has college degree" an easy filter for employers. If you have 800 applications, tossing the ones missing a github repo in addition to the college degree trims it down a bit more.

Will you miss some possibly great people? Absolutely. Same with the college degree filter. But you'll still likely end up with a bunch of "would like to hire" candidates and it'll be easier to see what their work actually looks like. If you're applying for a job, you should absolutely consider how to stay ahead of the competition, and I'm sure companies in the future when bombarded with so many applications will add things like this to the resume filter.