Sourcing guide
Boolean Search String Generator for Recruiters
Paste a job description and get ready-to-paste Boolean strings for LinkedIn X-Ray, Naukri RMS, Indeed, your ATS, public CVs, and Bing — one correct dialect per platform, plus the operator rules and answers below.
Senior FP&A Manager — 8+ years. CA or CFA.
Strong financial modeling and variance analysis.
SAP FICO or Oracle ERP. P&L exposure. Bengaluru.
("FP&A Manager" OR "Financial Planning Manager") AND ("financial modeling" OR "variance analysis") AND (CA OR CFA) AND (SAP OR "Oracle ERP") AND Bengaluru
title("FP&A Manager" OR "Financial Planning Manager") AND skill("financial modeling") AND skill(SAP) AND exp(8) AND location(Bengaluru)
site:linkedin.com/in/ ("FP&A" OR "financial planning") AND (CA OR CFA) AND (SAP OR "Oracle ERP") AND "Bengaluru"
6
dialects
42
profiles
86%
avg readiness
How the generator works
- 1
Paste the job description
Paste the hiring manager's JD. The parser lifts the role cluster, credentials, tools, and locations — for example: Senior FP&A Manager, CA or CFA, SAP FICO, Bengaluru.
- 2
Get one string per platform
The generator writes a separate Boolean string for each dialect: plain Boolean for your ATS, site:linkedin.com/in/ for Google X-Ray, title() and skill() field codes for Naukri RMS, title:(...) for Indeed, and Bing-safe syntax with inbody:.
- 3
Paste into the platform and screen
Paste each string into its own search box, run the searches, then bulk-screen the resumes against the role bar to build a ranked shortlist.
Boolean operators recruiters should know
| Operator | What it does | Example |
|---|---|---|
| AND | Requires both terms | CA AND SAP |
| OR | Accepts either term | ("Legal Counsel" OR "Corporate Counsel") |
| AND NOT | Excludes a term (ATS-safe) | MBA AND NOT "MBA Fresher" |
| "quotes" | Exact-phrase match | "Financial Modeling" |
| ( ) | Groups alternatives | (SAP OR Oracle ERP) |
| site: | Restricts Google to one site (X-Ray only) | site:linkedin.com/in/ |
| title() | Naukri RMS title field | title("FP&A Manager") |
| title:() | Indeed title filter | title:("Finance Manager") |
One brief, six dialects
A string that works in one search box can silently return nothing in another. Each platform gets its own syntax — never mixed.
Plain Boolean only. Quoted phrases, uppercase operators, max two nesting levels. No site:, no field codes.
Leads with site:linkedin.com/in/. Google operators allowed; exclusions as -term or NOT.
Leads with title(...). Field codes only: skill(), company(), location(), exp(). No Google operators.
Leads with Indeed's title:(...) filter, then plain Boolean. No Google operators.
Targets public CV documents: intitle:resume variations plus filetype:pdf OR filetype:doc.
Leads with site:linkedin.com/in/ and uses inbody:. Exclusions with NOT, never Google minus-operators.
Boolean search FAQs
What is a Boolean search string?
A Boolean search string combines job titles, skills, and exclusions with the operators AND, OR, and NOT, plus quotation marks for exact phrases and parentheses for grouping. Recruiters paste it into LinkedIn, Naukri, Indeed, an ATS, or Google to return only profiles that match the logic — for example: ("FP&A Manager" OR "Financial Planning Manager") AND (CA OR CFA).
How do I write a Boolean string for LinkedIn?
Use uppercase AND, OR, and NOT, wrap multi-word titles in quotes, and group OR alternatives in parentheses. Paste it into the LinkedIn search bar or the Recruiter keywords field. LinkedIn does not support wildcards or the site: operator. For public profiles beyond your network, use a Google X-Ray string starting with site:linkedin.com/in/ instead.
What does a Naukri RMS Boolean string look like?
Naukri RMS uses field codes instead of plain keywords: title() for job titles, skill() for skills, plus company(), location(), and exp(). A typical string is title("FP&A Manager") AND skill("financial modeling") AND exp(8) AND location(Bengaluru). Google operators like site: never belong in a Naukri string.
Can I use the same string on every platform?
No — each platform documents its own syntax, and a string that works in one box can silently return nothing in another. ATS search needs plain Boolean with no Google operators; Google X-Ray needs site: and minus exclusions; Naukri needs field codes; Indeed needs its title:(...) filter; Bing X-Ray needs inbody:. One brief should produce one string per dialect.
What are the ATS-safe Boolean syntax rules?
Quote every multi-word phrase, use uppercase AND, OR, and NOT (AND NOT for exclusions), wrap every OR group in parentheses, never nest more than two levels deep, and keep Google operators and field codes out of ATS strings. Most ATS parsers choke on deep nesting and unknown operators.
Is this Boolean string generator free?
No. Recruiting AI sells monthly plans starting at $9 for 500 AI actions — the generator, JD import, bulk screening, and outreach are all included in every plan, with no auto-renewal. Free generators typically write a single dialect and stop at the string; this pipeline continues into screening and shortlisting.
Generate your first six strings tonight.
Open a workspace, paste a JD, and screen the first pipeline — plans from $9/mo, no auto-renewal.