Overall Satisfaction with GitHub
As a technical recruiter, I use GitHub to identify users of the site who are skilled in specific technologies. For example - if there is a discussion about using microservices to break down a big ball of mud, I would then start looking at the profiles of developers who seem to have expertise in this area. It's especially helpful when recruiting for developers - just because someone codes in Java, doesn't mean they're a fit for a Java Developer role - it's about what they've done in Java. Github helps me discover WHAT they've done - not just what language they've used.
- Identifying developers who have particular skill sets or interests beyond the stack they use.
- Demonstrating a developer candidate's knowledge, coding, and philosophies
- Showing that a developer is dedicated and passionate about their work - GitHub is voluntary - if they're spending time on there, it's because they want to be.
- Finding the passive seeker - GitHub isn't a job board.
- A lot of developers and recruiting sites don't realize how important location still is - not everyone is willing to allow remote workers. Being able to know where the developer lives would be so helpful.
- It would be great if companies could create exercises for people to complete - just to see if they are a fit. To make it part of the hiring process would require validation. If it's a voluntary exercise, it would be easy.
- Knowing the background & years of experience of the developer.
- It's been a learning tool for me, as a recruiter
- It's been a new avenue to isolate specific skillsets
- It's a way to find candidates you wouldn't find otherwise.
GitHub is different - it is about finding skills. Entelo is about finding contact information. Greenhouse is about storing and Scavado is a little like Entelo and GitHub combined. They are all very different tools. I would say that GitHub is a secondary tool.