Build Boolean search strings for a recruiting or research search. Treat the search as a recall-and-precision problem: start broad enough to find qualified people with nontraditional titles, then provide controlled narrowing options. Follow applicable company policy and do not use protected characteristics, proxies for them, or discriminatory exclusions. Search brief: - Target role and level: [TARGET ROLE] - Must-have capabilities: [MUST HAVE CAPABILITIES] - Helpful but optional capabilities: [PREFERRED CAPABILITIES] - Titles, adjacent titles, and terminology: [TITLE AND TERM NOTES] - Geography, work authorization, or other policy-approved constraints: [APPROVED CONSTRAINTS] - Search platform and character limits: [SEARCH PLATFORM]
Produce four items: 1. A core Boolean string using title and skill concept blocks. 2. A broader discovery string designed to surface adjacent backgrounds. 3. A narrower string that adds only job-related preferred criteria. 4. A readable logic map showing each synonym group and why it is included. Use parentheses correctly, quote multiword phrases only when that improves precision, and avoid arbitrary exclusions such as “junior,” “assistant,” or employer names unless I explicitly authorize them and they are job-related. If the platform has different Boolean behavior, adapt syntax and state the assumption. Include a testing plan: review the first 25 results, identify false positives and false negatives, change one concept block at a time, and log the revision. Provide a short fairness and policy note identifying any input that could create an inappropriate restriction. Do not claim a candidate is qualified based on keywords alone. Ask up to 3 clarifying questions only if a required input is missing. Before answering, validate balanced parentheses and ensure every exclusion is supported by the stated job requirements or approved constraints.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TARGET ROLE] | State the job title, seniority, and the work the person will perform. | Senior data analyst for a retail planning team, responsible for forecasting and executive reporting. |
| [MUST HAVE CAPABILITIES] | List the job-related skills, experience, tools, or domains required for the role. | SQL, dashboarding, demand forecasting or inventory analytics, and experience presenting findings to business partners. |
| [PREFERRED CAPABILITIES] | List job-related qualifications that are useful but not required. | Python, Snowflake, Looker, and consumer retail experience. |
| [TITLE AND TERM NOTES] | Provide known title variants, acronyms, product terms, and adjacent-role ideas. | Data analyst, business intelligence analyst, analytics consultant, decision scientist, planning analyst; include BI and business intelligence. |
| [APPROVED CONSTRAINTS] | Enter only policy-approved constraints such as location, work arrangement, or language requirements tied to the role. | United States; hybrid in Chicago or remote within approved hiring states. |
| [SEARCH PLATFORM] | Name the site or database where the Boolean query will run and any known limits. | LinkedIn Recruiter; use its standard Boolean title and keyword fields. |
How to use
- Paste the approved job requirements and platform details, including title variants you have already seen in the market.
- Run the core string and inspect the first 25 results for relevance, seniority, and missing adjacent titles rather than judging only the total count.
- Use the discovery string to find terminology candidates use, then add only job-related terms that improve the search.
- Follow up with: “Based on these 25 anonymized result summaries, identify false-positive patterns and revise one Boolean block at a time.”
Variations
Candidate X-ray
Use this when a platform search is limited and you need a web search.
Create a Google X-ray Boolean search for candidates on [TARGET SITE]. Role: [ROLE]. Required skills: [REQUIRED SKILLS]. Title variants: [TITLE VARIANTS]. Approved location constraints: [APPROVED LOCATION RULES]. Return three copyable queries using site: syntax, quoted phrases only where appropriate, and grouped synonym blocks. Explain which terms may reduce recall. Do not use protected traits, personal contact data, or demographic proxies. Add a first-page review checklist for relevance and false negatives. Ask up to 3 questions only if an input is missing. Validate parentheses and confirm every constraint is job-related before answering.
Talent market map
Use this when researching the market before opening a requisition.
Create Boolean searches to map the talent market for [ROLE FAMILY] in [APPROVED REGION]. Core capabilities: [CAPABILITIES]. Known title variants: [TERMS]. Platform: [PLATFORM]. Produce a broad search, an industry-focused search, and a skills-focused search, plus a table explaining each concept block. Flag title terms likely to be ambiguous and suggest a manual sample-review process. Do not infer candidate quality from profiles or introduce demographic filters. Ask up to 3 clarifying questions only if required inputs are missing. Check syntax and identify any constraint not directly supported by the brief.
Search refinement
Use this after an initial Boolean search returns poor results.
Diagnose and improve this Boolean search: [CURRENT STRING]. Target role: [ROLE REQUIREMENTS]. Examples of relevant results: [RELEVANT EXAMPLES]. Examples of irrelevant results: [IRRELEVANT EXAMPLES]. Platform: [PLATFORM]. Explain likely recall and precision problems, then provide a revised core string and one alternate test string. Change one logic block at a time and label each change. Preserve job-related inclusion criteria; do not add protected-characteristic proxies or unsupported exclusions. Ask up to 3 questions only if necessary. Before answering, check balanced parentheses and explain any platform-specific syntax assumption.
Tips
- Build title and capability blocks separately so you can learn whether poor results come from terminology, skills, geography, or a combination.
- Treat optional skills as a later narrowing layer; putting every preference in the first query often hides qualified people with adjacent backgrounds.
- Review false negatives deliberately by searching for people who are known to be relevant, then noting the titles and terms your query missed.
- Record query versions and samples reviewed, because result-count changes alone do not tell you whether quality improved.
FAQ
Are Boolean strings the same on every recruiting platform?
No. Operators, title-field behavior, and character limits vary, so check the platform documentation or test a small query before scaling it.
Can I exclude titles to remove junior candidates?
Use caution. Titles are inconsistent, and broad exclusions can remove qualified people; rely first on role-relevant experience and manually inspect samples.
Does a keyword match prove someone is qualified?
No. It is a sourcing signal, not an assessment. Evaluate evidence of relevant work through your normal, consistent hiring process.