Boolean Search for Recruiters: Operators, Strings, and Examples

Boolean search is a way to find candidates by combining keywords with AND, OR, and NOT to include, widen, or exclude search results.

It gives you exact control over who shows up in your search. You decide which skills are required, which job titles count as a match, and which profiles to skip.

Boolean search operators

Boolean search uses three operators and three modifiers, and each one changes your results in a set way.

Source: Illinois library guide

OR does most of the heavy lifting in recruiting. MIT's library guide describes it as the way to connect synonyms and broaden results. People describe the same job in many ways, so your OR groups decide how much of the market you see.

Quotation marks matter just as much as the operators themselves. Without them, a search for project manager can match someone who managed a warehouse and once joined a project.

How to build a Boolean search string from the job requirements

Take notes during intake (the kickoff call where the hiring manager or client explains the role). To build your search, start with your intake notes and sort every requirement into one of four buckets.

1. Must-haves: Each one becomes its own group, joined to the others by AND. Keep it to two to four groups, because every AND removes people.
2. Synonyms: Inside each group, list alternate titles, spellings, and skill names joined by OR.
3. Deal-breakers: Add NOT only for terms that clearly mark a wrong fit, such as student or intern.
4. Nice-to-haves: Leave them out of the string. Use them to rank the shortlist when you review results.

Order matters once you mix operators in the same string. MIT's guide explains that databases often treat AND as the primary operator and connect those terms first. So wrap every OR group in parentheses.

nurse OR RN AND pediatric

This can return any profile that mentions "nurse" at all, pediatric or not.

(nurse OR RN) AND pediatric

The parentheses make the search treat nurse and RN as one group, then require pediatric.

Here's how the buckets turn into a string:

Say a client needs a bilingual customer service team lead who speaks Spanish and has run a team before.

("customer service" OR "customer support" OR "call center") AND (supervisor OR "team lead" OR manager) AND (Spanish OR bilingual)

Each must-have is one group, and each group lists the words candidates use for it.

If the client also wants help desk software experience but would hire without it, keep it out of the string. You'll use it later to sort the people you find, rather than losing strong leads who never listed it.

Boolean search examples

Each string below follows the same pattern: a title group, one or two skill groups, and sometimes a NOT for common noise. Swap in the titles and skills that people in your market use on their profiles.

Registered nurse in intensive care

("registered nurse" OR RN) AND (ICU OR "intensive care" OR "critical care") NOT student

The title group catches both the full title and the RN short form, and NOT drops nursing students.

Account executive

("account executive" OR "account manager" OR "sales executive") AND (SaaS OR software) AND quota

Adding quota finds people who carried a sales target, not just people with a sales title.

Staff accountant

("staff accountant" OR "general ledger accountant") AND (reconcil* OR "month-end close")

The asterisk catches reconcile, reconciled, and reconciliation with one term.

Backend developer

("backend developer" OR "back-end engineer" OR "software engineer") AND (Python OR Java) AND API NOT intern

Three title variants widen the pool, and the skill groups keep it on target.

Check what your string gets wrong

Run the string, scan the first page of results, and change one group at a time.

• Too many results: add an AND group for another must-have, or a NOT for the most common wrong match.
• Too few results: add OR synonyms, drop the weakest must-have, or use an asterisk to catch word endings.
• Wrong kind of profile: check that every OR group sits inside parentheses.
• Zero results: look for a missing quotation mark or bracket.

Change only one thing per run, and note what happened to the result count. If you change three groups at once, you won't know which change fixed the results.

A string that looks right can still hide good people behind a title you didn't think of.

Where to run Boolean searches

You can run a string almost anywhere you search for people, but each platform reads it a little differently.

• Your applicant tracking system (ATS): The software that stores past applicants. Search it first, since those people already know your company or client.
• AI sourcing tools: Tools such as Rotto turn a plain-language description of the role into a search, so you can skip writing the string. Keep your Boolean version anyway and run it elsewhere to spot-check what the tool returns.
• Job board resume databases: Good for active candidates who posted a resume.
• LinkedIn: Search people by title, skill, and keyword.
• Google: Good for public pages such as portfolios and member directories.

SNHU's library FAQ notes that not every database handles Boolean operators the same way. Some support nesting, and some accept symbols like "&". Check each platform's help page before you paste a string you built somewhere else.

Boolean vs plain-language search: what to use before you start

Use Boolean when you need exact control, and plain-language search when you'd rather describe the role and let a tool build the query.

• Choose Boolean when you need to see every rule, repeat a search next month, or explain to a client why someone was included.
• Choose plain-language search when the role has many title variants, you're short on time, or you keep losing results to a stray bracket.

You don't have to pick one. Start with a plain-language brief to see who's out there, then tighten the results with a string you control. Boolean search for recruiters stays useful either way, because it lets you check what any tool returns.