Boolean Search for Recruiters: The Complete Guide (With 10+ Ready-to-Use Strings)

Boolean search is one of those skills where the gap between "I know it exists" and "I actually use it well" separates good sourcers from great ones. The operators themselves take about ten minutes to learn. The craft is in knowing when and how to combine them — and that's what this guide covers.

By the end you'll have the fundamentals, the advanced tricks, and more than ten ready-to-copy search strings for the roles you're probably searching for right now.

What Boolean Search Actually Is

Boolean logic was formalised by mathematician George Boole in the 1840s, but it's been a recruiter's best friend since the early days of online CV databases. At its core, it's a method of combining keywords using logical operators to produce precise search results — rather than relying on a platform's algorithm to guess what you mean.

Why does it matter? Because algorithms lie. LinkedIn's default relevance ranking, for example, is influenced by sponsored content, premium accounts, and engagement patterns — not purely skills match. Boolean search cuts through that noise and returns results based purely on what you've specified.

The five operators you need to know:

The Five Core Boolean Operators

AND

Narrows results. Both terms must appear in the result.

Java AND "machine learning" — returns profiles that include both Java and machine learning. Useful when you need multiple skills confirmed. Most platforms assume AND between terms anyway, but making it explicit avoids ambiguity.

OR

Broadens results. Either term can appear. This is the operator most recruiters underuse.

CFO OR "Chief Financial Officer" OR "Finance Director" — essential for role titles, which vary wildly across companies and countries. In Germany, "Kaufmännischer Leiter" is the equivalent of Finance Director — without OR, you'll miss half the candidates.

NOT

Excludes terms. Critically useful for cutting out noise.

recruiter NOT "talent acquisition" NOT HR — if you're building a pool of agency-side recruiters, this removes in-house HR and TA professionals from results. In LinkedIn, NOT is written as a minus sign: recruiter -"talent acquisition".

Quotation Marks

Exact phrase matching. Without quotes, search engines treat each word independently.

"executive search" returns only that exact phrase. executive search without quotes might return "executive who does search engine marketing" — a very different person.

Parentheses

Groups operators, exactly like maths brackets. This is where boolean gets powerful.

(CFO OR "Finance Director" OR "VP Finance") AND (SaaS OR "software" OR "technology") NOT "interim"

Without parentheses, that string would be interpreted in a completely different order and produce garbage results. Parentheses tell the engine exactly which ORs to evaluate first.

The site: Operator for Google X-Ray Sourcing

This one deserves its own section because it's dramatically underused. The site: operator in Google lets you search within a specific website — including LinkedIn, which has its own search limitations on free accounts.

Basic structure: site:linkedin.com/in/ [your boolean string]

Example: site:linkedin.com/in/ "software engineer" "Berlin" (Python OR Django) -recruiter

This surfaces LinkedIn profiles that contain those terms, pulled directly from Google's index — bypassing LinkedIn's commercial search limits. It's not perfect (Google's index of LinkedIn is incomplete and not real-time), but it's a legitimate free alternative when you've burned through your InMail credits.

The same technique works for GitHub profiles: site:github.com "Rust" "Berlin" location — useful for sourcing developers who may not be active on LinkedIn at all.

And for finding CVs indexed on the web: site:docs.google.com OR site:dropbox.com filetype:pdf "curriculum vitae" "product manager" "London" — this surfaces publicly shared CV documents, which candidates often forget are indexed.

Boolean on LinkedIn: Platform-Specific Rules

LinkedIn's search is powerful but has quirks. These matter:

• Capitalise operators: AND, OR, NOT must be uppercase. Lowercase "and" is treated as a search term, not an operator.
• NOT becomes a minus: In LinkedIn's search bar, NOT is written as - (e.g., engineer -recruiter).
• Parentheses work: LinkedIn does support them, unlike some older job boards.
• Quotes are essential for multi-word titles: "Head of Product" vs Head of Product returns very different results.
• Search fields matter: Searching in the "Title" field returns far more precise results than a keyword search across the whole profile. Use filters aggressively.
• LinkedIn Recruiter vs. free search: With a free account, LinkedIn limits you to around 5 commercial searches per month before throttling. Recruiter Lite and full LinkedIn Recruiter give you significantly more — but the boolean logic itself works the same.

Boolean on Job Boards

CV databases like Totaljobs, Reed, CV-Library (UK), StepStone (Germany/Europe), and Pracuj.pl (Poland) all support boolean search, but each has slight variations:

• Totaljobs/CV-Library: Full boolean with AND, OR, NOT, parentheses, and quotes. Proximity operators (NEAR, WITHIN) are sometimes supported — check the help docs for the specific version.
• StepStone (DE/AT): Supports AND, OR, NOT and quotes. German-specific tip: search for both German and English equivalents of job titles — many German professionals list experience in both languages.
• Pracuj.pl: Basic AND/OR/NOT supported. Polish accented characters (ą, ę, ś, ź etc.) matter — searching "inżynier" and "inzynier" may return different results depending on indexing. Search both.

Advanced Techniques Worth Knowing

Proximity Operators

Some enterprise sourcing tools and databases support proximity search — Java NEAR/5 engineer finds results where "Java" and "engineer" appear within 5 words of each other. This cuts false positives. Not universally supported, but worth using when it is.

Wildcard Searching

The asterisk (*) acts as a wildcard, matching any suffix. manag* returns manager, managing, management, managerial. Useful for catching variations. LinkedIn doesn't support wildcards in basic search, but it works in full LinkedIn Recruiter and in most CV databases.

Stacking ORs for Role Title Breadth

Title variation is the single biggest source of missed candidates. A Finance Director might call themselves CFO, Finance Director, VP Finance, Head of Finance, Financial Controller (in some contexts), or Finansdirektör (Sweden). Your OR chain for a European cross-border search needs to cover all of them.

10+ Ready-to-Use Boolean Search Strings

Copy these, adapt the location/seniority filters, and use them. They're designed as starting points — you'll always need to tune based on your specific brief.

1. Software Engineer (Mid-Senior)

2. Senior Product Manager

3. Sales Manager / Head of Sales

4. Finance Director / CFO

5. Marketing Director / CMO

6. HR Director / Chief People Officer

7. Operations Director / COO

8. Data Engineer / Data Architect

9. Executive Assistant / Chief of Staff

10. In-House Legal Counsel

11. Recruitment Consultant (Agency-Side)

12. Engineering Manager / VP Engineering

The Limits of Boolean Search

Here's an honest assessment: boolean search is powerful, but it has real limitations worth acknowledging. And if you're on the market for new sourcing infrastructure, it's worth understanding how different platforms handle the gap between boolean and AI-powered search — the Yena vs Bullhorn sourcing comparison gets into this specifically, including how the two platforms handle passive candidate engagement differently.

It's keyword-dependent. A candidate with five years of Python experience who uses "programming" instead of "Python" on their profile won't appear in your boolean string. This is a bigger problem than most sourcers admit — especially with non-native English speakers who describe skills differently, or senior candidates who write narrative bios rather than keyword-dense profiles.

It rewards recent activity. Passive candidates who haven't updated their profile in two years won't show up in date-sorted results, even if they're exactly who you need.

It scales badly for complex semantic searches. "We need someone who can build a high-performing sales team, has experience in a post-series-B environment, understands European go-to-market, and has navigated a board-level relationship" — that's a brief. You can't boolean that.

This is where AI-powered search goes further. Yena's LinkedIn sourcing extension and AI candidate matching understand context, not just keywords — which means fewer missed candidates and less time refining strings. Boolean search remains an essential skill. But it doesn't have to be the ceiling.

Building a Personal Boolean Library

The most efficient sourcers maintain a personal library of search strings — organised by function, seniority, and geography. Every time you run a successful search, save the string. Every time you adapt one for a new market or role type, save that version too.

After six months, you'll have 40–50 tested, proven strings that cover the majority of your searches. The initial research time gets amortised across dozens of future placements. That's a compounding return.

Store them in a shared doc or note tool where your whole team can access and contribute. The collective sourcing intelligence of a 5-person desk is worth far more than any individual's saved searches.