Based on 2016-2017 Talent Shortage Survey, IT professionals constitute the second biggest talent shortage group globally and one of the hardest groups of professionals to recruit. LinkedIn is the go-to place for sourcing software developers for majority of recruiters, so it’s a very crowded and competitive space. The higher the demand for top tech talent, the more efficient you need to be with your sourcing. In this post, we explain how to source software developers from LinkedIn.
Source: 2016-2017 Talent Shortage Survey
In order to maximize the potential of a very limited talent pool, you need to get the most data from LinkedIn and be creative. It takes a certain amount of experience to work out an effective pattern – here’s how to become a LinkedIn sourcing superstar.
LinkedIn search filtering
Let’s start with the basics, shall we?
You can look for people with a given skill or join groups on the subject (which I also wholeheartedly recommend).
Here are the results you get when you run a simple location-specific search for people who specialize in Java. To narrow down your results, you can use the LinkedIn search filtering menu located to the right:
You can choose from the “Industry” menu:
- Computer Games,
- Information Technology and Services,
- Staffing and Recruiting,
- Program Development.
Another way is to search via current and past companies (you can add any company to the list):
The “Company” option also allows you to prioritize organizations with the largest talent pools and focus your employee branding effort on their current and past employees. The same goes for schools and universities, but you shouldn’t be too attached to the requirement of a formal degree, as 70% of devs say they are self-taught (2016 Stack Overflow Developer Survey).
Using job-specific keywords further increases your chance of finding the right person. However, remember that early in the process you should try to be inclusive. If you’re not, you’ll most likely miss some gems. To what extent? The impact of omitting or altering job criteria is presented in the LinkedIn Talent Solutions ebook entitled Data Driven Recruiting: Find quality hires faster with talent pool analytics. Check it out for yourself:
Source: LinkedIn Talent Solutions
As you can see, removing or altering just one of the criteria increases the talent pool over 6 times, and that makes a huge difference in a very crowded and limited talent pool everyone is trying to source software developers from.
The problem with the basic one to two keyword search is that the results you retrieve are identical to those of your competitors – read on to find out how to get some more unique ones. But before we get to that, it’s time to talk talent pools.
Talent pool size
Data is a strategic asset in talent acquisition, but according to LinkedIn Talent Solutions resources, 2 out of 3 recruiters don’t have the tools to understand the market and talent pool they are trying to recruit from.
Do they need them? They certainly do, as a staggering 77% of recruiters believe they are more efficient when they understand the market and talent pool they are recruiting from.
Source: Data Driven Recruiting
How to assess talent pool size? Let’s see how many people mention “java” in their profiles in your area:
…and play with the filters and search options. i.e. by adding more requirements through running a “java ruby” search in the same area. Remember that when you add keywords in a string, LinkedIn reads it as if there’s an “AND” operator in between.
Erik Putkonen talks about getting talent pool insights from LinkedIn in this post and he says that by adding every requirement from the list “instead of just saying that there were too many requirements or that few would meet these requirements, I was able to show what the numbers were” for each of the requirement. You can see exactly which of the requirements shrinks your talent pool most and decide if you can alter or omit any of them.
Here are the results of an iterative search Putkonen completed:
Source: Recruitng Blogs
Like I mentioned, the problem of the basic one or two keyword search is that you find people who everyone else finds. Because they are from the top of the pile and people usually go from top to bottom, these people are frequently contacted by recruiters and to put it mildly, they are most likely not in love with the idea of recruiter outreach.
How to find someone who’s not receiving tens of messages a day?
Meet Glen Cathey of Boolean Black Belt who rightly argues that as so many recruiters use LinkedIn at work, you need to get competitive advantage over them. One of the ways to do so is to improve your searching skills so you access what Cathey calls “LinkedIn’s Dark Matter”, or undiscovered profiles. To do so, you need to think (and search) creatively – this Ruby LinkedIn sourcing challenge is a great place to see what Cathey means by creative developer sourcing. Cathey argues that Dark Matter results constitute “at least 50% of the each source searched”, so there’s a lot at play here.
Glen Cathey believes you should run multiple searches (he calls that process “iterative search”) to get optimal results. Here’s his recipe:
- “Start with maximum qualifications,
- Use the NOT operator to systematically filter through mutually exclusive result sets,
- End with minimum qualifications.”
So, as Cathey advises, you should specify:
– Required qualifications: A,B, C,
– Explicitly desired qualifications: D, E,
– Implicitly desired qualifications: F.
Here’s how you go from maximum to minimum qualifications:
Source: Boolean Black Belt
And here’s the discrepancy between maximum and minimum results you could be getting:
Source: Boolean Black Belt
It’s probably even bigger, as some LinkedIn users don’t mention certain terms on purpose. They do it to avoid getting found by recruiters. Example? There are people who are experts in Java who never use the word “Java” in their LinkedIn profile because they don’t want to be found so easily. They want to be accessed only by cream of the crop recruiters who know how to search out of the box.
A great idea Cathey gives in his presentation is that you can run a search to find “software engineers or developers or programmers who have that as their current title but they don’t mention any primary programming language”. These people don’t show up in the standard “java ruby” searches most tech recruiters rely on and as a consequence are less frequently contacted.
Let me show you a practical example of how you can access less frequently retrieved results. If you’re looking for cloud experts, you can just search “cloud” in your area, but you’re only accessing top of the pile candidates again. However, if you work on your iterative search, you’re getting competitive advantage over your colleagues. You don’t need to specialize in the discipline – Cathey mentions he uses Google to confirm or deny the relationship of the terms with the skill he’s looking for, because most times he doesn’t specialize in it himself.
It’s hands-down one of the best tips I’ve ever heard on sourcing devs.
You can also use the following field commands inside LinkedIn:
Caution: These commands need to be written in lowercase and the Boolean operators AND OR NOT must be written in uppercase. Social Talent has a great post on the 2017 changes in internal LinkedIn searches which I urge you to read.
Another amazing point on the importance of polishing your search skills is made by Irina Shamaeva of Boolean Strings blog. Check out these discrepancies between returned results – as you can see, LinkedIn algorithm is puzzling and research is key when you’re searching:
Source: Boolean Strings
Both Cathey and Shamaeva are great experts and I strongly recommend following them to learn how to retrieve top results and think creatively when it comes to sourcing.
Commercial use limit
There’s a commercial use limit on free LinkedIn accounts when you browse LinkedIn for the purpose of hiring, prospecting or scraping. According to LinkedIn Help resources “this limit is calculated based on your search activity since the first of the calendar month.” Data security limit on profile views may also prevent you from temporarily viewing profiles of members you’re not connected with.
Here are the data security limit parameters officially listed by LinkedIn:
- Search frequency,
- Viewing suggested profiles,
- Non-name searches,
- Mobile searches,
- Searches outside your network
- Other factors.
You should also know that things recently got more difficult as there is now a limit of profiles you can access from outside of LinkedIn, as Social Talent pointed out in August 2016.
Source: Social Talent
LinkedIn is trying to block X-ray searching via browsers to some extent and encourage people to use premium products like LinkedIn Recruiter. Interestingly, LinkedIn doesn’t publish the exact number searches allowed (people claim it’s around 50 for most free users). With the Premium subscriptions profile views are unlimited.
Here are the activities that don’t count towards the data security limit:
- Searching profiles by name from within LinkedIn (through the search box),
- Browsing 1st-degree contacts using the connections page,
- Going through jobs on the jobs page.
While a lot of tech recruiters rely on the free version while they work, others use LinkedIn Recruiter Lite which comes at $119.95/MO. I’d definitely recommend checking it out because you get 30 InMails to engage with top talent and I think that’s by far the best feature. If you’re not sending these messages on a regular basis, I think you’re fine with the free version if you know how to work around the commercial limit. You can do that by viewing profiles while logged out or in incognito mode (check the comments of this post for more details), and X-ray LinkedIn on Google.
Google X-ray searching LinkedIn
X-ray Searching LinkedIn via Google is a good skill to have. Here are the basics of the technique:
- Log out of LinkedIn (some people also go to incognito mode to do this),
- The general rule is to use “site: or inurl: operator in Google, followed by the URL of the site you are searching on”, so in the case of LinkedIn it’s site:linkedin.com or inurl:linkedin.com, the difference being that the inurl: searches the whole URL and the site: searches the domain (so the beginning of the URL),
- Think of your keywords and use any of the already mentioned field commands (title: company: school: firstname: lastname:) and Boolean operators (AND OR NOT).
Here’s a sample X ray site: string (click the link to see results in Google).
site:www.linkedin.com intitle:linkedin “current * test manager” -intitle:answers -intitle:updated -intitle:blog -intitle:directory -inurl:jobs -inurl:megite.com -intitle:profile -inurl:jobid (Source: Boolean Black Belt)
It seems really complicated but you’ll get accustomed to it very quickly when you start doing it on a regular basis. The secret to X-ray searching is to use shortcuts. One such shortcut is this Google Custom Search hack proposed by Irina Shamaeva:
and you’ll see a search box. Type in your keywords to see the results in Google (remember to log out of LinkedIn first).
The link above simply shows the results of this search: https://www.google.pl/search?q=site:linkedin.com/in+OR+site:linkedin.com/pub+-pub.dir&num=100&newwindow=1&filter=0&gws_rd=cr&ei=IDD3WKmkJ6PX6QTfnIbgAg and the results you get are identical, it’s just quicker to carry out (hey, shortcuts for the win, right?).
The notion of X-ray searches is really complex and due to lack of space I can only signal that you need to pursue it to source like a boss (please do, it advanced searching rocks).
Location & willingness to relocate
According to Manpower Group 2016-2017 Talent Shortage Survey, average global talent shortage equals 40%, with Japan topping the list with a whooping 86%.
As the degree of talent shortage varies between countries, it’s worth getting into talent pool analytics of your region for the positions you’re typically hiring for. You can create a talent density map to see where the people you’re looking for are based:
Another idea is to use LinkedIn search filters to specify the location you’re interested in. This comes in handy when you’re looking for software developers from your area or an area you would like to open an office in.
An example from the software development industry – a few years ago, Qualcomm needed to recruit research software engineers in the very competitive San Diego area. Following some in-depth talent pool analytics, they’ve found that Sydney, Australia offered an abundance of people with the skillset they were looking for. They eventually built an office there with the aim to house most of their research software engineers.
Another great location tip is to promote your employer branding communication in the location where the talent you need to grow is abundant. This way, they are familiar with your brand long before you even reach out for the first time.
You can also look for developers who may be willing to relocate, as described by Andrew Stetsenko, Founder of Relocateme.eu. This strategy is still not utilized by many tech recruiters, so you have a chance of finding “the one”.
One way is to run a simple search in LinkedIn like this one: “Java relocate” or “Java relocation”. The results you get this way are scarce but there’s a chance these people might be very open to discussion – they most likely need a change in their life. Some of them even specify the area of their interest in their description.
Source software developers from LinkedIn with InMail
Although top tech talent is now more visible than ever, it’s simultaneously getting harder to get these people to talk to you. How to start a conversation with InMail?
LinkedIn Talent Solutions came up with the 9 golden rules of InMail to help you get things moving in the right direction.
- Review candidate profile. Let them know what caught your attention – it’s flattering, plus it shows you’ve done your job.
- Grab attention. One way of doing that is to mention mutual connections, it often works wonders.
- Show you are selective. Tell people what makes them interesting to you and compliment them (don’t be cheesy though).
- Be conversational and brief. Write like a person and don’t just paste the job description in your message. People enjoy talking to other people – remember to stay human despite the iterative nature of InMail. You’re not a robot and let your messages show that.
- Listen. Ask people about their goals and respond to whatever clues you get from them. Relocation? More responsibilities? What’s the one thing that could make their life better? Identify their needs and see if you can help fulfill them.
- Focus on goals. Tell people what’s in it for them, otherwise you seem self-centered and desperate to fill an open position.
- Leverage content. Devs like data – use whitepapers, reports and other resources to illustrate your point.
- Be patient. Use status updates as a gentle reminder to stay in the mind of the candidate throughout the process.
- Add a call to action. Invite to discuss the subject, don’t give a yes/no option to apply right away.
Since we’re talking InMail, I’d like to throw in a couple of personal recommendations here:
- Understand what developers find interesting in a position so you know what you should focus on when you first talk to them. According to Stack Overflow research 60% of software engineers believe product details are most important part of the new position, and 59% claim they would like to know the compensation details when they first hear about the opportunity. Use that knowledge when you reach out.
Source: Stack Overflow Business
- Build a strong talent brand – people who engage with it are “2x more likely to accept your InMail”. Finally, don’t disregard company connections because they are “1.5x more likely to accept your InMail”.
- Relax and be yourself. Based on 2015 Stack Overflow Developer Landscape research, it appears that developers don’t really hate InMail as much as you think:
Source: Stack Overflow Business
Finding new candidates with content
LinkedIn Talent Solutions recommends using Status Updates to show thought leadership and expertise to your candidates, present you as a strategic partner and expand your reach. They also advise using Sponsored Content to raise brand awareness and get new leads.
You can use Sponsored Content to estimate what your target audience find interesting because they are data-rich:
Your own profile & careers page
Effective LinkedIn sourcing starts with an impeccable personal profile. According to LinkedIn resource “The Modern Recruiter’s Guide“, here’s what a good recruiter profile looks like:
When it comes to recruitment, a lot of emphasis is placed on having a bold headline. Here’s a handful of inspiration from LinkedIn:
There are a couple of ways to locate LinkedIn groups, but the easiest one is to run a simple search with the keyword of your interest and click “Groups”. I searched for “Python” and clicked “Groups” in the upper menu:
When you find the group, you click “Ask to join” and wait to be accepted.
You can also browse LinkedIn Groups Directory:
The best group tip is to “convert highly connected group-only connections to 1st degree connections” but be careful. Recruiters often abuse LinkedIn Groups so make sure you’re not one of these people developers actually hate.
Because Slideshare is a part of LinkedIn, each CV uploaded to LinkedIn is automatically uploaded to SlideShare, unless you tick a box saying “Don’t upload to SlideShare”. This is great news because it means that these CVs are available to you – you just need to know how to look for them.
You can do that by running a Google search as suggested by Stetsenko:
Stetsenko suggests you can order the search results by using the “Sorted by date” option.
He believes that “most precise results are achieved when the search is narrowed down by adding “intitle:resume” or “intitle:cv”. Granted, the results you get this way are scarce but they are definitely worth checking out because they are bottom of the pile.
Sourcing from LinkedIn can give you high hopes, but the number of returned InMails is often disappointing. Remember to use iterative search, think creatively and access Dark Matter results to source software developers from LinkedIn, otherwise you risk landing on the pile of unwanted developer outreach. Identifying “bottom of the pile candidates” is critical to finding the right developer. As you can see, some of the ideas I’ve suggested in this post may bring you scarce results, but these are the searches many of the recruiters are forgetting to complete, so these results are actually quite promising. The best thing you can do when you want to improve your sourcing skills is to follow great minds like Irina Shamaeva and Glen Cathey – their inquisitiveness and creativity really makes the life of tech recruiters much easier and more effective.
What are your favourite techniques to source software developers from LinkedIn? Let me know how you’re getting on!