BlogCraft
LinkedIn boolean search: the strings that actually find people
LinkedIn boolean search accepts AND, OR, NOT, quotes and parentheses, with no wildcard. Ready strings for Java and DevOps roles, and what they miss.
Contents
- Which operators does LinkedIn boolean search actually support?
- What changes between a free account and Recruiter?
- What string finds a senior Java developer?
- What string finds a DevOps engineer?
- How do you run an X-ray search with Google?
- Why does a boolean search miss candidates?
- Does semantic search replace boolean?
- Where do you start on Monday?
A LinkedIn boolean search that actually finds people takes little syntax and a lot of vocabulary: AND, OR and NOT in capitals, quotation marks around phrases, parentheses around every group of synonyms, and every way a developer might have described their own job. The syntax takes ten minutes to learn. The vocabulary is what decides the result, because LinkedIn accepts no wildcard and guesses nothing.
What follows rests on LinkedIn’s own help pages rather than on the cheat sheets that circulate, and several of those cheat sheets get one thing wrong that matters: the order in which operators are read. We finish with what boolean will never find, and with what makes up for it.
Which operators does LinkedIn boolean search actually support?
Five elements and nothing else: AND, OR, NOT, quotation marks and parentheses. LinkedIn’s help page states that the three operators must be typed in uppercase, that quotes search for an exact phrase and that parentheses group terms together.
What is not supported matters just as much, because that is where habits formed on Google or in an
ATS let you down. The asterisk is not a wildcard on LinkedIn: the page lists it among unsupported
symbols, along with braces, square brackets and angle brackets, which are read as ordinary
characters. The + and - signs “may appear to work in some cases”, LinkedIn writes, but they are
not officially supported, and the help page recommends AND and NOT instead. A string that relies on
develop* or -intern therefore relies on behaviour nobody guarantees.
The point most guides leave out is precedence. LinkedIn reads quotes first, then parentheses, then
NOT, then AND, and OR last. In practice, Java OR Kotlin AND Spring does not search for “Java or
Kotlin, with Spring”: it searches for Java OR (Kotlin AND Spring), meaning every profile that
mentions Java, Spring or not. The practical rule follows from it: every group of ORs goes inside
parentheses, always, even when you think the order does not matter.
Then there are stop words. LinkedIn drops words such as “by”, “in” or “with” from searches, and the
Recruiter help gives the example of “after sales”, which returns profiles containing only “sales”.
That is one more reason to put quotes around any phrase of several words, and it is also why a
lowercase and does nothing useful: it is on that list.
What changes between a free account and Recruiter?
A free account understands the same syntax, but it is limited in volume and in fields, and the volume limit is the one a recruiter runs into first.
LinkedIn applies a commercial use limit to free accounts: past a certain number of profile searches in the month, the activity “indicates that you’re likely using LinkedIn for commercial use, like hiring or prospecting”, and search is restricted. The counter resets on the 1st of every month at midnight Pacific time. LinkedIn says it cannot display how many searches you have left, that the limit cannot be lifted on request, and that a warning may not appear if the allowance is used up too quickly. Every precise figure circulating about that threshold therefore comes from anecdote, not from LinkedIn.
What counts and what does not is worth knowing. Profile searches on the site and the app count, as does browsing through the People Also Viewed section or the People tab of a company page. A name search in the top bar, browsing your first-degree connections and searching for jobs do not count. Premium Business, Recruiter Lite and Sales Navigator raise the cap, without the help page ever calling it unlimited.
Recruiter and Recruiter Lite mostly change the structure of the search. Boolean and quotes work separately in the Job titles, Companies and Keywords fields, and several filters offer a “Must have”, “Can have”, “Doesn’t have” menu that is equivalent to AND, OR and NOT. The help page also warns that a boolean query stacking too many facets “can cause a search result issue”, and recommends moving part of the string into the dedicated filters. The Project filter does not accept boolean at all.
What string finds a senior Java developer?
A string in two parts, the more important being the job titles, because that is where the vocabulary of French IT services firms drifts furthest from the vocabulary of job ads.
In Recruiter, the Job titles field takes the variants of the role, in French, in English and in the feminine:
(développeur OR développeuse OR developer OR "ingénieur logiciel" OR "ingénieure logiciel"
OR "software engineer" OR "ingénieur études et développement" OR "tech lead" OR "lead developer")
The Keywords field takes the technical side, each family inside its own parentheses:
(Java OR "Java EE" OR J2EE OR "Spring Boot") AND (microservices OR Kafka OR "hexagonal architecture")
NOT (intern OR internship OR stage OR alternance)
On a free account everything has to fit in the main bar, which forces you to tighten:
("développeur Java" OR "développeuse Java" OR "Java developer" OR "ingénieur Java") AND "Spring Boot".
The word “senior” has no business in the string. Few people write it in their title, and those who
do are not necessarily the ones you want: seniority is read in the career history, and in Recruiter
it is filtered, which is exactly what the help page recommends to lighten an overloaded query.
Two precautions that come from practice rather than documentation. A hyphenated term such as
“back-end” goes in quotes, because - is precisely a sign LinkedIn does not officially support,
and nobody knows what it will do in the middle of a word. And exclusion has to be measured: every
NOT you add also removes profiles that mention the word for a good reason, like the senior
developer who mentors interns.
What string finds a DevOps engineer?
DevOps is the role where the title lies the most, because the job has changed name three times in ten years and each company kept whichever name was current the year it created the position.
(DevOps OR SRE OR "site reliability engineer" OR "ingénieur cloud" OR "ingénieure cloud"
OR "cloud engineer" OR "platform engineer" OR "ingénieur plateforme" OR "ingénieur système"
OR "ingénieur production")
The technical part combines orchestration, infrastructure as code and the cloud provider, each in its own group so that AND taking precedence over OR breaks nothing:
(Kubernetes OR K8s OR OpenShift) AND (Terraform OR Ansible OR Pulumi) AND (AWS OR Azure OR GCP OR "Google Cloud")
That second string is already too demanding for most real roles, and that is on purpose: it shows where boolean cuts. Three ANDs are three chances to lose a candidate who does exactly the job but only wrote one of the names in the family. A well-kept brief says which of the three groups is truly a dealbreaker, and that is the only one that deserves an AND. The sorting happens during the intake meeting, the only moment the odds of a placement can still be changed, not in front of the search bar.
How do you run an X-ray search with Google?
By restricting a Google search to the domain of public LinkedIn profiles with the site:
operator, then adding the job’s terms in quotes.
site:linkedin.com/in "développeur Java" "Spring Boot" Lyon -offre
Google’s help documents quotes for an exact phrase, site: to restrict to a domain and the minus
sign to exclude a word, and says no space should separate the operator from the term. Uppercase
OR works in practice but is not on that page, and nested parentheses behave less reliably there
than on LinkedIn: an X-ray string is kept short.
Its limits come from what it is. It only sees profiles their owners have made public and Google has indexed, with the snippet from the crawler’s last visit, which may be months old. It is for checking that a profile exists, or for widening a search once the month’s allowance is gone, not for building a database. Automated extraction of the results or the profiles breaks LinkedIn’s terms, and the cost of automating LinkedIn is paid not on the company’s account but on the recruiter’s.
Why does a boolean search miss candidates?
Because it finds what is written the way you write it, and a profile is written by its owner, in their words, often a long time ago.
The first blind spot is the title. In an IT services firm the displayed title is often “Consultant”, “Engineer” or the client’s name, and the technology sits three lines down, in the description of an assignment, when it is there at all. A title search misses it, and a keyword search brings back every consultant who once came across Java. The second blind spot is language and gender: with no wildcard, “développeuse”, “ingénieure” and “developer” are three different words, and a string that does not write them all silently drops part of the profiles, including a good share of the women in the field.
The third is the synonym you did not know. A recruiter who does not know that OpenShift is a Kubernetes distribution, or that “ingénieur études et développement” is the historic title of a developer in many older French IT firms, will not type it. Boolean has no knowledge of the trade: it applies the knowledge of whoever is typing, and a string is exactly as complete as its author.
The last lies with the profiles themselves. A consultant placed with the same client for four years no longer updates their profile, and the technology they use today is not on it. That is not a flaw in the string but stale data, and it is the same reason a database ages faster than it gets cleaned.
Does semantic search replace boolean?
It recovers what boolean misses, the synonyms, the unusual titles, the technology described rather than named, and it brings a risk boolean does not have: no longer knowing why a profile came up.
A boolean string is entirely readable. You know why every result is there, and why someone missing is missing; that is its great virtue, and the reason it will not disappear from recruiting tools. Semantic search looks for meaning rather than words, and Cobalt has set out what semantic search changes compared with keywords for an IT services firm, especially for profiles whose title says nothing. The price is opacity, if the tool only ranks.
Our position is therefore the same as on the match score, the wrong instrument for choosing a candidate: a semantic result is worth something when it comes with a sentence that can be refuted. “Came up because their last three assignments describe Kubernetes deployment on Azure, without the word DevOps anywhere; availability not checked” can be verified in ten seconds. A percentage cannot.
And the order matters. Semantic search pays off most where the data is yours and the conversation has already happened: the talent pool nobody searches before sourcing is the place to try it first. That is how we have Balt work: he searches your ATS by meaning, says why each profile came up, and leaves the boolean search on LinkedIn to the recruiter, who types it themselves, on their own account.
Where do you start on Monday?
By rewriting your most-used string with parentheses around every group of ORs, the feminine and English forms of every title, and a single AND per criterion that is truly a dealbreaker.
Then keep the string somewhere the team can find it, with the date and the role it was written for. A good boolean string is a brief written in a peculiar syntax, and like a brief it ages: the job changes name, the tools change, and the string that found everyone two years ago now misses half of the people it used to find.
Frequently asked questions
Does LinkedIn accept the asterisk as a wildcard?
No. LinkedIn’s help page on boolean search lists the asterisk among unsupported symbols. To cover developer, développeur and développeuse, you have to write all three forms joined by OR, inside parentheses.
Do you have to type AND in capitals on LinkedIn?
Yes. LinkedIn states that the AND, OR and NOT operators must be typed in uppercase. In lowercase, “and” and “or” are treated as ordinary words, and in the Recruiter Keywords field they are on the list of stop words that are ignored.
Does boolean search work with a free LinkedIn account?
Yes, in the main search bar. What limits a free account is not the syntax but the volume: past a monthly threshold LinkedIn does not disclose, profile searches are restricted until the 1st of the following month. Premium Business, Recruiter Lite and Sales Navigator raise that cap.
Is X-ray search through Google allowed?
An X-ray search is an ordinary Google search restricted to LinkedIn’s domain with the site: operator, and it only shows profiles their owners have made public. What causes trouble is automated extraction of the results or the profiles, which breaks LinkedIn’s terms: you read, you do not collect.
Sources
- LinkedIn, Using Boolean search on LinkedIn (LinkedIn Help)linkedin.com
- LinkedIn, Use Boolean to filter search results in Recruiter and Recruiter Lite (Recruiter Help)linkedin.com
- LinkedIn, Commercial use limit (LinkedIn Help)linkedin.com
- Google, Refine Google searches (Google Search Help)support.google.com
- Cobalt, Recherche sémantique vs recherche par mots-clés : ce que ça change concrètement pour une ESN (April 2026)cobalt-ia.com

