How is SeekOut's GitHub search different?

Article author
  • Updated

GitHub is an amazing place to find code and an extremely popular site for deeply technical engineers. Even though it has millions of coder profiles, however, it's a tough place to find candidates because:

  • It's difficult to tell the difference between a GitHub member who has done interesting work and one who has just forked several repositories but never made an impact with his or her code. 
  • Most GitHub profiles are incredibly sparse, without any mention of location, current employer, or any other basic data about the candidate. 
  • Without lots of clicking around, it's hard to even see what a GitHub user is interested in, let alone what kind of code they've written.

SeekOut's GitHub search solves these problems so you can source GitHub with efficiency. 

Specifically, we've taken the grunt work out of sourcing GitHub by:

  • Indexing the descriptions and metadata of all repositories (software projects) on GitHub to know what they are about, how widely used, and how influential they are.
  • Analyzing each code contribution on GitHub to understand how impactful it was (e.g., Was it made to an important project or in a branch with just one contributor? Was it reused by others? Etc.)
  • Rating each GitHub member's overall coding ability -- the SeekOut Coder Score -- as well as their proficiency with each individual programming language.
  • Merged the data in their GitHub profile with their public profile (from sites like LinkedIn). This is important because GitHub profiles are deep, but narrow and public profiles are wide but shallow. By combining them, you can search based on "deep" knowledge of the candidates technical expertise as well as "shallow" characteristics like location, company, education, etc.

Was this article helpful?

Article is closed for comments.