Use Tech Rankings to Source Candidates (and Find Hidden Gems)

We have built developerDB to be the most useful sourcing platform for tech recruiting. We are adding more features and search functions weekly. And while we are ecstatic that our beta users are using the default search functions to find, review, and contact candidates, we also want to encourage you to try something new.

One of the most exclusive functions that developerDB has is the technical rankings of developers on GitHub and Stack Overflow.

Right now there are three ways to prioritize your search results:
1. Work History: Shows profiles that have work history first
2. Expertise: Prioritizing candidates that are highest ranked for the first search Skill keyword (if you have more than one)
3. Diversity: Show candidates that meet the diversity search

The default search is Work History. But we encourage you to try prioritizing by Expertise.

METHODOLOGY

How did we rank users of GitHub and Stack Overflow?

For GitHub, we looked at the tech tags of all publicly available repos of a user. Repos with same tag were grouped together. For example, if a GitHub member has five repos that were tagged as python, we would group them together and added all the stars of those five repos. We then added up all the stars of repos of a specific tech tag. Next we rank how many stars for a specific tech tag against everyone else with repos of the same tech tag on GitHub. 100% percentile is the best.

For Stack Overflow, we looked at the tech tags of a user and compared their score for a specific tag (ex python) to same tag for everyone else on Stack Overflow.

WHY USE EXPERTISE IN SEARCH?

When you are searching using job titles and work history, you are missing out on all the developers who:

1. Have not updated their various social media accounts (from where we extracted out their information)
2. Don’t have much information on their various social media accounts
3. Transitioning to a different role but already acquired the tech skills

But those that are ranked high should receive a second look regardless of job role or education. Their peers have voted them up based on their codes or ability to elegantly explained complex technical problems. But if you search by job titles keywords, you may miss out on them.

Yes we know the demanding and unrealistic hiring manager may not go for this but you got data on your side. Thousands of developers can’t be wrong!

Happy sourcing and please do let us know how we can help you with your sourcing needs.

Leave a Reply

Your email address will not be published. Required fields are marked *