Guide9 min readUpdated

What is Boolean search, and how do recruiters use it?

Short answer

Boolean search is a way to combine keywords with the operators AND, OR and NOT, plus quotation marks and parentheses, so a search engine returns exactly the profiles you describe. Recruiters use it on LinkedIn, in job boards, in their ATS and on Google to find candidates by title, skill, location and exclusions.

A white panel of switches, two of them orange.

What does Boolean search mean in recruitment?

Boolean search means you describe the candidate you want as a logical formula instead of a loose set of words. The name comes from George Boole, the mathematician behind the true/false logic that search engines still use. A plain search for "java developer amsterdam" leaves it to the search engine to guess what matters. A Boolean string tells it: the title must be one of these variants, this skill must appear, these profiles must be left out.

For recruiters, that precision decides whether a search returns 40 useful profiles or 4,000 mixed ones. It also makes a search repeatable: a colleague can run the same string next month and understand why each result appeared. That is why Boolean search is still part of almost every sourcing training, even as more of the searching itself is done by software.

Where you can use a Boolean string

Most tools recruiters touch accept at least part of the syntax: LinkedIn search and LinkedIn Recruiter, job boards and CV databases, many applicant tracking systems and CRMs, and Google or Bing for X-ray searches. The details differ per tool, so a string that works in one place can silently fail in another. The sections below cover the rules per platform.

Which Boolean operators should every recruiter know?

Five building blocks cover nearly every search. Write operators in capitals: several platforms, LinkedIn included, only recognise them that way.

Operator
What it does
Recruitment example
Effect on results
AND
All terms must appear
"account manager" AND SaaS
Fewer, more specific results
OR
At least one of the terms must appear
(developer OR engineer OR programmer)
More results; use for synonyms and title variants
NOT
Leaves out results containing the term
recruiter NOT (intern OR student)
Fewer results; removes noise
" "
Exact phrase in this word order
"registered nurse"
Stops the engine from splitting a title
( )
Groups terms so the logic runs in the right order
(nurse OR verpleegkundige) AND ICU
Prevents OR from swallowing the rest of the string

Wildcards (an asterisk to catch develop, developer and development at once) work in some job boards and ATS searches, but LinkedIn states it does not support them. Check each tool before relying on a wildcard.

How do you build a Boolean search string step by step?

Start from the vacancy, not from the operators. A good string is a translation of three questions: what is this person called, what can they demonstrably do, and who do you not want to see. Everything else is filtering you can often do better with location, industry or seniority filters in the tool itself.

  • 1. List the title variants. Collect every name the role goes by, including older titles and the local language: ("software engineer" OR "software developer" OR "backend developer" OR ontwikkelaar).
  • 2. Add one or two must-have skills with AND. Pick the requirements that truly disqualify, not the whole wish list: AND (Python OR Django).
  • 3. Remove predictable noise with NOT. Recruiters, students and vendors often mention the same keywords: NOT (recruiter OR "talent acquisition" OR intern).
  • 4. Test and read the first 20 results. If more than a few are wrong, find the word that let them in and adjust.
  • 5. Save the string with a note. Write down what you excluded and why, so the next search on a similar vacancy starts from something that worked.

Why brackets matter more than people think

Without brackets, a string like "Java OR Kotlin AND Android" is read in the order the platform chooses. LinkedIn documents its order of precedence: quoted phrases first, then parentheses, then NOT, then AND, then OR. That means an unbracketed OR is evaluated last and can pull in every Java profile, Android or not. Writing "(Java OR Kotlin) AND Android" removes the ambiguity everywhere.

What does LinkedIn support, in free search and in Recruiter?

Both LinkedIn's free search and LinkedIn Recruiter accept AND, OR, NOT, quotation marks and parentheses, but they handle them differently. According to LinkedIn Help, the free search bar on LinkedIn.com accepts a Boolean string directly; operators must be in capitals, and braces, square brackets, angle brackets and asterisk wildcards are not supported. Plus and minus signs are not officially supported either. Stop words such as "by", "in" and "with" are ignored.

In Recruiter and Recruiter Lite, Boolean works in more places. LinkedIn lists job titles, location, companies, skills and assessments, schools, industries and spoken languages as filters that are treated as Boolean, with keywords and projects supporting modifiers as well. LinkedIn also warns that too many facets in one Boolean query can cause problems and recommends moving long strings into the individual filters. In practice: put titles in the title filter, companies in the company filter, and keep the keyword field for skills and exclusions.

Practical LinkedIn rules that save time

Write NOT, AND and OR in capitals. Use straight quotation marks, not the curly ones that phones and word processors insert. Do not rely on the asterisk. Test a long string by removing one block at a time: if the result count jumps, that block was doing the filtering. If you are weighing whether a Recruiter seat is worth it for this kind of searching, our guide on LinkedIn Recruiter cost sets out what you pay for.

What is X-ray search and how do you run one on Google?

X-ray search uses a web search engine to look inside one website, usually LinkedIn, GitHub or a professional register. You combine Boolean logic with the site: operator so Google only returns pages from that domain. Google's own help documents site:, exact-match quotes, the minus sign for exclusion and filetype:, and notes that there must be no space between the operator and the term.

X-ray is useful when you have no Recruiter seat, when you want to search public profiles on sites without a good internal search, or when you look for CVs and portfolios published as files. It has limits: you only see what the search engine has indexed, results are not complete, and snippets can be outdated. Treat X-ray as a way to discover names and signals, then check the live profile.

  • LinkedIn profiles: site:linkedin.com/in ("data engineer" OR "analytics engineer") (Utrecht OR Amersfoort) -recruiter
  • GitHub users: site:github.com "Rotterdam" (Rust OR Go) "followers"
  • CVs as documents: (cv OR resume OR "curriculum vitae") "process engineer" filetype:pdf -template
  • Conference speakers: ("speaker" OR "spreker") "platform engineering" 2026 site:nl

A note on OR and the minus sign in Google

Google's operator page lists the minus sign for exclusion, not the word NOT, so use "-recruiter" rather than "NOT recruiter" in X-ray strings. OR in capitals is widely used in X-ray searches but is not on that page, so check whether your results actually broaden. Collecting profiles in bulk from search results raises both platform terms and privacy questions; our guide to GDPR and candidate sourcing explains what to keep in mind.

Which Boolean search strings work for common roles?

Use these as starting points and adapt titles to your market and language. They are written for a keyword field; in LinkedIn Recruiter, move the title block into the title filter.

Software and data

  • Backend developer: ("backend developer" OR "back-end developer" OR "software engineer") AND (Java OR Kotlin) AND (Spring OR microservices) NOT (recruiter OR intern OR student)
  • Data engineer: ("data engineer" OR "analytics engineer" OR "big data engineer") AND (Spark OR dbt OR Airflow) AND (SQL OR Python)
  • DevOps: (DevOps OR SRE OR "site reliability" OR "platform engineer") AND (Kubernetes OR Terraform) NOT (sales OR "account executive")

Healthcare

  • ICU nurse: ("registered nurse" OR "IC-verpleegkundige" OR "intensive care nurse" OR verpleegkundige) AND (ICU OR "intensive care" OR IC) NOT (student OR leerling)
  • Physician assistant: ("physician assistant" OR "PA" OR "verpleegkundig specialist") AND (orthopedie OR orthopaedics)

Engineering, technical and trades

  • Service engineer: ("service engineer" OR "field engineer" OR "servicemonteur" OR "storingsmonteur") AND (PLC OR hydraulics OR hydrauliek)
  • Electrician: (elektricien OR "elektrotechnisch monteur" OR electrician) AND (NEN3140 OR "industriële automatisering")
  • Process engineer: ("process engineer" OR procestechnoloog) AND (food OR dairy OR voedingsmiddelen) NOT (student OR stagiair)

Sales, finance and logistics

  • SaaS account executive: ("account executive" OR "account manager" OR "new business") AND (SaaS OR software) AND (B2B) NOT (recruitment OR staffing)
  • Controller: (controller OR "business controller" OR "financial controller") AND (IFRS OR consolidatie OR consolidation) AND (SAP OR Exact)
  • Planner: (planner OR "transport planner" OR "logistiek planner") AND (TMS OR "warehouse management") NOT (event OR wedding)

Build your own string

Enter title variants, must-have skills and exclusions. The generator adds brackets and quotation marks for you. For more options, open the full Boolean search generator.

Fill in at least one job title.

What are the most common Boolean search mistakes?

Most failed searches come down to a handful of errors. They are easy to fix once you know where to look.

  • Too many ANDs. Every extra requirement removes people who have the skill but did not write it down. Keep AND for real knock-out criteria.
  • Missing title variants. The same job is called developer, engineer, programmer, ontwikkelaar or consultant depending on the employer. If you search one title, you see one slice of the market.
  • OR without brackets. It changes the logic of the entire string, often without any error message.
  • Curly quotation marks. Copied from a document or phone, they can break exact-phrase matching.
  • Lowercase operators. On LinkedIn, lowercase "and" and "not" are treated as stop words rather than operators.
  • Excluding too broadly. "NOT manager" also removes the senior engineer who once managed a team of two.
  • Never revisiting a string. Titles and tools change. A string that worked two years ago misses today's names for the same role.

Where does Boolean search stop and AI sourcing begin?

Boolean search finds the words in a profile; it cannot judge what they mean. It does not know that a "medior developer" at a scale-up may have more relevant experience than a "senior developer" elsewhere, or that a candidate without the keyword still fits because of their career path. AI sourcing works from the full vacancy instead of a string: it runs several search routes, reads profiles in context and ranks candidates with reasons.

  • One string equals one search route; an agent runs several in parallel
  • Keyword match versus fit on the complete vacancy, with missing requirements named
  • Your approval rules decide where a recruiter checks the strategy and the selection
See how AI candidate sourcing works
An orange beam of light passing through a row of white and black rings.

Is Boolean search still worth learning?

Yes. Even when software does most of the searching, Boolean logic is how you check it. A recruiter who can write a clean string can read an AI search strategy, spot a missing title variant and explain to a hiring manager why the market is small. It is also the fastest way to answer a quick question such as "how many ICU nurses within 30 kilometres mention night shifts?"

Writing, testing and rerunning strings for every vacancy, then reading every result, is the part that scales badly. In AIcruiters, the agent turns the vacancy into a search strategy with title variants, skills and career paths, runs it across available talent sources and ranks the results, while your team approves the strategy where you want a check. See how the platform works or compare AI sourcing with manual sourcing.

Boolean search: frequently asked questions

Does LinkedIn support Boolean search without Recruiter?

Yes. According to LinkedIn Help, you can type a Boolean string in the main search bar on LinkedIn.com using AND, OR, NOT, quotation marks and parentheses. Recruiter and Recruiter Lite apply Boolean logic in more filters, such as job titles, companies and skills.

Can I use wildcards like an asterisk on LinkedIn?

No. LinkedIn states that wildcards such as the asterisk are not supported, and neither are braces, square brackets or angle brackets. Write out the variants instead, for example (developer OR development).

What is the difference between Boolean search and X-ray search?

Boolean search is the logic: operators, quotes and brackets. X-ray search applies that logic in Google or Bing combined with the site: operator to search within one website, such as LinkedIn profiles or GitHub.

Why does my Boolean string return zero results?

Usually one of four reasons: too many AND conditions, a typo in an exact phrase, curly instead of straight quotation marks, or an OR block without brackets. Remove blocks one at a time until results return, then rebuild.

Is Boolean search the same as AI sourcing?

No. Boolean search matches keywords you choose. AI sourcing starts from the vacancy, runs several search routes and ranks candidates on their fit with the full set of requirements. Recruiters still use Boolean logic to check and steer the result.

Last updated:

Stop rewriting strings for every vacancy

See how AIcruiters turns one of your own vacancies into a search strategy and a ranked shortlist, in a 30-minute demo.

Book a demo on your own vacancy30 minutes · your vacancy · your numbersCalculate your business case