LinkedIn Boolean Search on Sales Navigator: Operators and Strings

LinkedIn holds the largest professional dataset on the open web, and its search bar is the cheapest way into it. Most people type two words and scroll. A LinkedIn Boolean search does the opposite: it hands the search engine a small piece of logic, with AND, OR, NOT, quotes and parentheses, so that ten thousand vague results collapse into two hundred people you would actually message. This guide covers the operators Sales Navigator really supports, the order it applies them in, twelve strings you can paste today, and the failure modes that quietly return the wrong people.

LinkedIn Boolean search operators: the quick reference

Five operators do all the work. Everything else is a combination of these five. LinkedIn documents them for Sales Navigator and for the classic search bar, and the behaviour is the same in both places.

Operators have to be typed in capitals. not in lower case is read as the English word and searched as a keyword, which is one of the most common reasons a carefully written string returns nothing useful.

The field operators that no longer work

Plenty of guides still list title:, company:, school:, firstname: and lastname: as Sales Navigator operators. They are not in LinkedIn's current documentation, and they do not filter anything in Sales Navigator today. Typing title:CFO searches for the literal string, colon included. Use the dedicated filters instead: Sales Navigator gives you a Current job title filter, a Company filter and a Keywords field, and Boolean logic works inside each of them.

Where a LinkedIn Boolean search applies in Sales Navigator

This is the part that costs people the most time. Boolean logic is not accepted everywhere in the interface, and the fields that reject it do so without an error message.

• Keywords: scans the whole profile, headline, summary, experience and skills included. The widest field, and the noisiest.
• Current job title: scans the present role only. This is where most prospecting strings belong.
• Company: scans the employer name, useful for account based work when you hold a short list of names.

The dropdown filters, geography, headcount, industry, seniority, years in role, are picked from a list. They already behave like an AND against everything else, so there is no reason to describe them in your string. The practical shape of a good query is therefore narrow text in the title field, hard constraints in the dropdowns, and the Keywords field kept for a signal you cannot express any other way.

One ceiling to keep in mind: LinkedIn caps a Sales Navigator query at roughly fifteen operators per field. A list of forty job title variants glued together with OR will not run. Split it into two saved searches instead of losing half the string without noticing.

The order LinkedIn applies to your query

When you mix operators without parentheses, LinkedIn resolves them in a fixed order: quotes first, then parentheses, then NOT, then AND, then OR. Read that sequence twice, because OR resolving last is the single most expensive thing to misunderstand.

Take CTO OR "VP Engineering" AND fintech. You meant both titles inside fintech. LinkedIn resolves the AND first, giving "VP Engineering" AND fintech, then applies OR, so the query becomes every CTO on the platform, in any industry, plus the fintech VPs. The list explodes and the titles look right, which is why nobody checks.

The fix is one pair of brackets: (CTO OR "VP Engineering") AND fintech. Rule of thumb, every OR block you write gets its own parentheses, always, even when it looks unnecessary.

A quick way to trust a string before you rely on it: run it, note the result count, then remove one bracketed block and run it again. If the count barely moves, that block is doing nothing and you can drop it. If the count triples, that block was the one holding the query together. Two minutes of this tells you more about a query than any amount of reading it back to yourself, and it is the only way to catch a precedence problem that produces a plausible looking list rather than an empty one.

The same habit applies to exclusions. NOT is blunt, and every term you exclude also removes people who mentioned that word once in a summary from a previous job. Start with two exclusions, not eight, and add one at a time while you watch what the count does.

Twelve Boolean search strings you can paste today

These go in the Current job title field unless the line says otherwise. Replace the industry words with your own and keep the bracket structure exactly as it is.

A string is only half a list. The other half is what comes out of it, which is a set of profiles with no email address, no direct line and no company data attached. That gap is the whole reason the next two sections exist.

LinkedIn free, Sales Navigator and Recruiter: what changes

The operators are identical across the three. What changes is where you are allowed to use them and how much of the result you can reach.

If you run prospecting rather than hiring, the free version of Sales Navigator is worth understanding before you pay, and the Sales Navigator pricing page covers what each tier actually unlocks.

Why your Boolean search returns the wrong people

Six failure modes account for most of it, and none of them produce an error message.

• Curly quotes. Written in a document, pasted into LinkedIn, ignored. Retype the quotes in the field itself.
• Lower case operators. and, or and not are treated as ordinary words. Capitals are mandatory.
• A missing bracket around an OR block. The precedence order does something you did not ask for, and the list looks plausible.
• Stop words. Small connectors such as by, in and with are dropped, so "head of growth in fintech" is not the phrase you think it is.
• Wildcards. There is no *. engineer* will not catch engineering. Spell out the variants inside an OR block.
• The wrong field. Keywords scans the entire profile, so a CFO who once wrote the word developer in a summary matches a developer string.

When a query behaves oddly, cut it in half and run each half on its own. The half that returns a sane count is fine, and the problem lives in the other one.

From a LinkedIn Boolean search to a list you can work

Sales Navigator gives you people on screen. It does not give you a file, an email address or a phone number, and it has no export button. So the string you just wrote is the targeting layer, and the data layer sits next to it.

Derrick covers that second half, and you reach it through the door that matches how you work.

• Google Sheets, when you have a list to fill. The sidebar pulls the profiles out of a Sales Navigator search and writes them into rows. Import LinkedIn Leads costs 1 credit per profile and runs on the free plan as well as the paid ones.
• MCP, when the question starts in a chat. Connected to Claude or any MCP client, you describe the segment in a sentence and get the rows back, which suits the moment where you are still refining who you want.
• The REST API, when the search feeds a workflow rather than a person. The same imports and enrichments run from your own code, so a saved search can become a nightly job that tops up a CRM.
• The web app, which arrives soon, for the same work without a spreadsheet in front of you.

Once the rows exist, Email Finder resolves professional addresses at 5 credits per email found, on a paid plan, and you only pay for the ones that come back. The free plan gives you 100 credits a month, which is enough to import a first hundred profiles and see what your Boolean string really caught before you spend anything on contact data.

Open a free Derrick account and run one saved search through it end to end. The comparison worth making is not tool against tool, it is the number of usable rows your string produced against the number of profiles it displayed.

We send one edition of the Derrick newsletter every two weeks, with the enrichment and outbound work we are running ourselves, including the parts that did not work. The signup form on this page asks for an email address and nothing else.

Save the search once it works

A string that survives a real list is worth keeping. Enter the query, click Save Search, name it, and Sales Navigator will keep watching it and email you the new profiles that match. It is the closest thing the platform has to a standing alert, and it means the twenty minutes you spent on brackets keeps paying after the first export.

From there, the natural next steps inside this cluster are the company search when you work account first rather than person first, and the Sales Navigator URL converter when you need to turn those results back into standard profile links.