How to build and review a recruiter Boolean search

Updated Oct 22, 2026 · 5 min read

A useful recruiting search expresses the role's requirements clearly. AIIA's free Boolean builder turns fields you can review into a broad query and a narrow query. The final strings are compiled from those fields. A model does not decide their syntax.

Separate required skills from preferences

Enter a role title and the skills that must appear. Put preferences in the optional-skills field, and add title alternatives only when you want to include them. A suggested title is not an established equivalent of the original role. Check it against the scope you are hiring for.

You can use a job description to suggest field values. Review those suggestions before compiling a query. The model may misunderstand an ambiguous description. Suggestions never include exclusions: removing people from every search you run is your decision, so you enter exclusions by hand. Manual fields remain available when model generation is unavailable, and manual query compilation does not need a model call.

A synthetic example

For a fictional data role, Python and SQL might be required while Tableau is optional. Both queries must retain Python and SQL. The narrow query can also require Tableau. Removing SQL to make the search broader would change the requirement, so that decision belongs to you.

Choose the search surface

LinkedIn's main search bar documents uppercase AND, OR and NOT, along with quotation marks and parentheses. Google Search uses quotes for exact phrases, site: for a site restriction, and a minus sign for exclusions. The builder's Google adapter deliberately uses only that conservative, documented set, with no OR and no parentheses, so title alternatives are shown as suggestions to substitute manually rather than inserted into the query.

Google X-ray queries look for indexed public LinkedIn profile pages through Google. They do not search LinkedIn's private data. The LinkedIn keyword mode targets the main LinkedIn.com search bar. It does not promise compatibility with every plan or every filter field. LinkedIn may limit complex consumer queries.

How do you use Boolean search in Google for recruiters?

To use Boolean search in Google, put exact job titles in quotes, join alternate titles with an uppercase OR, exclude words with a minus sign, and add site: to search one website such as LinkedIn or GitHub. Then combine the pieces in one string.

• Quotes find an exact title or phrase, such as "data analyst".
• An uppercase OR joins synonyms or alternate titles, such as "data analyst" OR "business analyst".
• A minus sign leaves out words you do not want, such as -jobs or -careers.
• site: limits the search to one website, such as site:linkedin.com/in for public LinkedIn profile pages, or a GitHub, resume or portfolio site.
• Combine site, titles, skills, location and exclusions in one string, then read the first results and adjust.

A fictional example is site:linkedin.com/in "data analyst" Python SQL London -jobs. It looks for public LinkedIn profile pages that mention a data analyst, Python, SQL and London, and leaves out pages that contain the word jobs. Google only searches pages it has indexed, so it will not find every profile. The builder's Google query uses quotes, site: and minus signs only, so add any OR alternatives by hand and recheck the string before you search.

Three mistakes spoil most Google searches for candidates:

• Writing the word OR in lowercase. Google treats lowercase or as an ordinary word, so use uppercase OR.
• Leaving out the quotes around a title with several words, which lets Google match those words anywhere on the page.
• Excluding too many words. A minus sign can remove a relevant profile because the word appears in an old job or an unrelated section.

Review exclusions and location

Check every exclusion. Excluding a required skill, an optional skill, or a title alternative creates a contradiction, and the builder rejects generation until you resolve it rather than silently dropping or changing a field. An exclusion can also remove a relevant profile because a word appears in an old job or an unrelated section. The builder cannot tell you how many results a query will return.

Use LinkedIn's location filters for location constraints rather than treating a place name anywhere in a profile as current residence. Google location terms are text matches and have similar limitations. Very restrictive searches may need you to review which requirements are truly necessary.

Copy a reviewed query

Read the term explanations, edit the query if necessary, and copy the version you want to use. The builder does not run searches, scrape profiles, bypass login or collect candidate data. If you manually edit a compiled query, check its grouping and required skills again before searching.

Manual compilation happens in the browser and works even when the free tools are otherwise unavailable. Optional description-based suggestions use AIIA's model provider within the stated allowance. Remove confidential information before using that option. Reset clears the inputs and results held on the page.