Comment by michaelchisari
11 years ago
A lot of people require a github to get an interview. But nobody wants to look at what's on the github.
I've interviewed hires before, and if I ask for a github, I'm going to take the time to review some of the code, otherwise why would I ask?
The link between the content of your GitHub and your ability to ship code is unclear at best. I knew a guy who had a really awesome GitHub profile but turned out to be a mediocre contributor to the codebase. He claimed that coding style guides we used were hurting his creativity to the point that he did not enjoy coding and would avoid it if possible. He'd fix bugs and make small-ish contributions but would never ship major features or libraries "because of the style guide". While I understand the sentiment I always found his attitude juvenile.
Seems like that's something you could easily suss out in an interview if you asked him questions about his code on github.
This is about Google, which does not require a github.
The thread is about the industry in general, which has adopted Google's algorithm heavy interview process, but also adopted github and open source as a resume.