You may well know the requirements that your company/client wants from a technical role, but if you’re not a developer and have no technical experience, how can you relate to the candidate’s employment needs and trends? Well, luckily, Stack Overflow conducts an annual developer survey, and we’ve got our hands on the results. Hold tight for the 6 key hiring insights for IT Recruitment in 2016…
1. Most candidates are passive
(Though you should already know this)
For instance, in the UK, 60.2% are passive candidates, while only 12.9% who are actively searching. Roughly a quarter of these active candidates are students, so you will need to use different methods to attract the right candidates, especially if the role requires commercial experience.
2. Most developers are referred by a friend
3. Salary is very important, but not unanimously
Global data suggests that 62.7% prioritise salary when looking for a new job, with work-life balance (50.4%), and company culture (41.8%) in second and third. However, it is not what developers care about the most, especially as 37% of developers didn’t even include salary on their list of priorities. Interestingly, British developers are more concerned with location.
4. Developers are happiest when they’re coding
According to the results, 65% of developers who never check in code are satisfied with their jobs, versus a 77% rate of satisfaction among developers who commit code multiple times per day. It’s not a huge difference, but it’s definitely a nod towards a correlation – and something to consider within your hiring strategy.
5. Remote developers are more satisfied
When asked if they love their jobs, 44.5% of full-time remote devs replied with a yes, and 35.7% of part-time remote workers also agreed. Of those who never work remotely, only 24.5% say they love their jobs. This definitely suggests a correlation, so if you’re keen to hire, and able to offer location flexibility, it could well be worth your time.
6. Developers are extremely keen to learn
Globally, 70.1% of respondents said that once within a role, they want to learn new technologies, and 64.3% want to build something new. In this vein, it’s clear that if you want to place a developer into a new role, it needs to be a position in which they can develop their skills and face new and exciting challenges. Interestingly, getting promoted was further down the list, with only 30.1% placing this as an on-job priority.