Microsoft · Global · Plain Boolean

LinkedIn Recruiter Boolean search

LinkedIn Recruiter documents Boolean inside its keyword filters — a different surface from the public LinkedIn search bar and from a Google X-Ray. The string is plain Boolean; the reach comes from Recruiter's structured filters around it.

Basis: Vendor documents the operators.

Your LinkedIn Recruiter string

Free · no login · nothing sent anywhere

Put the role and the skills in. This builds the string for LinkedIn Recruiter in its own grammar — with the operators and quotes that box actually parses.

Add one job title and one skill and the string appears here — built in LinkedIn Recruiter’s own grammar, in your browser.

Set these beside the string

  • Title, skills, location and years of experience are Recruiter's own filters and are more precise than the same facts typed into the string.
  • Lead, account and current-employer filters narrow the pool before the keyword field is read.
  • Boolean goes in the keyword filter; the other controls stay outside the string.

ATS Boolean string

("Operations Manager" OR "Supply Chain Manager") AND (Lean OR "Six Sigma") AND (Dubai)

Composed from titles “Operations Manager”, “Supply Chain Manager” and skills “Lean”, “Six Sigma”, Dubai, 6 years. Paste it as-is.

What the vendor documents

  • AND, OR and NOT are documented inside Recruiter's keyword filters.
  • Double quotes keep a multi-word phrase together.
  • Parentheses group alternates so one group can be combined with another.

What it does not say

  • This is the paid Recruiter seat, not the free LinkedIn search bar. The free route is a Google X-Ray that opens with site:linkedin.com/in/, which is a different dialect and a different page.
  • Recruiter's structured filters — current title, skills, location, years of experience — are more precise than putting the same facts in the string. Use the filters for fields and the string for free text.
  • No search-engine operators. site:, intitle: and filetype: belong to Google, not to Recruiter's keyword field.

The filters that do the work

  • Title, skills, location and years of experience are Recruiter's own filters and are more precise than the same facts typed into the string.
  • Lead, account and current-employer filters narrow the pool before the keyword field is read.
  • Boolean goes in the keyword filter; the other controls stay outside the string.

Why the search returns nothing

  • A location term inside the keyword string matches profile text, not geography, so it can exclude candidates who live there but never mention it.
  • Recruiter's filters and a string that repeats the same facts compound each other, and the pool collapses to almost nothing.
  • The Recruiter seat and the free search bar read different indexes; a string that works in one says nothing about the other.

How to paste it

  1. 1

    Open Recruiter's talent search and the Keywords filter.

  2. 2

    Paste the plain-Boolean string into Keywords; keep the uppercase operators and the quotes.

  3. 3

    Set title, skills, location and experience in the filters beside the box rather than adding them to the string.

Where each claim comes from

Every claim on this page carries a status. documented means the vendor's own page says it. reported means an independent source shows it. our claim means we say it and nobody else does.

LinkedIn Recruiter Boolean search FAQs

Does LinkedIn Recruiter support Boolean search?

Yes. LinkedIn's Recruiter help documents AND, OR, NOT, quotes and parentheses inside Recruiter's keyword filters. It is not the same box as the public LinkedIn search bar.

Is this the same as a LinkedIn X-Ray?

No. A LinkedIn X-Ray is a Google search pinned with site:linkedin.com/in/ and reads public profile text. Recruiter Boolean runs inside LinkedIn's own index and can be combined with Recruiter-only filters.

Can I use site:linkedin.com/in/ in Recruiter?

No. site: is a Google operator. Inside Recruiter's keyword field it is literal text; use Recruiter's own filters for scope and the X-Ray dialect when you want public profiles through a search engine.

Should I put location in the string?

Prefer the location filter. A city inside the keyword string matches profile text, not geography, so it can exclude candidates who live there but do not mention it.

Related

Start your next shortlist tonight.

Open a workspace, paste a JD, and screen the first pipeline. Plans from $9/mo, no auto-renewal.

Get started