Ugh. If you really want to do this, try a whole bunch of nasty heuristics on github profiles - analyze how "carefully" they code (kind of apis they use, coding

Ugh. If you really want to do this, try a whole bunch of nasty heuristics on github profiles - analyze how "carefully" they code (kind of apis they use, coding style, defensive programming, etc.); how much care they take polishing their projects (frequency and type of commits, comment sentiment, refactoring, etc.); how well they write documentation and unit tests, and such. It would be an interesting academic project, but I doubt you can really create an acceptable scoring model out of it. In many ways the "certification" for software engineers is a misnomer. For me, github is a certification of sorts - a (biased) view: good engineers code for passion not money. I'm sure there's lots of good engineers that don't have a github, but I prefer those that do.