How to write Boolean search strings for LinkedIn Recruiter

Most recruiters learn Boolean search by copying someone else's string and tweaking it. That works until it doesn't — and then you're staring at 12 results or 40,000 with no idea what went wrong.

This guide breaks down how Boolean search actually works, how to calibrate your strings for different market depths, and the mistakes that kill most searches before they start.

What Boolean search actually does

Boolean search uses three operators — AND, OR, and NOT — to combine keywords into a single query. LinkedIn Recruiter, Indeed, and most ATS platforms support them.

• AND narrows results. Every AND you add cuts your pool.
• OR widens results. It tells the engine "any of these count."
• NOT excludes. Use sparingly — every NOT removes candidates who might have been worth screening.

The mistake most recruiters make: too many ANDs, not enough ORs.

The three-tier approach

Instead of building one string and hoping for the best, build three:

Tight string — 3-4 AND clauses, narrow OR groups. You want 50-200 results. These are your best-fit candidates.

Balanced string — 2-3 AND clauses, generous OR groups. Target 200-500 results. This is your default search.

Broad string — 1-2 AND clauses, wide OR groups, minimal NOTs. Target 500-2,000 results. Use this when the talent market is shallow.

Running all three tells you whether the market is deep or thin before you waste hours refining a single string.

Common mistakes that kill your search

Too many ANDs. If you have 5+ AND operators, your Tight string is probably returning zero. Each AND is a filter — stack too many and no one passes.

Location in the string. LinkedIn Recruiter handles location separately. Putting "Houston" or "Texas" in your Boolean wastes an AND clause and reduces results because it only matches profiles with that word in the text, not the location field.

NOT overuse. Every NOT removes an entire group of people. "NOT manager" removes a Senior Engineering Manager who's hands-on and perfect for your role.

Missing synonyms. If you search for "Boomi" but the candidate's resume says "Dell Boomi" or "Boomi AtomSphere," you miss them. Use OR groups: ("Boomi" OR "Dell Boomi" OR "AtomSphere").

Template you can steal

Here's a balanced string for a Senior Software Engineer role:

("Software Engineer" OR "Software Developer" OR "Full Stack" OR "Backend Engineer")
AND ("React" OR "Angular" OR "Vue" OR "TypeScript")
AND ("Node" OR "Python" OR "Java" OR "C#")
NOT ("intern" OR "student" OR "professor")

Three AND clauses (title, frontend, backend), one conservative NOT. This will return 200-800 results depending on location filters.

Calibration matters

After running a string, check your result count: - Under 50: too tight. Remove an AND or add more ORs. - 50-500: good range. Screen the top results. - Over 2,000: too broad. Add an AND or tighten your OR groups.

The goal isn't the "perfect" string — it's finding the range where qualified candidates outnumber noise.

Try it yourself

Candid.ai's Boolean Generator builds three calibrated strings from any job description — a tight, balanced, and broad version — so you can pick based on your market depth. No more guessing.