How to Source Github for Technical Talent

Editor’s note: This post is part of our Source the Web series here on SourceCon. It features articles on how to mine particular online data resources from experts like Shane Bowen.

If you’re a technical recruiter or sourcer, then you’re likely familiar with Github’s existence. However, sourcing Github can be tricky and even intimidating for some, especially if you approach it as you would other social networks like LinkedIn, Twitter, or Facebook.

Because Github is a community where developers share code, it’s best if you have a clear understanding of what you’re looking for as this is not the place for “title” recruiters/sourcers. If you’re looking for a software engineer, you’d be better served NOT using the term “software engineer” in your query and instead search for what the software engineer is working on.

The beauty of Github is the amount of layers the site has and how accessible it is via search engines and the more tech savvy you are; the better. There are many ways to build out your query to find what you’re looking for on Github, the following should help get you started. Add search terms as needed!

Github Profiles

Profiles: [ site:github.com “joined on” “public activity” -tab.activity ]

Profiles with location: [ site:github.com “san francisco” “joined on” “public activity” -tab.activity ]

Profiles with above + key terms: [ site:github.com (ios | android) “joined on” “public activity” -tab.activity ]

Profiles with above + followers | starred count: [ site:github.com (“50..250 followers” | “100..500 starred”) (ios | android) “joined on” -tab.activity ]

You can also expand your search by removing [ -tab.activity ] in any of the strings examples above. Or target the activity page with [ tab.activity ]

Additionally, you can include “email *” in your search string to return profiles that contain an email address in them, however email addresses are obfuscated and the returned results may include some noise if the term email is used elsewhere in the users profile.

Narrow results by when a user joined: By year “joined on * 2009?  or by month  “joined on mar *”

Article Continues Below

Github/Uploaded Resumes

Github Resumes: [ site:resume.github.com ]

Uploaded Resumes: [ site:github.com (intitle:resume|cv|vitae | inurl:resume|cv|vitae) -inurl:https|format ]

Uploaded Resumes 2: [ site:github.com (intitle:resume|cv|vitae | inurl:com/resume | inurl:com/cv | inurl:com/vitae) -inurl:https|format ]

Github Organizations

Organizations: [ site:github.com “joined on” “repositories * members” -tab.members ]

Organization locations: [ site:github.com “san francisco” “tab.members” ]

Organization members: [ site:github.com inurl:tab.members ]

Organizations + member count: [ site:github.com “50..500 members” “tab.members” ]

Organizations + public repositories: [ site:github.com “1..100 public repos” “50..500 members” -tab.members ]

Oranizations + repositories OR members: [ site:github.com (50..500 “public repos” | “members”) “tab.members” ]

Github Blogs/Personal Pages

[ site:github.com (intitle:musings|blog) -inurl:https ] [ site:github.com (intitle:musings|blog | inurl:musings|blog) -inurl:https ]

There are literally countless ways to source Github and it would be a boon to any technical recruiter or sourcer to get familiar with the network. It not only lets you uncover great talent, but can help you become a more effective recruiter/sourcer by encouraging you to gain a better understanding of what the role you’re trying to fill requires.

This post originally appeared on Sourcinghacks.com