Boolean sourcing: the skill to showcase on your recruiter CV

"Proficient in LinkedIn Recruiter and Boolean search." That line appears on a lot of recruiter CVs, and it says almost nothing. Everyone has typed "java AND developer" at some point. What a Head of Talent wants to know is whether you can build a search that surfaces the right people in a candidate-short market, adapt it from one tool to another, and turn a list of results into candidates actually met. Here is how to present this skill credibly, with the right vocabulary, sample search strings and before/after CV lines, with a focus on recruiting in France.

What Boolean sourcing really covers

Boolean search means combining keywords with logical operators to filter a database of profiles. The basic operators are well known:

• AND: both terms must appear.
• OR: either term, useful for synonyms and alternative job titles.
• NOT (or the minus sign on Google): exclude a term.
• Quotation marks: search for an exact phrase, such as "management accountant".
• Parentheses: group alternatives to control how the string is read.

On LinkedIn Recruiter, operators are written in capitals. On Google, AND is implicit and exclusion uses the minus sign. These differences look trivial, but a recruiter who knows them saves a great deal of time.

The real skill lies elsewhere: turning a vague need into a search. A manager asking for "a good back-end dev" gives you no language, no framework, no seniority. Boolean sourcing starts with translating that need into keywords, synonyms and exclusions. In France, it also means searching in two languages, since many profiles mix French and English job titles.

Three levels of mastery, and how to tell them apart on a CV

Level 1: keyword search inside one tool

You use LinkedIn Recruiter filters or a job board's CV database with a few operators. Most recruiters are here. On a CV, don't present it as a distinctive skill: just name the tool.

Level 2: structured, reusable search strings

You build structured strings with synonym groups and deliberate exclusions, and you save them to reuse by job family. A sample string for an industrial management accountant role in France:

("contrôleur de gestion" OR "controller" OR "business controller" OR "contrôle de gestion") AND (industrie OR usine OR "site de production" OR manufacturing) NOT (stage OR stagiaire OR alternance OR alternant)

At this level, you also understand why a string returns too many or too few results, and how to tighten it.

Level 3: multi-platform sourcing (X-ray, communities, open sources)

You go where the profiles are, not only LinkedIn. X-ray search uses Google to query a specific site:

site:linkedin.com/in ("data engineer" OR "ingénieur data") (Spark OR Databricks) Lyon -recruteur -recruiter

For technical profiles, you also explore GitHub (repositories, languages used), specialist communities, speaker lists from meetups and conferences, and alumni directories. This level is what makes the difference for hard-to-fill roles, and it is covered in detail in the article on the tech recruiter CV.

How to write this skill on your CV

In the skills section: precise, not decorative

A skills section is not where you prove anything, but it must be accurate. Rather than an isolated keyword, name the environments.

Before: "Sourcing, boolean search, LinkedIn"

After: "Sourcing: advanced Boolean strings (LinkedIn Recruiter, job board CV databases), Google X-ray search, GitHub sourcing, talent pool management in the ATS"

In your experience: the outcome of sourcing, not the tool

The proof sits in your experience lines. Your reader wants to know what your technique produced: how many profiles identified, what response rate, how many hires from direct sourcing.

Before: "Sourced candidates via LinkedIn and Boolean search."

After: "Built a pool of 180 process engineers in 6 weeks using X-ray search and LinkedIn Recruiter strings; 9 of the year's 14 hires came from this pool."

Before: "Direct approach for scarce profiles."

After: "Sourced embedded C/C++ developers outside LinkedIn (GitHub, open source communities): 35% positive replies to outreach messages, 4 hires with no agency involved."

Take a fictional profile: a recruiter with 2 years' experience at a mid-sized IT consultancy (an ESN, in French terms). He wrote "Searched for consultants on LinkedIn". Better:

"Built a library of 25 Boolean strings by skill (SAP FI/CO, Salesforce, Java/Spring) shared with a team of 4 recruiters, cutting the prep time for each new search."

That last line works because it shows a skill passed on, not just practised. You can try these phrasings directly in the CV editor to see how they sit on the page.

Metrics that prove good sourcing

• Response rate to outreach messages: it reflects how accurate your targeting is as much as the quality of your message.
• Share of hires from direct sourcing: the most solid metric for a manager.
• Size and use of your talent pool: how many qualified profiles, and how many were re-contacted for later roles.
• Agency fees avoided: to phrase carefully, and only if the information is not confidential.

The article on recruiter KPIs for your CV explains how to write each of these numbers.

The legal framework: a point that sets you apart

A recruiter who sources knows they are handling personal data about people who never asked to be contacted. Showing you understand the rules is a real sign of maturity, especially for a role in a large group.

• The GDPR applies to sourcing. When data is not collected from the person directly, Article 14 requires informing them within a reasonable period and at the latest within one month of collection, or at the first contact.
• The CNIL, France's data protection authority, has published a reference framework for data processing in recruitment, which notably sets out retention periods for candidate data.
• The French Labour Code restricts what can be asked of candidates: Article L1221-6 requires information to have a direct and necessary link with the role, and Article L1221-9 prohibits collecting information about a candidate through a method they were not made aware of.
• Non-discrimination (Article L1132-1 of the Labour Code) prohibits filtering searches by age, origin, sex or other protected criteria. A string that excludes graduation years to target an age bracket is a problem, not a trick.

On a CV, one line is enough:

"Configured talent pool retention periods in the ATS in line with the CNIL recruitment framework and built a GDPR notice into outreach sequences."

Mistakes that weaken the "sourcing" line on your CV

• Listing the operators ("AND, OR, NOT") as a skill. It is like putting "Ctrl+C" under office software.
• Quoting messages sent rather than replies and hires. "1,200 InMails sent" can also read as loose targeting.
• Leaving out the roles you source. Field sales reps and cybersecurity engineers don't live in the same places: say which job families you are effective on.
• Presenting scraping or automation tools without nuance. Some data extraction practices breach platform terms of use or the GDPR. If you use browser extensions or enrichment tools, mention them with their usage framework.
• Claiming expert level without an example. In an interview, you may be asked to write a string on the whiteboard for a given role. Practise.

Preparing for the interview question

Many interviews for sourcer or talent acquisition partner roles include an exercise: "Here is a job description, how would you search?" The expected answer follows four steps:

1. Clarify the need: must-have skills, learnable skills, possible job titles at competitors.
2. List synonyms and variants: titles in French and English, abbreviations, names of tools or certifications.
3. Choose sources: LinkedIn, specialist job boards, GitHub, communities, schools.
4. Test and adjust: read the first 20 results, spot false positives, refine exclusions.

If you are coming from another field and want to show this reasoning without recruiting experience, the article on switching careers into recruitment suggests ways to present it.

Put your skill on paper

The pre-filled talent acquisition CV already has a structured skills section and sourcing-oriented experience lines: all that is left is adding your own strings, job families and results. Open the pre-filled Talent Acquisition CV.

Frequently asked questions

Is Boolean sourcing still useful with AI-assisted search tools?

Yes. Natural-language search tools built into platforms help you get started, but a recruiter must understand why a profile does or doesn't show up, and be able to take back control when results are too broad. Boolean logic remains the basis of that control, and it works everywhere, including Google and ATS databases.

Do I need a certification to list Boolean sourcing on my CV?

No. Courses and certifications exist, and you can mention one if you have it, but the most convincing proof is a result: a talent pool built, hires from direct sourcing, a string library shared with your team.

Where should this skill go on the CV?

In the skills section, under a detailed "Sourcing" line, and above all in one or two experience lines that show its outcome. If you are targeting a dedicated sourcer role, it can also appear in your summary.

How do I talk about sourcing if my company mostly received inbound applications?

Focus on what you did for the difficult roles, even if there were few. A single hire of a scarce profile through direct approach, well described, demonstrates the skill. You can also highlight re-screening older applications in the ATS, which relies on the same search logic.

Is X-ray search legal?

Querying Google with search operators is. What is regulated is how you use the data you find: informing the person, retention periods, use limited to recruitment. Large-scale scraping, on the other hand, may breach the terms of use of the sites concerned.