LinkedIn Boolean Search: 5 Strings for Hyper-Targeted Leads

LinkedIn search understands five Boolean tools: AND, OR, NOT, straight double quotes, and parentheses. Type them in capitals, group every OR list in brackets, and put role logic in the Title field rather than the main keyword bar. That covers most of what makes LinkedIn Boolean search work. The rest is precision: knowing which field reads your string, which fields ignore it, and how to stop a 40,000-person result set from burying the 400 people you actually want.

The five operators, and the order LinkedIn reads them

LinkedIn evaluates a string in a fixed sequence: quotes, then parentheses, then NOT, then AND, then OR. That last position is the one that bites people.

Take VP Sales OR Head of Sales SaaS. You meant "either title, at a SaaS company." LinkedIn reads it closer to "VP and Sales, or Head and of and Sales and SaaS." Two different searches glued together.

Here is what each tool does:

• Quotes ("VP of Sales") force an exact phrase. Without them, words can appear anywhere on the profile in any order. Use straight quotes. Curly quotes pasted from a doc get ignored.
• Parentheses group terms so OR lists stay contained: ("VP Sales" OR "Head of Sales").
• NOT excludes the term or group immediately after it. NOT (intern OR assistant) drops both.
• AND requires both sides. A plain space between words is treated as AND, but writing it out makes strings easier to debug later.
• OR accepts any of the options. This is how you handle title sprawl, since one company's "Head of Revenue" is another's "VP Sales."

There are no wildcards. found* does nothing useful. Spell out founder OR "co-founder" OR cofounder, because LinkedIn treats the hyphenated and unhyphenated versions as different tokens.

Free search vs. Sales Navigator: where Boolean actually works

The operators are identical across both products. What differs is which boxes accept them and what you can combine them with.

Two mechanics matter here.

First, the keyword bar searches the entire profile. "VP of Sales" in the keyword bar returns someone who held that title in 2015 and now runs a bakery. The Title field reads the job title instead, which is almost always what you want for role targeting. Keywords are for context: industry terms, tech stack, stage.

Second, Sales Navigator picklists follow their own implicit logic. Multiple values inside one filter are OR'd together; different filters are AND'd. Selecting "Director" and "VP" under seniority means either. Adding a headcount band on top means both conditions apply. You don't type operators there, and trying to fake firmographics with keywords ("51-200 employees") is a waste when the filter exists.

Free search has a ceiling worth knowing about. Search heavily on a free account and LinkedIn applies its commercial use limit, cutting off results until the next month. If prospecting is a weekly job, that limit alone justifies Sales Navigator. For more on stacking its filters, see Sales Navigator Search Tricks That Actually Fill Pipe.

Five LinkedIn Boolean search strings for common ICPs

Each string is split by field. Paste the title portion into the Title box and the keyword portion into the keyword bar. Then add geography and, in Sales Navigator, seniority or headcount on top.

1. B2B SaaS VP Sales

Title:

("VP Sales" OR "VP of Sales" OR "Vice President of Sales" OR "Head of Sales" OR "VP Revenue") NOT (intern OR assistant OR associate OR former)

Keywords:

SaaS AND (B2B OR "software as a service" OR "subscription software")

Excluding "associate" removes the Associate VP inflation common in banking. If you sell to sales leaders specifically, LinkedIn Outreach for B2B SaaS: A Founder Playbook covers what to say once you've found them.

2. Series A fintech founder

Title:

(founder OR "co-founder" OR cofounder OR CEO) NOT (investor OR "venture partner" OR advisor OR "board member")

Keywords:

(fintech OR payments OR lending OR "embedded finance" OR neobank) AND ("Series A" OR "seed round" OR "backed by")

Funding stage isn't a profile field, so this only catches founders who mention it in their headline or about section. That's a smaller pool, but it skews toward people who talk publicly about the raise, which is a decent signal.

3. Performance marketing agency owner

Title:

(founder OR owner OR "managing director" OR CEO OR partner)

Keywords:

agency AND ("performance marketing" OR "paid media" OR PPC OR "paid social") NOT (freelance OR freelancer OR "looking for")

The NOT freelance clause separates agencies with staff from solo operators with "agency" in their headline.

4. Startup talent leader (buying recruiting tools)

Title:

("Head of Talent" OR "Talent Acquisition Lead" OR "Head of People" OR "VP People" OR "Director of Talent")

Keywords:

(startup OR scaleup OR "Series B" OR "Series C") NOT ("executive search" OR "recruitment agency" OR staffing)

Excluding staffing firms matters because agency recruiters use near-identical titles and will never buy an in-house tool.

5. Engineering leader at infrastructure-heavy companies

Title:

(CTO OR "VP Engineering" OR "VP of Engineering" OR "Head of Engineering" OR "Head of Platform")

Keywords:

(kubernetes OR "platform engineering" OR devops OR SRE) NOT (consultant OR contractor OR freelance)

Tech stack terms work well as keywords because engineers list them in skills and role descriptions.

Debugging a string that returns garbage

Results too broad? The usual culprit is an OR group without parentheses, so the OR is swallowing everything to its right. Add brackets and rerun.

Too narrow means you have probably over-quoted. "Vice President of Sales" misses "Vice President, Sales" because the comma breaks the exact phrase. Add the variant to the OR list.

Build in layers. Start with the title group alone and scan the first page. Add one keyword clause, scan again. Add exclusions last, only for patterns you actually see in the results. A NOT clause written from imagination often removes good leads you didn't anticipate.

And save the string somewhere outside LinkedIn. Free search won't keep it, and you'll want to rerun it in a month.

Turning a tight search into conversations

Here is the arithmetic that should shape how tight your strings are. Ampliflow sends 25 connection requests per LinkedIn account per day on every paid plan, which tracks the conservative pacing LinkedIn tolerates. A 2,000-person result set therefore takes 80 working days to work through. A sharp string that returns a few hundred highly relevant people gets you to the end of the list, and to real feedback on your messaging, in weeks.

So we would argue for precision over volume every time. Narrow the string until you'd be comfortable personalising the first line for anyone on page one.

Once the list is right, Ampliflow imports it directly from LinkedIn search or Sales Navigator. You connect your account with one click through the Chrome extension, and from there campaigns run in the cloud via the Unipile API, not in your browser, so your laptop can be closed. The workflow builder lets you branch with If/Else logic (did they accept, did they reply) and add delays, while sends go out with randomised timing jitter during the working hours you configure. Auto-pause on reply stops the sequence the moment someone answers, and real-time safety scoring flags anomalies before they become restrictions. For sequencing, Designing an Outreach Cadence That Gets Replies goes deeper.

On cost, be clear-eyed. Linked Helper starts at $15/mo and Octopus CRM at $9.99/mo, both cheaper than Ampliflow's Standard plan at $19/mo for founding members ($39/mo regular). If price is the only criterion, those win. Ampliflow's case is architecture: cloud execution, account safety scoring and human-like limits, against tools like Dripify at $79/mo or Expandi at $99/mo. Plans and per-account message and profile view limits are on the Pricing page, and every plan starts with a 7-day free trial.