Why GitHub should be in your sourcing toolbox
Linkedin, Indeed, Monster. What do all these sourcing platforms have in common? They all rely on resumes to find the best candidates. Well this method may have worked pre-social media, it certainly does not work well now. Let me give you an example of why they don’t work.
This is an example given for a "good resume" for a Senior Java Engineer. If you read the article where the example is taken from, you can see that the recommendation given (which is given by many people to candidates) is for the resume to be optimized for ATS systems to read rather than for humans. The most relevant thing to practical skills in this is "Applied relevant technical skills" - which tells you absolutely nothing except that the candidate believes their skills to be relevant.
GitHub is the key to finding talent while also being sure that you've found the right talent. Since it contains real projects built by candidates, you can verify the skills that the candidate is talking about and ensure that you're on the same page long before you pickup the phone or shoot an email off.
Great question. GitHub is the world’s largest collaborative software developer community. With over 50 million members from hundreds of countries and 11% coming from the USA, it is an amazing talent pool. While Stack Overflow only has 10 million users registered as of 2019. Moreover, a survey conducted by Stack Overflow concluded that 28% of technical talent cannot be found on Linkedin. Why? Developers don’t want to be spammed by recruiters and don’t even bother setting up a LinkedIn account.
While GitHub is fruitful, it would not be possible without some elbow grease. Here is a basic rundown of what you need to do to conduct a basic search on the platform.
Well, if it were that easy, everyone would be doing it. The problem with GitHub is that conducting specific searches is tricky and in many cases, not possible. For example, GitHub cannot distinguish between backend Java developers vs. Android developers (both exist in the 'language:Java' search). For all my tech savvy recruiters out there, you will realize that these two searches are not the same thing.
In other words, GitHub search results are a big melting pot that groups developers who are frontend developers, backend developers, mobile developers, etc.
This search provides 19K users. Guess what? They aren’t sorted in the way you’d expect. GitHub, like many social media platforms, relies on superficial metrics to figure out who are the best developers on the platform. This results in the implicit diversity biases of the industry and platform becoming part of your sourcing process. Here are a few examples of what GitHub likes:
What is the one thing GitHub neglects to do? Tell a recruiter if the candidate is worth hiring! Luckily, for all those tech savvy recruiters, there is a way out. You can read the candidate code and figure out for yourself if they are
But you’re probably going to be staring out thousands of lines like the code snippet above. But hey, at least you have access to an exclusive talent pool.
If you’re thinking that there must be an easier way to get around all this hard labour and still reap the rewards, I like the way you think! HireFast is the perfect solution, offering a search engine built on top of GitHub that reads
the code for you and shortlists candidates so you don’t have to read any code. Focus on nurturing candidates, and leave the sourcing to HireFast! We have a free trial for you to get started and check out the quality for yourself.
No credit card required 💰. So you keep your money till you think we’re worth it!