Boolean Search

Introduction

Boolean search is named after George Boole, a 19th-century mathematician who developed a system of logical algebra. In recruitment, Boolean search refers to the practice of combining keywords with logical operators to build precise search strings that surface specific candidates.

Despite the rise of AI-powered semantic search, Boolean search remains an essential recruiter skill. It gives sourcers and recruiters explicit control over which terms must appear, which are optional, and which must be excluded — something semantic search does not provide at the same level of precision.

Boolean search is used across the recruitment workflow:

• Google X-Ray search to find profiles across the open web
• LinkedIn search to find professionals by title, company, and skills
• GitHub and StackOverflow search to find developers by activity
• ATS and resume database search to find candidates in your own database
• Job board search to find active candidates

Boolean Operators

Boolean operators are the building blocks of every Boolean search string. There are three core operators every recruiter must know.

AND Operator

The AND operator tells the search engine that all terms must appear in the result. It narrows your search.

Example search string

React AND Node.js AND PostgreSQL

This finds candidates whose profiles contain all three terms. A candidate with React and Node.js but no PostgreSQL would be excluded.

When to use AND

• When you need candidates who have multiple required skills
• To narrow a broad search that returns too many results
• To combine role, skill, and location requirements

OR Operator

The OR operator tells the search engine that at least one of the terms must appear. It broadens your search and is commonly used for synonyms.

Example search string

(developer OR engineer OR programmer)

This finds candidates who use any of those job titles. It is especially useful because companies use different titles for similar roles.

Common OR use cases

• Synonyms: (React OR ReactJS OR React.js)
• Job titles: (manager OR lead OR head)
• Related skills: (Python OR Java OR Go)
• Locations: (Bengaluru OR Bangalore)

NOT Operator

The NOT operator excludes results containing a term. It filters out unwanted results.

Example search string

developer NOT junior NOT intern

This finds developer profiles that do not mention junior or intern — useful for sourcing experienced candidates.

Parentheses

Parentheses control the order in which operators are applied — just like in mathematics. They are essential for building complex search strings.

Without parentheses (ambiguous)

developer AND React OR Angular

This is ambiguous. It could mean developers who know React, plus anyone who knows Angular — which is probably not what you want.

With parentheses (clear)

developer AND (React OR Angular)

This clearly means: developers who know React or Angular.

Quotation Marks

Quotation marks search for an exact phrase. Without quotes, a search engine treats words separately.

Without quotes

project manager

This may return profiles that contain “project” and “manager” anywhere — not necessarily as a job title.

With quotes

"project manager"

This returns profiles containing the exact phrase “project manager.”

Wildcards

Wildcards allow you to search for variations of a word. The most common wildcard is the asterisk (*), which matches any number of characters.

Example

develop*

This matches developer, developers, development, developing, and other variations.

Useful wildcard examples for recruiters

• manag* — manager, managing, management
• engineer* — engineer, engineers, engineering
• analy* — analyst, analytics, analytical

Proximity Search

Proximity search finds terms that appear within a certain distance of each other. The syntax varies by platform, but commonly uses a tilde (~) followed by a number.

Example

"machine learning engineer"~5

This finds the words “machine,” “learning,” and “engineer” within 5 words of each other — useful when the phrase may be phrased differently.

X-Ray Search

X-Ray search is the recruiter technique of using Google to search within a specific website. It uses the site: operator and is one of the most powerful free sourcing methods available.

LinkedIn X-Ray example

site:linkedin.com/in ("software engineer" OR "software developer") Python Bengaluru

This searches Google for LinkedIn profiles of software engineers or developers who mention Python and Bengaluru.

GitHub X-Ray example

site:github.com ("machine learning" OR "deep learning") Python

Google Boolean Search

Google supports a rich set of Boolean operators and search commands. For recruiters, Google is a sourcing engine that reaches the entire open web.

Useful Google operators for recruiters

Combined Google search example

(site:linkedin.com/in OR site:github.com) ("frontend developer" OR "frontend engineer") React -job -jobs

This searches LinkedIn profiles and GitHub pages for frontend developers or engineers who mention React, while excluding job listings.

LinkedIn Boolean Search

LinkedIn supports Boolean operators in its keyword search field. This is one of the most common Boolean search use cases for recruiters.

Supported operators on LinkedIn

• AND — all terms must appear
• OR — at least one term must appear
• NOT — exclude a term (use parentheses for clarity)
• Parentheses — group terms
• Quotation marks — exact phrases

Not supported on LinkedIn

• Wildcards (*)
• Proximity search (~)
• The site: operator (that is Google-only)

LinkedIn Boolean search example

("software engineer" OR "software developer") AND (Python OR Java) NOT ("intern" OR "junior")

GitHub Search

GitHub is a goldmine for technical recruiters. Beyond Boolean keyword search, GitHub lets you search by programming language, repository activity, location, and followers.

GitHub search parameters for recruiters

GitHub search example

language:Python location:India followers:>20 repos:>10 "machine learning"

StackOverflow Search

StackOverflow (and the Stack Exchange network) is valuable for sourcing developers who actively answer technical questions. Reputation and tags signal genuine expertise.

Sourcing approach

• Search for users by technology tags (e.g., [react], [python])
• Filter by reputation to find highly active contributors
• Review tag scores to identify specialized expertise
• Combine with Google X-Ray: site:stackoverflow.com/users Python

Boolean Search vs Semantic Search

A common question is whether Boolean search is obsolete given the rise of AI-powered semantic search. The answer is that they serve different purposes and work best together.

Best Practices

• Always write operators (AND, OR, NOT) in CAPITAL LETTERS.
• Group every OR statement in parentheses.
• Use quotation marks for multi-word phrases and job titles.
• Test search strings incrementally — start simple, then add complexity.
• Save effective search strings for reuse across roles.
• Maintain lists of synonyms for common skills and job titles.
• Use NOT sparingly — it can exclude good candidates unintentionally.
• Combine Boolean sourcing with semantic matching for end-to-end evaluation.
• Keep up with platform-specific limitations (e.g., LinkedIn has no wildcards).
• Document your sourcing strings so team members can reuse them.