I came across a post in a sourcing group about new software that collects resumes on GitHub and allows you to search through this resume database (haven't had a chance to test it yet, but planning to).
I have a few thoughts that I would like to describe more specifically and share with you.
Unfortunately, only a small portion of my colleagues in their daily searches go beyond the usual sourcing platforms.
They start with their internal candidate databases, which almost all companies maintain in the form of Excel spreadsheets or ATS (depending on their setup). Or they initiate basic search queries on LinkedIn, often without a well-thought-out sourcing strategy.
And they stay there... After all, you need to go through thousands of profiles mentioning the required technology.
But if you "think outside the box" and take a broader look at sourcing, then GitHub will definitely be the next step in finding specialists.
Resumes on GitHub?!
The platform has a robust internal search feature that allows you to search within the platform, even if you are just getting started here.
Hundreds of thousands of repositories, discussions, millions of lines of code — users should easily find the information they need.
In the screenshot, we can see that the platform searches across all sections and suggests you choose where you would like to get the results: Code, Wiki, or, for example, Users.
In the Advanced search section, there are already more variables for you to calibrate your search.
And most importantly, in addition to search criteria for Repositories, Issues, Code, there is a User search block, and this is exactly what every recruiter/sourcer needs.
After all, what interests us most is finding specific specialists and their personal profiles in the system.
Where to find resumes on GitHub?
Repositories
Often, in addition to the projects they work on, developers create a separate repository specifically for their resumes.
This is convenient: it's a familiar environment for them, always at hand, and they can even show their code if asked.
It may not be as familiar to recruiters as searching on LinkedIn, but finding such documents and reviewing a dozen or so repositories will make them less intimidating and become a useful tool for gathering and analyzing information about candidates.
Bio
Yes, in the self-description section, in addition to the usual usernames, contacts, or the company they work for, users could leave a link to their resume.
Technical professionals often create personal pages with descriptions of projects, companies they've worked for, and tasks they've performed when looking for a job.
Or they simply create a one-page document with information about themselves [read as "resume"].
Readme.md
A relatively new section where everyone can fill in their information.
If you haven't filled in this section yet, then it's time to create your first repository on GitHub.
And, of course, it's an excellent opportunity to gather more information about a potentially interesting specialist!
You can also build search queries using common phrases that are used in this section.
Elsewhere
But in general, you can and should search everywhere:
- Check the bio.
- Look at repositories.
- Explore topics related to your technology stack.
- See who has contributed to repositories.
- Come up with a creative search using a username or name.
I've encountered resumes in a live format several times. When the document is filled with basic criteria like Name, Surname, and contacts, these parameters are static.
And flexible blocks: Popular user repository, Number of their contributions over a period. They are generated based on the profile's activity on GitHub.
Changing your daily search routine can be challenging. Your brain resists going against the usual set of actions, limiting your results. Dedicate some working time each day to testing new approaches, channels, and tools.
No super-secrets needed! Just give GitHub search a try.
