Boolean Search for Recruiters:Operators, Strings, and Real Examples
The difference between a recruiter who finds 8 qualified candidates and one who finds 80 is usually one thing: how well they write a search string. Boolean is the cheapest sourcing skill you can learn, and it pays off on every single requisition.
Most candidate databases hold far more qualified people than you will ever surface with a plain keyword search. Type "software engineer" into LinkedIn and you get millions of profiles ranked by an algorithm you do not control. Write a tight Boolean string and you get a filtered list of people who actually match the role, in the order you decide. That control is the whole point.
Boolean search is named after George Boole, the 19th-century mathematician whose logic underpins every search engine and database built since. You combine keywords with three operators, AND, OR, and NOT, plus quotes and parentheses, to tell the engine exactly what you want. The same syntax works across LinkedIn, Google, Google's search operators, GitHub, and nearly every applicant tracking system. Learn it once and it travels with you.
The reason it still matters in 2026: sourcing is the highest-impact part of recruiting. The LinkedIn Talent Blog has reported for years that the best candidates are passive, not actively applying, which means you have to go find them. A good Boolean string is how you reach the people who never see your job post. It pairs naturally with the rest of your candidate sourcing workflow and your passive candidate strategy.
This guide covers the operators, gives you copy-paste strings for real roles, walks through Google X-ray search, and lists the mistakes that quietly tank your results. Whether you run 30 searches a week or you are filling your first technical role, the structure here will get you to better candidates faster.
The Building Blocks
The six operators that do all the work
You do not need to memorize a manual. Boolean search runs on six symbols. Three of them, AND, OR, and NOT, are the logic. The other three, quotes, parentheses, and the wildcard, control how the engine reads your terms. Get comfortable with these and you can build a string for any role.
Both terms must appear
python AND djangoProfiles mentioning both Python and Django
Either term can appear
("product manager" OR "product owner")Widens the net across job-title variations
Exclude a term
developer NOT recruiterDrops sourcers and agency profiles
Match an exact phrase
"machine learning engineer"Keeps the words together, in order
Group terms together
(java OR kotlin) AND androidControls the logic order, like in math
Wildcard for word endings
engineer* Catches engineer, engineering, engineered
AND narrows, OR widens, NOT excludes. That sentence is most of what you need to remember. Every AND you add shrinks your result set, because both terms now have to be present. Every OR grows it, because either term qualifies. NOT carves out the noise you do not want, like agency recruiters or students.
Quotes keep phrases intact. Without them, "product manager" searches for any profile containing "product" and "manager" anywhere, including a product designer who manages a dog-walking side business. With quotes, you get the exact title. Use them on every multi-word skill or role.
Parentheses control the order of logic. Search engines read Boolean the way you read arithmetic: what is inside the brackets gets evaluated first. So (java OR kotlin) AND android finds Android developers who know either language, while leaving out the parentheses produces a mess the engine resolves in ways you did not intend. When in doubt, add brackets.
The Method
Build every string in four layers
The recruiters who write good strings fast are not improvising. They follow the same structure every time and just swap the contents. Think of it as four layers stacked from broadest to most specific. Write each layer on its own, then stitch them together with AND.
("software engineer" OR "backend developer" OR "swe")AND (go OR golang) AND (kubernetes OR k8s)AND ("distributed systems" OR microservices)NOT (recruiter OR "looking for" OR student OR intern)Stitched together
("software engineer" OR "backend developer" OR "swe") AND (go OR golang) AND (kubernetes OR k8s) AND ("distributed systems" OR microservices) NOT (recruiter OR student OR intern)Layer one, titles. Start with every title that describes the role, not just the one on the job description. A backend engineer might list themselves as "software engineer", "backend developer", "SWE", or "server-side engineer". Miss the synonyms and you miss the people. This is the single most common reason a search comes back thin.
Layer two, must-have skills. These are your non-negotiables, joined with AND. Keep this list short. Two or three genuine must-haves is usually right. If you list six, you are describing a person who does not exist, and the search will prove it by returning nothing.
Layer three, nice-to-haves. Group these in an OR set so a profile matching any one of them still surfaces. This is where you add the signals that separate a strong match from a perfect one without forcing every box to be checked.
Layer four, exclusions. Strip out the predictable noise with NOT: recruiters, students, interns, "looking for" (a sign of an active job seeker posting, not a profile). A clean exclusion layer can cut a result set in half without losing a single real candidate. From there, log the string in your applicant tracking system so you can reuse it on the next req.
Copy and Paste
Five strings you can use today
These work in the LinkedIn keyword field and, with a site: prefix, in Google. Swap the skills and locations for your role. Treat them as starting points, then tighten or loosen based on what comes back.
Senior backend engineer (Go)
("software engineer" OR "backend developer" OR "swe") AND (go OR golang) AND (kubernetes OR k8s OR docker) NOT (recruiter OR intern OR student)Product manager, B2B SaaS
("product manager" OR "product owner" OR "head of product") AND (saas OR b2b OR "enterprise software") AND (roadmap OR "product strategy") NOT (recruiter OR "product marketing")Data scientist with ML
("data scientist" OR "machine learning engineer" OR "ml engineer") AND python AND (pytorch OR tensorflow OR "scikit-learn") NOT (student OR "looking for")Senior product designer
("product designer" OR "ux designer" OR "ui/ux") AND (figma OR sketch) AND ("design systems" OR prototyping) NOT (graphic OR freelance OR student)Account executive, mid-market
("account executive" OR "sales executive" OR "ae") AND (saas OR b2b) AND (quota OR "closed won" OR "net new") NOT (recruiter OR "sales development" OR sdr)Beyond the Platform
Google X-ray search: reach profiles others miss
LinkedIn limits how many profiles a free account can view and caps the operators in a single search. X-ray search sidesteps both. Instead of using LinkedIn's own search bar, you point Google at LinkedIn with the site: operator and apply Google's full Boolean syntax. The same trick works on GitHub, Stack Overflow, and anywhere candidates leave a public profile.
site:linkedin.com/insite:linkedin.com/in ("data scientist") AND python AND (pytorch OR tensorflow) "San Francisco"site:github.comsite:github.com "react" "typescript" location "Berlin"site:stackoverflow.com/userssite:stackoverflow.com/users (rust OR "systems programming")intitle:resume OR inurl:cv(intitle:resume OR inurl:cv) "ux designer" (figma OR sketch) -job -applyThe pattern is always the same: start with site:domain, then add your Boolean string. For LinkedIn, use site:linkedin.com/in to target individual profile pages rather than company pages or job posts. One note on Google syntax: it uses a minus sign instead of NOT, so -recruiter excludes the word the same way NOT does inside LinkedIn.
X-ray has real limits. You only see public profiles, the snippets Google indexes can be stale, and you lose LinkedIn's structured filters for things like current company or years of experience. Treat it as a complement to native search, not a replacement. The recruiters who get the most out of it run both and cross-reference. For the wider toolkit, see our roundup of the best sourcing tools for recruiters.
What Goes Wrong
The mistakes that quietly ruin your results
A bad Boolean string rarely throws an error. It just returns the wrong people, or nobody at all, and you assume the talent is not there. Here is what separates a string that works from one that wastes your afternoon.
- Group every OR list inside parentheses
- Quote multi-word titles and skills
- Add synonyms and abbreviations (k8s, ML, SWE)
- Test with two terms, then layer in more
- Keep a saved library of strings per role
- Use NOT to strip out recruiters and students
- Stacking 12 ANDs until zero results return
- Forgetting that LinkedIn caps OR at ~50 terms
- Searching only for the exact title on the JD
- Mixing operators without parentheses
- Excluding so aggressively you lose good profiles
- Treating one perfect string as the whole job
The number-one killer is over-stacking AND conditions. A recruiter reads a job description with eight requirements and faithfully turns all eight into AND clauses. The result returns zero profiles, because no single human checks all eight boxes on their public profile. Start with the two or three skills that genuinely matter and add from there.
The second killer is the missing parenthesis. Search engines do not ask what you meant; they evaluate exactly what you typed. An OR group without brackets gets misread, and you end up with results that look random. When a string behaves strangely, check your parentheses first. It is almost always that.
Where This Is Heading
Boolean in an age of AI sourcing
The honest answer about AI and Boolean: the workflow is changing, the underlying skill is not going away. Newer sourcing tools, Prepzo included, let you describe a candidate in plain English, "senior Go engineer in Berlin who has worked on payments", and they translate that into the operator logic behind the scenes. For routine searches this is genuinely faster than hand-writing a string.
But the recruiter who understands Boolean still has the edge. When an AI tool surfaces a strange shortlist, you can read why, because you understand the logic underneath. When it misses an obvious synonym, you can correct it. The skill becomes less about typing every string by hand and more about knowing what good filtering looks like, which is a judgment AI cannot fully replace yet.
My view: learn Boolean properly, then let tools handle the repetitive part. That combination beats either approach on its own. The same thinking applies across the rest of your stack, which is why we wrote about recruitment automation and the AI recruiting tools worth knowing.
Frequently Asked Questions
What is Boolean search in recruiting?
Boolean search is a way to query databases and search engines using logic operators like AND, OR, and NOT to combine or exclude keywords. Recruiters use it to filter large candidate pools down to people who match specific skills, titles, and locations. The name comes from George Boole, the mathematician who formalized this logic in the 1850s. In sourcing, it turns a vague keyword search into a precise filter.
Do the Boolean operators have to be in capital letters?
Yes, on most platforms. LinkedIn, Google, and the major job boards require AND, OR, and NOT to be uppercase so the engine reads them as operators rather than ordinary words. If you type a lowercase 'and', it gets treated as a search term. Quotation marks and parentheses work the same regardless of case.
Does Boolean search still work on LinkedIn?
It does, with limits. LinkedIn supports AND, OR, NOT, quotes, and parentheses in the keyword field on both the free search and Recruiter. The catch is that LinkedIn caps the number of operators in a single string, roughly 50 OR terms, and it no longer applies Boolean to the title or company filters the way it once did. For deeper reach, recruiters pair LinkedIn Boolean with Google X-ray search.
What is X-ray search?
X-ray search uses Google's site: operator to search inside a specific website, like site:linkedin.com/in, instead of using that site's own search bar. It lets you apply Google's full Boolean syntax to LinkedIn, GitHub, or Stack Overflow profiles, often surfacing people you would not see through the platform's native filters. It is the most common workaround for free accounts and search-credit limits.
Why does my Boolean string return zero results?
Almost always because you chained too many AND conditions. Each AND narrows the pool, so five required skills plus a title plus a location can shrink a 10,000-person result to nothing. Start with two terms, confirm you get results, then add one condition at a time. Missing parentheses around OR groups is the other common cause, since the engine then misreads your logic.
Is Boolean search being replaced by AI sourcing tools?
AI sourcing is changing the workflow, not erasing the skill. Natural-language tools let you describe a candidate in plain English and handle the operator logic for you, which is faster for routine searches. But understanding Boolean still matters when you need to audit why a tool surfaced someone, or refine a search the AI got wrong. My view is that the recruiters who know both will outperform the ones who only know one.
Resources & Further Reading
Related Guides
- What Is Candidate Sourcing? A Practical Guide
Where Boolean search fits in the sourcing process
- How to Source Passive Candidates
Reaching the people who never apply to your posts
- Best Sourcing Tools for Recruiters
The toolkit that pairs with a good search string
- How to Build a Talent Pipeline
Turn one-off searches into a repeatable pipeline
External Sources
- Google Search Operators Reference
The official list of operators for X-ray search
- LinkedIn Talent Blog
Research on passive candidates and sourcing
- SHRM Talent Acquisition
HR research on hiring and recruiting practices
- Bureau of Labor Statistics
Occupational data to size your candidate market
Source candidates without writing a single string
Prepzo turns a plain-English description into a ranked shortlist, then runs the screening for you. Describe who you want and let the AI find them. 14-day free trial.
Try Prepzo free