We're recruiting at the moment. Did we mention that already? (Good people please send CVs and pithy intros to firstname.lastname@example.org). Anyway, it has thrown up a rather interesting set of selection criteria one in particular.
We’re recruiting at the moment. Did we mention that already? (Good people please send CVs and pithy intros to email@example.com). Anyway, it has thrown up a rather interesting set of selection criteria - one in particular.
As I come from a marketing background I have always selected people based on their attention to detail and their ability to market themselves. A personalised, well-written letter that says something about why they’d like to work for me/the company has usually been enough to secure an interview. Spelling and grammar errors, or boring generic letters have ruled out 90% of applicants before I’ve even looked at their qualifications.
But recruiting developers is a little bit different to recruiting marketers. So what’s the criterion that allows us to filter out developer candidates?
Whether or not they have a Github account*.
This is important: Github is not widely recognised as a source of identity. You wouldn’t naturally think of it as a source of data for qualifying prospects. But for our specific needs it is very, very relevant.
This is true for many different types of prospect in many different industries. There are niche data sources that could help to qualify prospects in much greater depth than the ‘obvious’ sources such as Facebook, LinkedIn and Twitter.
This is why we’re creating CANDDi Services, a dedicated team to help clients create bespoke modules for CANDDi to tailor the platform to their own specific needs. Now whatever data source you want to plug into CANDDi, and whatever software you want to integrate it with, we have the resources to make it happen.
*This rule isn’t hard and fast but it has proven to be a pretty good benchmark for quality.