One of the things that has always struck me as extremely odd with regard to sourcing is the fact that there appears to be so little sharing of Boolean search strings.
While one can find basic search string examples in training materials and in various sourcing groups online, I know plenty of sourcers and recruiters that have never seen another person’s production search strings – those used to actually fill positions.
Why do you think that is? I have my ideas, and I’d like to know yours.
I believe there may be several contributing factors:
- Some people just don’t save their searches. If I were a betting man, from what I’ve seen over the past 15+ years, I’d wager that the majority of people don’t save their search strings. If they’re not saved anywhere – you severely limit any sharing opportunities to live, in-the-moment situations that may or may not ever present themselves.
- It simply never occurs to some people to share their searches with others – unless someone specifically asks, why would someone?
- Plain old insecurity. Some folks might not want to share their search strings with others because they are afraid theirs are somehow “wrong,” inferior or inadequate.
- The belief that their Boolean search strings are somehow their “secret sauce” and that in sharing their searches might somehow expose their competitive advantage.
What do you think?
How Would You Search for these Positions on LinkedIn?
Are you up to the challenge of sharing some of your searches with a global audience of talent acquisition professionals? I will be performing a hat trick this year at LinkedIn’s Talent Connect event in Las Vegas– I’ve been asked back to present for the third time on how to effectively source potential candidates on LinkedIn.
During these sessions I show examples of my own searches. This year, in addition to my searches, I’d like to provide a number of examples from the global sourcing community. I believe there is much to learn from sharing search strings – it’s very similar to sharing recipes.
Provided there are no syntax errors, search strings are not “right” or “wrong,” and there is no single “best” search string, just as there is no single best recipe for anything.
Remember – all searches “work.” As long as you are pleased with the quality and the quantity of the results, your search is sound – so don’t be nervous, be confident!
If you’re game, take a look at the 4 jobs below that I mashed up from some random Indeed searches and comment on this blog post with a search for one or more of the positions. You don’t have to have any experience in sourcing for similar roles – so don’t let them intimidate you if you are unfamiliar with the positions.
I’d argue that when it comes to sourcing, you don’t have to have any prior experience with a specific role to be effective in sourcing for it, but that’s a whole blog post in and of itself.
Here are some basic guidelines to participate:
- I’m looking for the search criteria you would use if you were searching LinkedIn using LinkedIn’s search interface – not X-Ray searching via Google or Bing
- If it’s material to your searches, specify whether your searches are for the free version of LinkedIn or one of the premium versions
- Specify the fields and facets you’re leveraging (e.g., keywords, title & company [current and past, current, past, past not current], company, industry, groups, etc.)
- For the purpose of this exercise, location is irrelevant, so there is no need to specify
If you’re a shy sourcer and would rather not take credit for your work and let the world know who you are – that’s 100% cool with me. I understand why some of you might not want to identify yourself. You are totally free to leave your searches anonymously.
On the other hand, if you’re particularly proud of your searches, let me know – I’d be happy to give you credit if I used one of your searches during my presentations. Maybe your manager or even you will be in the audience when I share it – how cool would that be?
Position #1 Loan Processor
- Reading and reviewing financial documents in order to make sound financial decisions
- Working directly with underwriters and loan officers to understand the financial picture of the customer
- Working with FHA/VA and Conventional loans
- Interacting with loan officers to coordinate the approval process and make it as efficient as possible
- 1-2 years of recent loan processing experience
- Track record of success in working with FHA, VA and Conventional Loans
Position #2 Substation Engineer
The Substation Engineer will be required to provide design, specifications and construction documents. The position requires a strong interest in power systems and design of electrical high voltage substations. Primary Responsibilities
- Perform electrical design and calculations for various electrical power, communication and control systems involved with electrical substation projects
- Gather all pertinent information of projects and document scope of each project and prepare material lists, plan, elevation and detail drawings for substation projects
- Bachelor’s degree in Electrical Engineering with emphasis in Power Systems
- Minimum 4 years of substation design experience
- Professional PE registration is preferred
- Knowledge of National Electrical Safety Code (NESC) is required and knowledge of Rural Utility Service (RUS) requirements desired
Position #3 User Interface Designer
Position #4 C# Developer
- Develop new applications and convert legacy applications from MS Access to C# winforms & web services.
- Ongoing development, maintenance, and support of the above-mentioned application once the initial version is deployed.
- Maintenance and support of several existing C# winforms, Windows service, and command-line applications.
Requirements 5-8 years of experience with the following technologies is required:
- C# winforms & web services development using Visual Studio
- Interacting with external web services and performing data manipulation
- Information storage and retrieval with Microsoft SQL Server
- Microsoft Access w/ Visual Basic for Applications (needed for porting functionality from a legacy applications)
Let the Search String Sharing Begin!
As I write this, my spider sense is telling me I probably won’t get that many searches in response to this post.
If I don’t, I’d bet that it would be primarily due to reasons #3 and #4 I listed at the beginning (insecurity or “secret sauce,” respectively).
However, I’ve tried to address both of those concerns – if you’re on the fence on whether or not you might throw your search strings in the ring, remember you can post them anonymously, and you can choose not to create searches for any of the 4 positions you routinely source for if you feel it will somehow betray your competitive advantage.
Care to share?