Boolean search for recruiting
Boolean search is a way to query a candidate database with AND, OR, and NOT so you only see people who match a role. It is still useful. It is also slow, easy to get wrong, and a poor fit once the search has to account for messy job titles.
The operators that matter
AND requires every term. OR accepts any term in the group. NOT, or a minus sign on some sites, drops a term. Quotes lock a phrase, so "staff software engineer" does not also match a staff accountant who once used the word engineer. Parentheses control which OR group the AND applies to.
Most recruiting databases, including LinkedIn Recruiter, use this grammar. A few add site-specific fields such as title:, company:, or location. Those field names are not portable. A string that works in one tool often returns nothing in another.
A string for a backend role
Start from the work, not from a single job title. People who can build backend systems call themselves software engineer, backend engineer, server engineer, or just engineer. Exclude the titles that pollute the search.
- ("backend engineer" OR "back end engineer" OR "server engineer" OR "software engineer") AND (Go OR Golang OR Python) NOT (intern OR recruiter OR "engineering manager")
- Add a location or a company filter only after the skill string returns a sensible set. Tightening location first hides strong people who will move.
- Read the first twenty profiles. If half of them are the wrong craft, the OR group is too wide. If you only see one company, the AND group is too narrow.
Where boolean search wastes a week
Titles drift. A founding engineer, a member of technical staff, and a software engineer can be the same person at three companies. Boolean search treats those as different queries, so you maintain a pile of strings and still miss people.
It also does not tell you who is worth contacting. A match on "Python" can be a data analyst, a bootcamp project, or someone who last wrote Python in 2016. You still open profiles one by one. On a startup team, that review is usually the founder’s evening.
When to stop writing strings
Use boolean search when you already know the exact skill and the database is small enough to review. Switch when the role is senior, the titles are inconsistent, or you need someone to do the first pass. An AI sourcer can read the role in plain language, look past title noise, and bring back a short list with a reason for each person.
Ava does that inside Slack. You describe the role, she returns people who fit, and you approve who she contacts. The boolean string is still there if you want to inspect a search. It is no longer the job.
Common questions
- What is boolean search in recruiting?
- It is a query made of AND, OR, and NOT that filters a candidate database down to people who match the terms you care about.
- Does boolean search still work on LinkedIn?
- Yes. LinkedIn Recruiter still accepts boolean strings. Results depend on how complete each profile is, and on whether your title list matches how people actually describe themselves.
- What should I use instead of a long boolean string?
- Describe the role in plain language and let a sourcer rank people against that description. Keep boolean search for narrow lookups inside a database you already trust.