If there is any on line code I can reference I will always take a look. Looking at someones code is a great way to see how they approach and structure problems. The code as well as the problems they choose to tackle tell a great deal about the candidates level of maturity and the kind of code that they are going to write once they start working with you. One of the last candidates I interviewed, when I was corporate, was a great talker but when I looked at his code on github it was full of AbstractDefaultFactoryProxyDecoratorBuidler's...Mehhhh, my boss hired him and loved him anyways (and now he's working at LinkedIn, so what do I know)....But he did fill up our code with the above types of garbage classes.

Same. Nobody gives a shit about your open source stuff on Github unless you are known for some other reason already. It's worth commenting on because of how often job seekers are told "do Open Source," as if this were an actual advantage in practice

I always check github when it's included. It's a great way to determine a person's follow through, ability to organize a problem (or set of problems), code quality.

Oftentimes, the great coders are so anal about the code they write, that it's highly refined, well organized and thorough (mostly because they can't attach their name to bad code, especially when it's public). Those are the guys you really want on your team.

That surprises me - if I get a resume with a github url on it, I always look at it. Maybe it would be different if they all did, but to me it signifies that they do interesting stuff.

Of course, I've gotten ones with a github url with no repos in it or some piddly little thing, and that sends a different signal.