Github is a social-programming website. Meaning individuals can post open source code to a community. This allows users to create profiles (social) and upload there “repositories” to the website.
What is Github to a Sourcer/Recruiter?
Let us develop the answer by stating what Github is NOT. Github is not a source for a recruiter to go to, as a means of acquiring all information needed on an individual to store into a database.Now that we understand what Github is not. We can now transition into what Github IS. Github, in the mindset of a sourcer or recruiter, is a tool to use to begin their headhunting journey.
Headhunting does not have to start with Github. A recruiter can use various e-establishments to start his/her searching. Such as Facebook, Google, Twitter, Linkedin etc. But for today’s sake we will allow this document to be solely based on the Github foundation.
When you approach github.com you can determine at that moment in time if it is in your best interest to sign up and register for an account or take the easy way out and just use the site as a search tool.
There are both pros and cons to doing both. As of right now (2011) github allows anonymous individuals to browse their site without a registration. However, the downside is obviously you have no access to e-mail if needed.
For our purpose, let us hypothetically assume you are registered and ready to go.
So the site’s layout that we need to pay attention to is on the top right below your account information. It is the search bar.
This is your gateway. Learn it and Love it. Searching is an art. It’s not just some random thing you take for granted in our industry. It’s serious business. Got it? Good! 🙂
As we proceed for training purposes we will use a current search that I used today (July 11th 2011) while I was working on Box.com. Box is a current client who has sent us a high priority “Lead Security Software Engineering” role. It’s an important role, and because we don’t get this type of REQ on a weekly/monthly basis, our Database lacks qualified candidates in the area/core skills of “XSS/ CSRF/SQL Injection”
What does this mean?
It means its time to become that traditional “Headhunter” that oh so many people talk about. Good or bad, its what we do.
“Show me the $MONEY$”
So as we transform ourselves into the mindset of headhunting, take the term “CSRF” and input it into the search bar. This allows you to find every relevant repository that has been created by an individual for the community.
A repository in a sense is a way for you to show off your programming skills to those who most likely can read it. Not everyone who uses Github can actually read the complex code. So don’t feel alone. For those who might not understand the coding, but have to use github as a recruiting tool, we have three tools to pay attention too once we have our target.
You may be asking, how do we find our target. If this is the case here is a visualization:
Once you have accomplished the above visualization, your next step is to sift through the data. This means you go through the list. In our case, I had to go through 4 different candidates who I was able to disqualify due to three areas of interest. These are:
1. Location of an individual
3. Public Repositories
Your next inevitable question for this exercise should be: How do I find out about those listed above. And once I do, how do I dictate the process of how to disqualify candidates easily, efficiently and quickly? To answer these questions Lets look at the next step of your training visually.
user of the repository
After you clicked your target that you are interested in, you are presented with his comment, for instance “fixing another typo left over from old code” and a author who you can continue lurking (gathering intelligence.)The second part of the above picture is the open source code. My personal opinion is that it is irrelevant to me only because I do not have the ability to read code. However, please don’t take this as me saying that the information is irrelevant. No, not at all. But I do use the three tools as my main source of quick disqualification.
Find out detailed information about Location, Public Repositories, and Followers down below
3 areas needed
1. Location (Objective)
This is the most important and objective source of information that we use to disqualify a candidate. Our world in 2011 has 750,000 developers. So Github is a international community. Therefore, you need to disqualify candidates based on geographic location.
2. Followers (Subjective)
The reason I write subjective next to followers is because there is no real recipe for us as an agency to disqualify or even favor a potential target by his number of “followers”. With this in mind, let us use followers as a means to understand a persons influence without using a mathematical algorithm. A large part of our job as a headhunter is based off of having an “eye” for patterns and using intuition as a means to determine possibly pursuing a candidate.
Basically, I am inferring to you as a new individual, to lurk github, understand who has influence, develop a hierarchy in your mind and go from there.
In the case of Lorenzo, has 69. From my experience, and based on our recent success with him as a candidate, 69 is doable and influencial. However, match him against someone like Paul Irish from Google Chrome who is a innovator in HTML5. Lorenzo is no match. (Paul Irish:1,700k plus )
3. Public Repository (Subjective)
This as well is a subjective tool that we can use. Understand that there may be a diamond in a ruff on github, but for some reason he only has 5 public repositories on github.
So use these subjective tools with caution.
What this can tell you, is how passionate they are about the developer community, and the idea of “open-source”
So those are the main tools that I use to disqualify candidates. If they pass these requirements, I then continue on with the headhunting process into other domains on the internet.For instance if we have his handle name “Zeelot3k”
but no “Lorenzo”
I can go to google and search that name and possibly find his twitter account, which may give me more information like a website and such.
Since we have Lorenzo’s name, I was able to go to Facebook during my time and add him as a friend. In like 20 mins he responded to my message. I was able to come to that conclusion of adding him to fb because he is young (my age- 20’s) and we are a generation that loves fb. (my opinion)
If your lucky, that the person has an e-mail attached to github, you then can add them to your Database. You will at least need a phone number or e-mail to consider it a successful headhunting task.
So there you have it, use github as your tool to find out the beginning process of an individual and move along the process after qualifying a candidate and move into the first contact phase.
Let the force be with you!