Boolean search
Also called: boolean operators, search strings
The operators that matter
The complete toolkit is small:
- AND: both terms must appear.
"senior engineer" AND python - OR: either term.
(designer OR illustrator) - NOT: exclude.
engineer NOT recruiter(LinkedIn uses NOT; Google uses-) - Quotes: exact phrase.
"head of marketing" - Parentheses: group.
(senior OR staff) AND (engineer OR developer)
Most sourcers use these in combination. A typical productive search has 6-10 operators.
What it’s actually for
Boolean is how you find candidates LinkedIn’s recommendation algorithm won’t surface. The default “people you might know” view shows you candidates similar to people you’ve already talked to. Boolean lets you ask the question “who, anywhere, has [specific signal]” — without LinkedIn deciding for you what’s relevant.
A starter pattern that works
For a senior backend engineer search:
("senior engineer" OR "senior software engineer" OR "staff engineer")
AND
(python OR golang OR java)
AND
(berlin OR munich OR remote)
NOT
(recruiter OR "looking for talent")
The NOT clause matters more than people think — it strips out the recruiters and the “I help people find jobs” profiles that pollute results.
X-Ray search
A variant: using Google to search LinkedIn (or another platform) with Boolean operators. site:linkedin.com/in "head of marketing" berlin finds public LinkedIn profiles via Google’s index — useful when LinkedIn’s own search throttles you.
Where Join fits
Sourced candidates from Boolean searches flow into Join’s talent pool with their Boolean-search-string captured as the source attribute. See the features page.