Boolean Search Cheat Sheet for Recruiters (Word)

What's Included in This Boolean Search Cheat Sheet

A Boolean search string tells a search tool exactly who to find. Built well, it saves hours of scrolling. Built badly, it returns thousands of profiles or none at all. This Word file puts everything you need on a few pages: the operators, a builder and 12 ready-to-adapt strings for roles that recruiters in Germany, Austria and Switzerland search for every week.

1. The operators on one page: AND, OR, NOT, quotation marks, brackets and capitals, each with an example and the usual catch.
2. Google X-Ray commands: site:, intitle:, inurl:, filetype:, the minus sign and the wildcard, for searching public profile pages through a web search.
3. A builder in four steps: title synonyms, must-have skills, location and exclusion, in one formula you can reuse for any role.
4. 12 search strings: backend engineer, data engineer, DevOps, product manager, intensive care nurse, industrial electrician, plumbing and heating technician, field sales, SaaS account executive, controller, performance marketing manager and site manager. Titles come in German and English.
5. Count and sharpen: what to change when a search returns thousands of results, almost none or the wrong ones.
6. Seven typical mistakes and a short legal overview: Art. 14 GDPR, legitimate interest, sensitive data and Section 7 UWG for email and phone.

Key Features That Save You Time

• German and English titles in one string. In the DACH region the same role has several names. Every string covers them, including masculine and feminine forms.
• Spelling variants built in. Umlaut spellings (Köln, Koeln, Cologne) and common alternatives are part of the examples, so you do not miss people because of a letter.
• A must-have and nice-to-have logic. AND is for what has to be there, OR is for synonyms and extras. The builder makes you decide this before you type.
• A funnel table. Thousands of results, very few results, many but wrong ones: for each case there is one thing to change.
• A legal row you can show your data protection officer. Information duty, legal basis and the channel rules in plain wording, with the sources.

How to Use This Boolean Search Cheat Sheet

1. Write down the role and its must-have criteria in plain words before you type anything.
2. Build the string in the four steps: titles, must-have skills, location, exclusion. Start with the broad version.
3. Run it and read the number of results. Use the funnel table to widen or narrow it.
4. Read a sample of 20 profiles. Find the term that lets the wrong ones in and fix it there.
5. Save the final string with date and tool, and record where the profiles came from. You will need that for information and deletion requests.

Why This Boolean Search Cheat Sheet Works

The most common mistake in searching has nothing to do with syntax. In our conversations with recruiting teams, the typical error is to treat a requirement as a nice-to-have when it is really a must-have, or the other way round. In a Boolean string that is the difference between an AND and an OR. The builder in this file forces the decision first, and the strings show how it looks in practice.

Boolean is precise, but it is manual work: collect synonyms, count brackets, read the result, sharpen. That is why many teams use it next to other methods. If you want to see how it compares with describing a role in plain language, read Boolean search versus requirement search or Boolean search versus natural language in recruiting. Our own coverage test runs a filter search (LinkedIn Sales Navigator) next to free-text requirement searches; the method is public on the benchmark page.

The legal part is deliberately short but concrete. A search string only finds data. As soon as you save a profile or write to a person, Art. 14 GDPR asks you to inform them, at the latest after one month or at first contact. For the full picture, see our guide to active sourcing under the GDPR.

A Closer Look: Building One String From Scratch

Take a nurse search in Hamburg. Step 1 gives the titles: (Pflegefachfrau OR Pflegefachmann OR Pflegefachkraft OR "Gesundheits- und Krankenpfleger" OR "Registered Nurse"). On its own this returns a huge list, because it contains every nurse.

Step 2 adds the must-have: AND (Intensivpflege OR Intensivstation OR "Intensive Care"). Now only people with intensive care in their profile remain, and the OR inside the brackets catches the different spellings.

Step 3 adds the location: AND (Hamburg OR Norddeutschland). Step 4 is optional. If trainees and students show up, add NOT (Auszubildende OR Praktikant). Count the results after every step. If one step removes almost everything, that term was too strict for a must-have, and it probably belongs in the OR group.

The same four steps work for every string in the file. What changes is the vocabulary: in a trade the titles are many and the skills few, in IT the titles are fewer and the skills decide.

Who Should Use This

• Recruiters and sourcers who build strings every day and want a clean, shared standard.
• Agency recruiters who switch between industries and need a starting string for each role.
• HR generalists who source occasionally and do not want to learn every operator by trial and error.
• Teams that onboard new sourcers and want one page they can hand over on the first day.

If you would rather not maintain strings by hand, take a look at an active sourcing tool that works from a plain-language description of the role.

FAQs

What is a Boolean search string?

It is a search query that combines terms with the operators AND, OR and NOT, quotation marks and brackets. It lets you describe a profile precisely, for example a data engineer with Python and Airflow in Hamburg, and exclude what you do not want.

Do operators have to be written in capitals?

In most tools, yes. Lowercase and, or and not are treated as ordinary search words. Write them in capitals and check how your tool behaves.

Does the same string work in every tool?

No. Operators, length limits and the handling of brackets differ by tool. The strings in the file are starting points. Test each one in your tool and adjust.

Is searching public profiles through Google allowed?

Searching public web pages is a technical matter. What counts legally is what you do with the data: inform the person, have a legal basis and delete on time. Platforms may also restrict systematic collection in their terms, so check them. This is not legal advice.

How many results should a good search return?

There is no fixed number. As a rule of thumb, thousands of results mean the search is too broad, and fewer than about 30 mean it is too narrow. What matters is how many of the first 20 profiles fit.

How do I handle German and English titles in one search?

Put both in the same OR group, for example (Softwareentwickler OR "Software Engineer" OR "Backend Developer"). In the DACH region many profiles are written in English even when the person works for a German company, and many German-language profiles use German titles. Covering both costs nothing and avoids a blind spot. Add masculine and feminine forms where they differ, such as Entwickler OR Entwicklerin.

Should I save my strings?

Yes. Keep a small library with the role, the string, the tool, the date and the number of results. A saved string with its result count tells you six months later whether a market has moved, and it gives new colleagues a head start.