Boolean search in recruitment

The name comes from Boolean logic, where a statement is either true or false. Applied to sourcing, every operator is a filter: AND narrows, OR widens, NOT excludes, quotation marks lock an exact phrase, and parentheses control the order the logic runs in. The payoff is precision and repeatability: a good string returns the same shortlist next month, can be handed to a colleague, and can be tuned one operator at a time when the results miss.

Recruiters use boolean search in three places: LinkedIn and its Recruiter products, the resume databases inside an ATS or job board, and general web search, where an X-ray string searches inside one site from Google. The operators are the same everywhere; what differs is which ones each platform honors.

LinkedIn documents support for exactly five: quoted phrases, AND, OR, NOT, and parentheses, with the boolean words in uppercase. It does not support wildcards, brackets, or braces, and notes that plus and minus signs may appear to work but are not officially supported. Unsupported syntax usually fails silently and just returns worse results, so when a string underperforms on any platform, check that platform’s current documentation before rewriting the logic.

The strings below are starting points for the three main surfaces: LinkedIn search, Google X-ray, and resume databases. Swap the titles, skills, and metros for your desk and keep the operator structure.

Treat every string as a draft. Run it, scan the first page of results for false positives, add a NOT for the noise you actually see, and save the version that works. A desk that saves its strings builds a library a new recruiter can run on day one, which is the real compounding value of learning the syntax.

Almost every boolean guide stops at candidates, which is odd, because the same operators point the other way. A company that is hiring emits public text: job postings, careers pages, and managers announcing openings. Strings that search that text surface client prospects with live need, which is warmer than anything a purchased list can tell you.

The limit is not the strings; it is the running of them. Client-side boolean work only pays if someone runs the saved searches every week and sends the outreach while the posting is fresh, and that routine is exactly what collapses on a busy desk. dreach, which is our product, automates that side: it watches hiring signals in your niche continuously, starts conversations with the managers who own the roles through email or LinkedIn, follows up until there is an answer, and books the intake call. SMS or iMessage is used only after the recipient requests it or when the agency has another documented, counsel-approved basis.

Sourcing tools are moving to natural-language search: Juicebox pairs plain-English candidate search with agents that assess profiles and send outreach, and the larger platforms are adding similar layers. For a first pass across a big market, those tools are usually faster than hand-built strings.

Boolean still earns its keep in three places. Precision: when a search must exclude exactly the wrong profiles, an explicit NOT beats a model’s guess. Repeatability: a string is auditable and shareable, and a conversational search is neither. And cost: boolean works on the free tier of everything, which matters for a new desk. The strongest sourcers treat AI search as the wide net and boolean as the scalpel, and knowing the operators is what makes an AI tool’s output checkable.