All articles

Boolean search for recruiters: strings that work, and when to use AI

Boolean search for recruiters: the five operators, where each works on LinkedIn, Google X-ray and CV databases, 12 copy-paste strings, and the same search asked in plain words.

On this page
  1. What is Boolean search for recruiters?
  2. Where does Boolean search work on LinkedIn, Google and job boards?
  3. Boolean search on LinkedIn and LinkedIn Recruiter
  4. Boolean search on Google (X-ray)
  5. Boolean search on CV databases and job boards
  6. Which Boolean strings work for common agency roles?
  7. Boolean strings for software engineers
  8. Boolean strings for nurses
  9. Boolean strings for accountants
  10. Boolean strings for sales
  11. Boolean strings for construction
  12. Boolean strings for executive search and business development
  13. What does the same search look like as a plain-language AI prompt?
  14. How hyreflow mapped the request into a search
  15. What the hyreflow search returned
  16. When does Boolean search still beat AI search?
  17. What are the most common Boolean search mistakes?
  18. How do in-house recruiters use Boolean search?
  19. Questions recruiters ask about Boolean search

The short answer

Boolean search lets a recruiter define a candidate with five operators: AND, OR, NOT, quotation marks for exact phrases and brackets for grouping. LinkedIn, LinkedIn Recruiter, Google X-ray and CV databases such as Reed read them, each with its own limits. AI replaces the string when you would rather describe the person: on 30 Oct 2026 hyreflow turned one plain request into a search that returned 10 Manchester engineers for 0.5 credits.

  • LinkedIn wants AND, OR and NOT in capitals, reads only round brackets and ignores wildcards.
  • Google X-ray reads quotes, the minus sign and the site operator, and its first result count is an estimate.
  • Write the location the way profiles show it (Austin, Texas), or first names and firm names match instead.
  • A plain-language search can hold years of experience, which a string cannot, and the people it returns cost credits.
  • A string costs nothing to run on Google or free LinkedIn and works in any tool that reads the operators.

Boolean search is how a recruiter tells a search box exactly who to find. Every string is built from five operators, and the same string behaves differently on LinkedIn, Google and a CV (resume) database.

Below are the rules for each platform and 12 strings for common agency desks. Eleven ran on 30 Oct 2026. The four LinkedIn strings returned nothing in free LinkedIn search and are untested in Recruiter. Then the same search is typed in plain words to hyreflow, the AI recruitment assistant.

What is Boolean search for recruiters?#

Boolean search for recruiters writes a candidate search as logic, so the database returns only the profiles that meet every condition. It uses five operators. Each one narrows the search, widens it or sets the order in which the others apply.

OperatorWhat it doesExample
ANDEvery term must appear. Narrows the search.accountant AND CIMA
ORAny one of the terms may appear. Widens the search; use it for title variants."staff nurse" OR "registered nurse"
NOTRemoves profiles that contain the term. On Google, use a minus sign instead.developer NOT intern
Quotation marksMatch the exact phrase, words in that order."quantity surveyor"
BracketsGroup terms so OR and AND apply in the order you mean.(ACCA OR CIMA) AND "management accountant"

LinkedIn applies them in a fixed order, according to its help page on Boolean search (checked 30 Oct 2026). Quotes come first, then brackets, NOT and AND, with OR last.

Put every OR group in brackets anyway, so the order is explicit in every tool you paste the string into.

Where does Boolean search work on LinkedIn, Google and job boards?#

Boolean search works on LinkedIn, LinkedIn Recruiter, Google and most CV databases. Each one reads a slightly different set of operators and sets its own limits. The table shows what each one's own help pages say, checked on 30 Oct 2026.

Where you searchReadsDoes not readLimit
LinkedIn.com search barAND, OR, NOT in capitals; quotes; round bracketsWildcards; square, curly or angle brackets. + and - are not officially supportedA cap on operators per search; the number is not published
LinkedIn Recruiter and Recruiter LiteThe same, in the Job titles, Companies and Keywords filtersBoolean in the Project filterNo cap on operators
LinkedIn Sales NavigatorThe same15 operators per search
Google (X-ray)Quotes, the minus sign, site:, filetype:, before: and after:NOT as a word. OR and brackets are not on Google's list, but they worked in our testssite: results are not exhaustive
Reed.co.uk CV SearchAND, OR, quotes, brackets, and * for word endingsNOT is not listed in Reed's guide3,000 characters in the keyword field

Boolean search on LinkedIn and LinkedIn Recruiter#

On LinkedIn.com, you type the string into the main search bar with AND, OR and NOT in capitals. LinkedIn's help page says round brackets are the only grouping symbols it recognises, and it does not support wildcards such as an asterisk. It also drops stop words such as "by", "in" and "with".

The free search caps the number of Boolean operators in one query and does not say what the cap is. LinkedIn's page on Boolean limits says Recruiter and Recruiter Lite have no limit, and Sales Navigator allows 15 (checked 30 Oct 2026).

On 30 Oct 2026 we pasted the four LinkedIn strings in this guide into the LinkedIn.com search bar. Each has eight or nine operators, and all four returned no results, with no reason given.

We have not confirmed that the operator cap caused it. Run strings this long in Recruiter or Recruiter Lite, which have no cap.

In LinkedIn Recruiter and Recruiter Lite, Boolean works in the Job titles, Companies and Keywords filters. The Must have, Can have and Doesn't have dropdowns map to AND, OR and NOT, according to Recruiter's help page. The same page lists lowercase "and", "or" and "not" among the stop words the Keywords filter ignores, so the operators only work in capitals.

InMail to people outside your network needs a LinkedIn licence. What a seat costs and when it pays for itself is covered in is LinkedIn Recruiter Lite worth it.

Boolean search on Google (X-ray)#

Google's help page Refine Google searches lists quotes for an exact phrase, a minus sign to exclude a word and site: for one website. It also lists before:, after: and filetype: (checked 30 Oct 2026).

There is no space after the colon: site:linkedin.com/in works, site: linkedin.com/in does not. Google has no NOT operator, so exclusions use the minus sign.

Google's own documentation warns that a site: search "doesn't necessarily return all the URLs that are indexed", in the words of Google Search Central. Our test showed the gap between that estimate and the results you can open.

64

results could actually be opened for the backend engineer X-ray string below. Page one of the same search estimated about 68,100, and Google stopped at page 7.

Source: hyreflow test in Google, UK settings, 30 Oct 2026

On our test browser, Google showed its unusual-traffic check after seven searches in about three minutes. Most were deep pages of one string, so X-ray at volume runs into that check. Google's help page states no maximum query length, so keep X-ray strings short and test them in parts.

hyreflow runs X-ray strings through Serper, a Google search API, at 0.1 credits a search, charged even when nothing comes back (30 Oct 2026). Each call in our tests returned at most 10 results, even when we asked for 100.

Boolean search on CV databases and job boards#

CV databases read most of the same operators, and some read more. The CV Search of Reed.co.uk, a UK job board, reads AND, OR, quotes, brackets and an asterisk for word endings. Admin*, for example, finds administrators and administrative assistants.

That is from Reed's Boolean guide, published in September 2024. The same guide gives the keyword field a 3,000-character limit and does not list NOT.

Indeed's employer guide to Boolean search, updated 16 Jul 2026, describes AND, OR, NOT, brackets and quotation marks. It applies them to resume databases and sourcing tools. Check the help page of your own job board or ATS before you rely on NOT or a wildcard, because support differs between tools.

GitHub's user search takes qualifiers instead of Boolean words. GitHub Docs describe language: for users whose repositories are mostly in one language and location: for where they say they live.

Which Boolean strings work for common agency roles?#

The 12 strings below cover common agency desks: tech, healthcare, finance, sales, construction and executive search. Each one is built from the same blocks, and the ones marked tested were run on 30 Oct 2026. Only counts are reported, no names.

  1. Write the title block

    List every name the job goes by, joined with OR, inside brackets. One literal title is the most common reason a search misses people.

  2. Add the must-have skills

    Put each requirement in its own OR group and join the groups with AND. Tools, certificates and methods separate people; soft skills do not.

  3. Write the location as profiles show it

    Quote it in full, such as "Austin, Texas" or "Leeds, England". A bare city name matches first names, surnames and company names.

  4. Add exclusions last

    Run the search first, look at the noise, then exclude it. LinkedIn's own advice is to be "specific and inclusive rather than vague and exclusive".

  5. Check the count, then loosen

    If nothing comes back, widen the titles first, then drop the rarest skill, and only then change the market.

hyreflow's Boolean and X-ray string builder does these steps from a job spec. It spends no credits, because writing a string calls no data provider.

Boolean strings for software engineers#

Code
("backend engineer" OR "software engineer" OR "python developer") AND python AND (django OR fastapi OR flask) NOT (intern OR graduate OR recruiter)

Three title variants, Python plus one of three frameworks, and the usual noise removed. Run in the LinkedIn.com search bar on 30 Oct 2026, with nine operators: LinkedIn showed no results.

Code
site:linkedin.com/in ("backend engineer" OR "software engineer") python "Manchester"

Tested in Google with UK settings. Page one estimated about 68,100 results; paging through, only about 64 could be opened, across seven pages. Add -recruiter -intern once you see what the first page returns.

Code
language:python location:"manchester, uk" followers:>=10

On GitHub's search, language:python location:manchester returned 1,484 users. That bare city also covers Manchester, New Hampshire, which returned 51 on its own. Writing "manchester, uk" cut the list to 552, and a floor of 10 followers cut it to 96.

Boolean strings for nurses#

Code
site:linkedin.com/in ("staff nurse" OR "registered nurse" OR "senior staff nurse") (ICU OR "intensive care" OR "critical care") NMC London

Run through Serper with UK settings: of the first 10 results, 8 were critical care nurses in clinical posts. One was a nursing lecturer, and one worked at a hospital outside the UK.

NMC is the UK's nursing register, so requiring it favours profiles that mention UK registration.

Code
("registered nurse" OR RN) AND (ICU OR "intensive care" OR "critical care") AND (CCRN OR ACLS) NOT ("nursing assistant" OR CNA OR student)

US profiles often write RN after the name, so the title block includes it. CCRN and ACLS are certifications that critical care nurses put on their profiles, and the NOT group removes assistants and students. Run in the LinkedIn.com search bar on 30 Oct 2026, with nine operators: LinkedIn showed no results.

Boolean strings for accountants#

Code
("management accountant" OR "financial accountant" OR "finance business partner") AND (ACCA OR CIMA OR ACA) NOT (trainee OR "part qualified" OR recruiter)

Three UK titles, qualified through one of three bodies. Run in the LinkedIn.com search bar on 30 Oct 2026, with eight operators: LinkedIn showed no results.

NOT "part qualified" removes people still studying. It also removes anyone who once wrote that phrase on their profile, so drop it if the list looks thin.

Code
site:linkedin.com/in ("senior accountant" OR "staff accountant") CPA "Chicago" -recruiter

Run through Serper with US settings: nine of the first 10 were in the Chicago area. The tenth lived elsewhere and matched "Chicago" through a university's name. One result matched CPA through the name of an accounting firm.

Code
(Bookkeep* OR "accounts assistant") AND (Xero OR Sage OR QuickBooks)

Bookkeep* catches bookkeeper and bookkeeping in one term, which Reed reads and LinkedIn does not. Not run: we have no Reed account.

Boolean strings for sales#

Code
site:linkedin.com/in ("account executive" OR "enterprise account executive") (SaaS OR software) "Austin, Texas" -recruiter -intern

The first run used "Austin" on its own. Only 4 of the first 10 were in Austin; 6 were people named Austin who lived elsewhere. With "Austin, Texas", all 10 showed Austin, Texas on the profile, 9 of them as a current role or home city.

Boolean strings for construction#

Code
site:uk.linkedin.com/in "quantity surveyor" (NRM OR "cost management" OR "final accounts") "Leeds, England" -recruiter -recruitment

NRM and final accounts are terms quantity surveyors use in their work. The first version used site:linkedin.com/in and a bare Leeds: none of the first 10 lived in Leeds, and 4 were outside the UK.

The version above searches LinkedIn's UK pages and writes "Leeds, England". It returned 10 UK profiles: 5 people in the Leeds area now and 3 who had worked there before.

Boolean strings for executive search and business development#

Code
("finance director" OR CFO OR "chief financial officer") AND ("private equity" OR "PE-backed" OR "portfolio company") NOT (interim OR fractional OR recruiter)

Finds finance leaders with private equity experience. NOT interim also removes anyone who ever held an interim role, so delete it when the client is open to interim candidates. Run in the LinkedIn.com search bar on 30 Oct 2026, with eight operators: LinkedIn showed no results.

Code
site:linkedin.com/in ("head of engineering" OR "engineering manager" OR CTO) "Leeds, England" -recruiter

Finds engineering leaders in Leeds for business development: the people who sign off developer hires. Run through Serper with UK settings on 30 Oct 2026: of the first 10 results, 8 were software or technology leaders in Leeds. One had moved to a role in Manchester, and one managed engineers at an oilfield equipment maker.

Working out which of them owns the role is covered in how to find hiring managers.

What does the same search look like as a plain-language AI prompt?#

As a plain-language prompt, the backend engineer search becomes one sentence, and hyreflow turns it into a structured people search instead of a string. We ran it on 30 Oct 2026 through hyreflow, which runs inside Claude and ChatGPT as a connector. The run was paid in hyreflow credits.

Claude prompt

Use hyreflow to find 10 backend or software engineers in Manchester, UK, who work in Python and have at least four years of experience. Show me how you mapped the search before you spend anything.

What comes back

A free preview of how the request was mapped, then 10 profiles in the Manchester area. Each has a current title, employer, listed skills and a LinkedIn link. No contact details: those are a separate step, priced before it runs.

Credits
0.5
Cost
About $0.05
Time
About 9 seconds for the search step

Connecting hyreflow to Claude takes a few minutes, and the steps are in how to source candidates with Claude.

hyreflow split the request into the same blocks a string has, plus one a string cannot hold. The preview showed the mapping before anything was charged.

Boolean blockhyreflow people search fieldValue in this run
Title block, joined with ORtitles, matched against the current titleBackend Engineer, Software Engineer, Python Developer
Skills, joined with ANDskills: any listed skill matches, and only AI Ark applies itPython
LocationlocationsManchester, United Kingdom
No equivalent in a stringmin_experience_years, across the whole career4
Exclusions, NOTChecked against the results after the searchNot used in this run

The preview named the first provider, AI Ark, a people-data provider. It also gave the price: 0.5 credits for each page of 10 people that comes back. Prospeo, a people and contact data provider next in line, was skipped because it has no skills filter.

What the hyreflow search returned#

AI Ark reported 936 matching profiles. hyreflow returned the first 10, all in the Manchester area, and charged 0.5 credits. The same search without the four-year floor reported 1,084 and included a degree apprentice and a graduate engineer; the floor removed both.

Current titleLocationEmployer typeLanguage named in the headline
Software Engineer, GenAI and backendManchester areaInvestment platformNone
Senior Software EngineerManchester areaData software companyJava, TypeScript
Lead Software EngineerManchesterTelecoms groupNone
Software Engineer IIManchester areaTravel booking siteJava, .NET
Senior Backend EngineerManchesterFood delivery companyGo
Software EngineerManchester areaCredit ratings agencyPython

All 10 list Python as a skill. Only one names Python in the headline, and four lead with Java, .NET or Go.

A skills match has the same blind spot as python in an X-ray string. It proves the word is there, not that it is the person's main language.

Check each row's location too. As with location:manchester on GitHub, a city name can match a town of the same name in another country.

The next step is reading each person's work history against the brief, which the job spec to shortlist playbook does. A full run with scores and contact details is in how to turn a job description into a shortlist with Claude.

At the Starter plan's rate, $49 a month for 500 credits on hyreflow pricing (30 Oct 2026), 0.5 credits is about five cents. Most searches charge for the people they return, and some methods also charge per call.

Boolean search still beats AI search when you need exact control, a search that costs nothing, or a database the AI tool cannot reach. AI search wins when the request holds things a string cannot express, such as years of experience.

Boolean stringPlain-language search in hyreflow
Cost per searchNothing on Google or free LinkedInReturned people cost credits (0.5 for 10 in our run); some methods also charge per call
What you controlEvery term, visible in the stringThe mapping, shown in a free preview
Years of experience, tenureNot expressibleFields of their own
Where it runsLinkedIn, Recruiter, Google, CV databases, and any ATS whose search reads the operatorsSeveral people-data providers, through one connector
LinkedIn's member database and InMailYes, with a LinkedIn account and licenceNo; InMail still needs a LinkedIn licence
Contact detailsA separate toolThe next step in the same conversation

LinkedIn and Reed now offer plain-language search themselves. LinkedIn Recruiter's AI Search lets you describe a candidate or paste a job description, then applies the filters for you. LinkedIn's help page says these AI features are reaching accounts gradually (checked 30 Oct 2026).

Reed.co.uk launched an AI-Search Builder on 30 Sep 2026 that builds a CV search, title variants included, from a job description.

Sourcing platforms built around search screens still take Boolean. SeekOut, an AI sourcing platform, names itself beside Google and LinkedIn in its own Boolean guide (checked 30 Oct 2026).

hireEZ, another AI sourcing platform, has the line "No more blind keyword matches" on its AI Sourcing page (checked 30 Oct 2026). The page does not mention Boolean. How both compare with hyreflow is in SeekOut vs hyreflow and hireEZ vs hyreflow.

What are the most common Boolean search mistakes?#

The most common Boolean search mistakes are lowercase operators, location words that match names, and treating Google's estimate as a count. Each one turned up in the tests above or on the platform's own help page.

  1. Lowercase operators on LinkedIn. Recruiter lists "and", "or" and "not" among the stop words it ignores, so type them in capitals.
  2. A bare city name. Among the first 10 results, "Austin" returned six people named Austin, and a bare Leeds returned nobody who lived in Leeds. Quote the location as profiles write it.
  3. Reading Google's first number as a count. About 68,100 estimated became about 64 results you could open.
  4. Wildcards where they are not read. LinkedIn ignores the asterisk; Reed reads it.
  5. Plus and minus signs on LinkedIn. LinkedIn does not officially support them; write AND and NOT.
  6. Too many ANDs on the first pass. Start with titles and the core skill, check the count, then tighten.
  7. A NOT that removes good people. NOT manager removes every profile with the word anywhere on it, past roles included.

In-house talent teams use the same strings in their ATS keyword search and in LinkedIn Recruiter. The business development string does not apply to them.

Recruiter's AI Search, which takes a pasted job description, suits a team that writes its own job ads. An in-house sourcer's toolkit, Boolean included, is described in what is a sourcer.

An agency recruiter also has to decide which source to search first. The sources worth working, from your own database to GitHub, are ranked in the best candidate sources for recruitment agencies.

Turn a job spec into strings

Paste a spec and get the title, skill and exclusion blocks, a LinkedIn string and an X-ray string. Writing them spends no credits.

See the string builder
Is there a free Boolean string generator for recruiters?

Claude or ChatGPT will write a string from a job spec. hyreflow's Boolean and X-ray string builder lists the title variants, skill groups and exclusions separately. It spends no credits, because writing a string calls no data provider. Running a string is a separate, priced step.

Can ChatGPT or Claude write my Boolean strings?

Yes. On a hyreflow sales call in October 2026, a recruiter described asking AI assistants for Boolean tips, then running the searches on LinkedIn by hand. Check the operators against the table in this guide first, because LinkedIn, Google and CV databases each read them differently.

Why does my LinkedIn Boolean search return no results?

The usual causes are operators in lowercase, square or curly brackets, an asterisk, or too many AND groups. On free LinkedIn there is also a cap on operators per search, which LinkedIn does not publish. Remove the rarest skill first and run it again.

Is Boolean search still worth learning in 2026?

Yes, even if an assistant writes your strings. Reading a string is how you see why a search came back empty or full of noise. The same five operators work in LinkedIn Recruiter, Google and most CV databases.

Does hyreflow search LinkedIn?

hyreflow replaces the search with people-data providers and public sources, and it never logs in to your LinkedIn account. With HeyReach connected, LinkedIn outreach goes out from your own account (30 Oct 2026). InMail to people outside your network still needs a LinkedIn licence.

Sources

  1. Use Boolean search on LinkedIn, LinkedIn Help. Checked 30 Oct 2026
  2. Use Boolean to filter search results in Recruiter and Recruiter Lite, LinkedIn Recruiter Help. Checked 30 Oct 2026
  3. Boolean Query Limitations, LinkedIn Help. Checked 30 Oct 2026
  4. AI features in LinkedIn Recruiter, LinkedIn Help. Checked 30 Oct 2026
  5. Refine Google searches, Google Search Help. Checked 30 Oct 2026
  6. site search operator, Google Search Central. Checked 30 Oct 2026
  7. Using Boolean search in recruitment, Reed.co.uk. Checked 30 Oct 2026
  8. Introducing: AI-Search Builder for CV Search, Reed.co.uk. Checked 30 Oct 2026
  9. What Is Boolean Search for Recruiting and How Can Employers Use It?, Indeed. Checked 30 Oct 2026
  10. Searching users, GitHub Docs. Checked 30 Oct 2026
  11. AI Sourcing, hireEZ. Checked 30 Oct 2026
  12. A Guide to Boolean Search for Recruiters, SeekOut. Checked 30 Oct 2026
  13. hyreflow pricing, hyreflow. Checked 30 Oct 2026
Written by

Niklas Huetzen

Co-founder, hyreflow

Niklas builds hyreflow and has set up sourcing and business development systems for 75+ recruitment agencies.

Niklas on LinkedIn

Run it yourself, in the agent you already use.

hyreflow works inside Claude, ChatGPT and any agent that speaks MCP. New workspaces start with free credits, and nothing is charged until data comes back.

Add this URL as a custom connector in Claude

https://recruit.hyreflow.ai/api/v2/mcp

In Claude: Customize, then Connectors, then Add custom connector.

Using ChatGPT or another client? See the setup steps for each one.