LinkedIn Boolean search for recruiters: Operators, strings and examples

On this page
Boolean search for recruiting is a way of combining keywords with the operators AND, OR and NOT, plus quotation marks and parentheses, so a candidate search returns the profiles you want and leaves out the ones you don't. On LinkedIn you type the string into the main search bar or, in LinkedIn Recruiter, into the Keywords filter. A good string turns a job description into a search you can rerun, save and share with your team.
This guide covers the five operators, the rules LinkedIn applies to them, ten strings you can copy by role, X-ray search through Google, the mistakes that quietly break a search, and where keyword strings stop being enough.
The five Boolean operators
Every Boolean string is built from the same five pieces. AND and NOT narrow a search, OR widens it, quotation marks lock a phrase together, and parentheses control what runs first.
| Operator | What it does | Example | Effect on results |
|---|---|---|---|
| AND | Every term must appear | accountant AND finance AND CPA | Fewer, closer matches |
| OR | Any one of the terms can appear | sales OR marketing OR advertising | More matches |
| NOT | Removes profiles that contain the next term | programmer NOT manager | Fewer matches |
| " " (quotation marks) | Matches an exact phrase | "product manager" | Fewer, more exact matches |
| ( ) (parentheses) | Groups terms so they are evaluated together | VP NOT (assistant OR SVP) | Controls the logic |
The examples in the table are the ones LinkedIn uses in its own Boolean search help page. The same page sets the order LinkedIn evaluates a query in: quoted phrases first, then parentheses, then NOT, then AND, and OR last. That order is why parentheses matter. Without them, a string like java AND developer OR engineer runs as (java AND developer) OR engineer, which can return engineers who don't know Java.
How LinkedIn handles Boolean search
LinkedIn supports the five operators above, with a few rules that trip people up.
- Operators go in capitals. LinkedIn says you must type AND, NOT and OR in uppercase for the search to work correctly.
- Use straight quotation marks. LinkedIn's Sales Navigator help page says only standard, straight quotation marks are supported. Curly "smart" quotes pasted from a document are not.
- No wildcards or extra brackets. LinkedIn does not support braces { }, square brackets [ ], angle brackets < > or wildcards such as the asterisk *. Parentheses are the only grouping symbols it recognizes.
- Use AND and NOT, not + and -. The + and - signs are not officially supported, even when they seem to work.
- Stop words are dropped. LinkedIn.com doesn't use stop words such as "by", "in" and "with". In Recruiter, the Keywords filter ignores and, or, the, of, at, by, to, for, with, in, they, have, from, not, but and after, so a search for "after sales" returns profiles that contain only "sales".
Where Boolean works in each LinkedIn product
| Product | Where you can use Boolean | Operator limit |
|---|---|---|
| LinkedIn.com | The main search bar at the top of the page | Limited per query on the free search (the help page doesn't give a number) |
| LinkedIn Recruiter and Recruiter Lite | Quoted searches and Boolean modifiers in the Job titles, Companies and Keywords filters. Job titles, Location, Companies, Skills and Assessments, Schools, Industries and Spoken languages also offer Can have (OR), Must have (AND) and Doesn't have (NOT). The Project filter doesn't support Boolean. | No limit |
| Sales Navigator | The company, title and keyword fields | Maximum of 15 per query |
In Recruiter you rarely need one long keyword string. Put title variations in the Job titles filter, skills and other must-haves in Keywords, and use the Can have, Must have and Doesn't have dropdowns, which map to OR, AND and NOT.
LinkedIn Boolean search examples by role
Paste these into the LinkedIn search bar or the Recruiter Keywords filter, then add location and other filters. Each one is a starting point. Run it, read the first page of results, and adjust the titles, skills and exclusions to your role.
Backend software engineer
("software engineer" OR "software developer" OR "backend engineer" OR "backend developer") AND (python OR django OR flask) NOT (intern OR student OR recruiter)
Frontend engineer
("frontend engineer" OR "front end engineer" OR "front end developer" OR "UI engineer") AND (react OR typescript) NOT (manager OR intern)
Enterprise account executive
("account executive" OR "enterprise account executive" OR "strategic account executive") AND (SaaS OR software) AND (quota OR "president's club") NOT (assistant OR intern)
Sales development representative
("sales development representative" OR "business development representative" OR SDR OR BDR) AND (SaaS OR software) NOT (manager OR director)
ICU registered nurse
("registered nurse" OR RN) AND (ICU OR "intensive care" OR "critical care") AND (CCRN OR BLS OR ACLS) NOT (student OR "nursing assistant")
Financial analyst (FP&A)
("financial analyst" OR "FP&A analyst" OR "finance analyst") AND (forecasting OR budgeting OR modeling) AND (excel OR tableau OR "power bi") NOT (intern OR student)
Controller
("financial controller" OR "corporate controller" OR "assistant controller" OR controller) AND (CPA OR "certified public accountant") AND (GAAP OR "month end close") NOT ("air traffic" OR gaming)
Product manager
("product manager" OR "senior product manager" OR "product owner") AND (B2B OR SaaS) AND (roadmap OR discovery) NOT ("product marketing" OR "project manager" OR intern)
Data scientist
("data scientist" OR "machine learning engineer" OR "ML engineer") AND (python OR pytorch OR tensorflow) AND ("machine learning" OR "deep learning") NOT (intern OR student OR teacher)
Technical recruiter
("technical recruiter" OR "talent acquisition partner" OR "senior recruiter") AND (sourcing OR "full cycle") AND (greenhouse OR lever OR workday) NOT (agency OR staffing)
If a long string starts returning odd results on LinkedIn.com, you may be running into the operator limit on free search. Move the title group or the exclusions into filters and keep the keyword string short.
X-ray search: finding LinkedIn profiles through Google
X-ray search means using Google to search inside one website, here LinkedIn's public profile pages under linkedin.com/in. Google's search help documents the operators you need: quotation marks for an exact phrase, site: to limit results to one site, and a minus sign in front of a word to exclude it. Don't put a space between the operator and the term: site:linkedin.com/in works, site: linkedin.com/in doesn't.
Note the switch: on Google you exclude with a minus sign, while on LinkedIn you use NOT. You can also put OR in capitals between alternatives, as in the examples below. Google's help page doesn't list OR, so check that your results reflect it.
site:linkedin.com/in ("software engineer" OR "backend engineer") python "San Francisco" -recruiter -jobs
site:linkedin.com/in "registered nurse" ICU (Chicago OR Evanston) -student
site:linkedin.com/in controller CPA GAAP "Denver" -gaming
Be careful with X-ray results
- You only see what members made public. Members choose which profile sections are eligible to appear publicly, can opt out of appearing on search tools, and not all sections can be displayed publicly at all. A skill can be on someone's full profile and still be invisible to Google.
- Results can be out of date. After a member changes their public profile, it can take several weeks or months for search tools like Google to refresh, and LinkedIn doesn't control that process. The title and employer in a Google snippet may be old.
- Open the profile before you reach out. Treat X-ray as a way to widen a search, not as a record of where someone works today.
Common Boolean search mistakes
- Lowercase operators. LinkedIn needs AND, OR and NOT in capitals. Lowercase "or" is just a word, and in Recruiter it's a stop word that gets ignored.
- Curly quotes. Strings drafted in a word processor often pick up smart quotes, which Sales Navigator doesn't recognize. Retype the quotation marks or paste through a plain text editor.
- Wildcards and minus signs on LinkedIn. develop* and -intern are not supported. List the variants with OR, for example (developer OR development OR developing), and exclude with NOT.
- OR groups without parentheses. Because LinkedIn evaluates AND before OR, an unwrapped OR list attaches to the wrong terms. Wrap every OR group in parentheses.
- A NOT that's too broad. NOT removes any profile that contains the word. Recruiter highlights keyword matches in the profile card, Summary, Experience and Skills sections, so check what a broad term will catch before you exclude it.
- Stop words inside phrases. In the Recruiter Keywords filter, "after sales" matches profiles that only contain sales. Pick a phrase without stop words, or use the Job titles filter.
- One giant string. Long strings are hard to debug and can hit the operator limits on LinkedIn.com and Sales Navigator. Let filters handle location, company and seniority.
Where Boolean search falls short
Boolean matches text. It finds the words a person chose to put on a profile, not the work they did. That leaves three gaps no string fully closes.
Titles and synonyms vary more than any OR list. Each OR group is your guess at how people describe the same job. When Findem compared its curated titles with a traditional keyword search, a software engineer search took in 800+ additional titles and returned 12% more candidates, and a CFO search took in 1,000+ more titles and returned 40% more CFOs (Find candidates you'll never find with keyword search strings).
Seniority and fit don't always show up in the words. A candidate can list "software engineer", have the experience the role needs, and still be missed because "senior" isn't in their title. The reverse happens too: Findem's example is a search for a software engineer with Python skills that could return a profile with experience at a local zoo, not an engineer with verified Python experience (same post).
Inferred experience isn't in the text at all. A profile lists employers and dates. It doesn't say what stage the company was at when the person joined, how it grew while they were there, or what their career moves add up to. You can't write a Boolean string for "joined an early-stage company and stayed through its growth" unless someone happened to write those words.
How attribute-based search complements Boolean
Attribute-based search starts from what a person has done rather than the words on their profile. Findem, the People Intelligence Platform, builds search on 3D data, which goes beyond job titles and keywords by connecting people and company data over time, so a search can reflect someone's career journey, impact and attributes (Findem).
In practice, Copilot for Sourcing translates a job description into clear search criteria when a requisition opens, and surfaces candidates whose experience and trajectory align with the role across inbound, ATS, CRM and external sources. Profiles are continuously updated with verified career history, outcomes and trajectory. Recruiters can refine titles, skills, keywords and experience requirements, and if the team uses Boolean, review or edit strings as needed.
The two work best together. Boolean is still the quickest way to test a specific idea or enforce a hard requirement, such as an RN license or a CPA. Attribute-based search is better at finding the people who fit the role but describe themselves differently from your string. If you're comparing sourcing tools beyond LinkedIn, our guide to LinkedIn Recruiter alternatives covers the main options.
LinkedIn Boolean search FAQ
What is Boolean search in recruiting?
Boolean search is a way to combine keywords with the operators AND, OR and NOT, plus quotation marks for exact phrases and parentheses for grouping, so a candidate search returns the profiles you want and leaves out the ones you don't. Recruiters use it on LinkedIn, in job boards and ATS search, and on Google for X-ray searches.
Where can you use Boolean search on LinkedIn?
On LinkedIn.com you can type a Boolean string into the main search bar. In LinkedIn Recruiter and Recruiter Lite, you can use quoted searches and Boolean modifiers in the Job titles, Companies and Keywords filters. In Sales Navigator, Boolean works in the company, title and keyword fields.
Why is my LinkedIn Boolean search not working?
The usual causes are lowercase operators (LinkedIn needs AND, OR and NOT in capitals), curly quotation marks pasted from a document, wildcards such as an asterisk, the + and - signs, brackets other than parentheses, missing parentheses around OR groups, and stop words inside phrases. On the free LinkedIn.com search there is also a limit on the number of operators in one query.
What is X-ray search on LinkedIn?
X-ray search means using Google's site: operator to search LinkedIn's public profile pages, for example site:linkedin.com/in followed by titles, skills and a location. It only reaches the parts of profiles members have made public, and search engines can take weeks or months to pick up profile changes, so check the live profile before you reach out.
Is there a limit on Boolean operators in LinkedIn search?
Yes, on the free LinkedIn.com search, which limits the number of Boolean operators in a single query. LinkedIn Recruiter and Recruiter Lite have no limit. Sales Navigator allows a maximum of 15 Boolean operators in a single query.










