What is a Boolean String?

Extended definition

A Boolean string is the written artefact of Boolean search. If Boolean search is the skill, the string is the tool.

Sourcers write, test, refine, and save strings as reusable templates for specific role types — senior software engineer in London, account executive in Boston, staff product designer remote. The best sourcers maintain libraries of strings built over years, each tuned to return tight shortlists for a given role family.

A well-written string can be the difference between 30 relevant candidates and 3,000 noisy ones. Bad strings waste sourcer time on review; good strings make review easy.

Key elements of a Boolean string

A strong Boolean string typically has five layers:

• Title block — Grouped with OR, covering the main and synonym titles for the role: ("Software Engineer" OR "Developer" OR "Programmer"). This broadens coverage where title conventions vary across companies.
• Seniority block — Restricts to the right level: (Senior OR Staff OR Principal) or excludes wrong levels: NOT (Junior OR Intern OR Associate). Seniority filtering is where most strings go wrong.
• Skill block — The technical or functional requirements: (Python AND (Django OR Flask)). Skills should be specific enough to signal competence but not so narrow they exclude real matches.
• Location block — Either a city, region, or cluster: (Dublin OR "Greater Dublin" OR "Leinster"). On LinkedIn, location is usually set via filter rather than string.
• Exclusions — Removes irrelevant matches: NOT (recruiter OR "looking for" OR student OR "career transition").

A complete string might read: ("Senior Software Engineer" OR "Staff Engineer") AND (Python OR Go) AND (Django OR Flask OR Gin) NOT (recruiter OR "looking for").

Strings are iterated. Run, review 20 results, identify noise patterns, add exclusions, broaden or narrow as needed.

Most experienced sourcers refine a string three to five times before it’s stable. Once stable, they save it — tagged by role, dialect, and platform — so the next hire on that role family starts from a working baseline, not a blank box.

Why Boolean strings matter

A saved, tested Boolean string is a compounding asset. The first time it’s written, it takes 30-60 minutes.

Every subsequent use saves that time for the whole TA team. A sourcing team with a mature string library can respond to a new req within hours, not days, because the Boolean foundation for most role types already exists.

For VPs of TA, that’s the difference between a scrappy sourcing operation and an infrastructure — one produces hires, the other produces hires while the team is already moving on to the next ten.

Common mistakes and misconceptions about Boolean strings

• Writing strings from scratch for each req — Most role types are repeatable. A mature team reuses and refines strings, not rewrites them.
• Forgetting parentheses on compound logic. Senior OR Staff AND Python reads ambiguously. (Senior OR Staff) AND Python reads correctly.
• Stacking too many ANDs — Each AND narrows results. A string with seven ANDs almost always returns zero hits and needs relaxing.
• Using commas instead of operators — Some platforms interpret commas as spaces, not AND. Always use explicit operators.
• Never auditing old strings — Titles, tech stacks, and company landscapes change. A string that worked in 2022 may miss half the market in 2026 if it’s not refreshed.

Frequently asked questions

What is a Boolean string?

A Boolean string is a search query that combines keywords with Boolean operators — AND, OR, NOT, parentheses, and quotation marks — to return a precise list of candidates from a database or search engine. If Boolean search is the skill, the string is the tool.

How long should a Boolean string be?

As long as it needs to be to return the right shortlist, and no longer. For most roles, a string with a title block, skill block, seniority modifier, and a couple of exclusions does the job. Strings longer than a few lines usually contain redundancy and are worth editing down.

How do you test if a Boolean string is working?

Run it, review the first 20-30 results, and check whether they look like the target profile. If more than a third are clearly wrong, tighten the string. If fewer than 10-20 results return in a large market, loosen it. The first page of results tells you most of what you need to know.

Can you use the same Boolean string on LinkedIn and Google?

Partly. Core operators (AND, OR, NOT, quotes, parentheses) work on both. Wildcards, proximity operators, and some advanced syntax work on Google but not LinkedIn. Most sourcers maintain slightly different versions of each string for the two platforms.

Where should you save Boolean strings?

In a shared, searchable location the whole sourcing team uses — a Notion database, an internal wiki, or a CRM field. Keeping them in personal documents wastes the team's collective knowledge. Tag by role family, platform, and date last tested.