LinkedIn has been quietly removing its most useful search filters for years — moving them behind premium paywalls or making them disappear entirely. What LinkedIn doesn’t advertise is that many of the most powerful filters still exist. They’re just hidden.
Secret LinkedIn Filters
Finding the right people on LinkedIn has never been straightforward. That is partly by design. As LinkedIn has monetized its platform over the years, genuinely useful search filters have quietly disappeared from view. Sometimes, LinkedIn has moved a vanishing filter to a higher-tier premium subscription, and occasionally, the filter is gone for good. Most users compensate by typing keywords directly into the search bar, unaware that LinkedIn applies those keywords across every field in a profile simultaneously. The search done this way returns voluminous, imprecise results that take far too long to sift through.
Boolean Search on LinkedIn: The Foundation
Before getting to the hidden operators, it is worth establishing what LinkedIn’s own search bar officially supports. You can run Boolean searches directly from the main search bar at the top of any LinkedIn page by entering your Boolean string there.
The operators LinkedIn officially supports:
Quoted searches — enclose a phrase in quotation marks for an exact match. For example: "VP of Engineering" or "Head of Information Security". Note that LinkedIn only supports standard straight quotation marks. Curly or “smart” quotes will not work. Stop words such as “by,” “in,” and “with” are ignored.
NOT — type NOT in capitals immediately before a term to exclude it. For example: "VP of Engineering" NOT (interim OR consultant OR contract)
OR — type OR in capitals to broaden results. For example: "VP of Software Engineering" OR "VP of Software Development" OR "Head of Engineering"
AND — type AND in capitals to narrow results. For example: "Head of Executive Search" AND "financial services"
Parenthetical searches — combine terms with parentheses for complex logic. For example: ("VP of Talent Acquisition" OR "Head of Executive Recruiting") NOT (staffing OR agency). Parentheses are the only grouping symbols LinkedIn recognizes. Square brackets, curly braces, and angle brackets are treated as ordinary characters and will not group terms.
Order of precedence — LinkedIn evaluates Boolean logic in this sequence: quoted phrases first, then parentheses, then NOT, then AND, then OR. When your string has more than two operators, always use parentheses. Without them, LinkedIn may interpret your query differently than intended.
What LinkedIn does not support: braces { }, brackets [ ], angle brackets < >, wildcards, or asterisks. The + and - operators are not officially supported. Use AND and NOT instead.
The Hidden Operators
The Boolean operators above are the visible layer. Beneath them is a second layer — undocumented operators that function like the filters LinkedIn removed from the interface.The following table is drawn from research by Irina Shamaeva, who spent more than a decade documenting LinkedIn’s hidden search infrastructure at booleanstrings.com before retiring in December 2024. Her operator list remains the most comprehensive published reference on the subject. The site continues under her collaborators David Galley and Julia Tverskaya.
| Operator | What It Searches | Values | LinkedIn Inference |
|---|---|---|---|
headline: | Keywords in headline | Text string | No |
summary: | Keywords in summary | Text string | No |
skills: | Keywords in skills | Text string | No |
spokenlanguage: | Language proficiency | Text string | No |
startyear: | Start year in college | Year | No |
endyear: | End year in college | Year | No |
title: | Current job title | Text string | No |
company: | Current company name | Text string | No |
school: | School name | Text string | No |
firstname: | First name | Text string | No |
lastname: | Last name | Text string | No |
industry: | Industry | Industry Codes | No |
companytype: | Company type | Company Type Codes | No |
companysize: | Company size | Company Size Codes | Yes |
seniority: | Seniority level | Seniority Codes | Yes |
degree: | Degree | Degree Codes | Yes |
profilelanguage: | Profile language | Two-letter language code | No |
functions: | Job function | Job Function Codes | Yes |
yoe: | Years of experience | Number 0–100 | Yes |
yoecc: | Years at current company | Number 0–100 | Yes |
yoepos: | Years in current position | Number 0–100 | Yes |
fieldsofstudy: | Field of study | FoS Codes | No |
schoolid: | School ID | School Codes | No |
Credit: Irina Shamaeva, Boolean Strings (booleanstrings.com/linkedin-search-operators)
On LinkedIn Inference: Operators marked “Yes” search values LinkedIn has calculated or inferred about a member — not information the member entered themselves. When you search using one of these operators, you are querying LinkedIn’s algorithmic assumptions about a profile, not the member’s stated data. Results may or may not reflect reality. More on this below.
A note on reliability: LinkedIn does not officially support or maintain these operators, and results can be uneven. A search may return fewer results than expected simply because many profiles are not coded for the field an operator is querying — a member’s seniority level or years of experience may not exist as a value in LinkedIn’s data layer for that record. Operator behavior also changes without notice as LinkedIn updates its infrastructure. Treat results as directional and verify.
Example Searches Using Hidden Operators
These examples use role titles relevant to executive search and corporate talent acquisition — the work these operators are built for.
title:"VP of Engineering" NOT (interim OR consultant OR contract) Finds VP of Engineering profiles in current roles, excluding interim and consulting assignments.
title:"Head of Information Security" OR title:"VP of Information Security" OR title:"SVP of Information Security" Captures the range of titles used for senior security leadership across organizations of different sizes.
title:"SVP of Platform Engineering" OR title:"VP of Platform Engineering" Targets senior platform engineering leaders — a role that varies significantly in title by company.
title:"VP of Product" OR title:"Vice President of Product" OR title:"Head of Product" Covers the most common title variations for senior product leadership.
title:"Chief Architect" OR title:"VP of Architecture" OR title:"Head of Architecture" Finds senior architecture leaders across title conventions.
title:"Head of Executive Search" OR title:"VP of Talent Acquisition" OR title:"VP of Executive Recruiting" Targets the in-house executive search and TA leaders who commission research engagements.
headline:"VP of Technology" NOT (staffing OR recruiting OR agency) Finds VP of Technology professionals, excluding recruiters and staffing professionals who use the title differently.
skills:"executive search" title:"Head of Talent Acquisition" Finds TA leaders who have listed executive search as a skill — a precise filter for in-house search practitioners.
school:"MIT" fieldsofstudy:"computer science" yoe:20 Finds MIT computer science graduates with approximately 20 years of experience — useful for academic lineage research.
spokenlanguage:es title:"VP of Software Development" OR title:"VP of Software Engineering" Finds Spanish-speaking senior engineering leaders — useful for searches requiring language skills.
The Skills Problem: What LinkedIn Is Doing Behind the Scenes
The skills: operator is one of the most useful hidden operators — and one of the most misunderstood, because LinkedIn’s definition of “skills” is considerably broader than what a member enters on their own profile.
LinkedIn Engineering has confirmed publicly that when it evaluates skills, it draws from multiple sources simultaneously. It converts all the text in a member’s entire profile into a single large field and uses it to perform keyword searches for skills. It scans resumes that it has access to. And — most significantly — it infers skills based on network connections: if a member’s connections are similar to those of others with a particular listed skill, LinkedIn will assign that skill to the member even if they never listed it.
In practice, this means skills:javascript returns profiles where LinkedIn has inferred JavaScript proficiency — not only profiles where the member explicitly listed it. LinkedIn’s broader skills definition approximately 97% of members who have the keyword listed anywhere in their profile. A word does not need to be listed as a skill to be interpreted as one by LinkedIn.
The hidden skills: operator queries self-entered skills specifically — a materially more precise search than LinkedIn’s default skills filter. This distinction matters for executive search, where precision is the point.
The broader implication: LinkedIn is actively appending inferred attributes to member records based on network analysis and full-text processing. Members do not see these inferred attributes and cannot correct them. Sourcers searching by skills may retrieve profiles that match LinkedIn’s inferences rather than the member’s stated expertise. For senior technical roles where skills specificity matters, this is a meaningful source of false positives — and a compelling reason to use the hidden skills: operator rather than the visible filter.
LinkedIn Search Is Inconsistent — and That Is a Known Problem
Experienced sourcers have observed for years that LinkedIn returns different results for the same search string on the same day. This is not imagined. LinkedIn’s search infrastructure involves personalization algorithms, relevance ranking, and ongoing A/B testing that vary by account, session, network, and time. The same Boolean string entered by two users with different account tiers, different connection networks, and different search histories will return different results.
This inconsistency is compounded by the fact that LinkedIn changes its infrastructure without announcement. Operators that worked reliably last quarter may produce degraded results today. The hidden operators documented here are undocumented by LinkedIn precisely because LinkedIn does not want to support them as a stable feature. They are artifacts of the underlying data architecture that the sourcing community has reverse-engineered, tested, and shared.
Google X-Ray Search: Still Legal, Significantly Diminished
Google X-ray search — using site:linkedin.com/in/ followed by Boolean search terms to find LinkedIn profiles through Google’s index rather than LinkedIn’s own search — remains a legal and widely used sourcing technique. In practice its value has diminished considerably.
LinkedIn has systematically restricted what public profile data it makes available to search engines. If you view a LinkedIn profile while logged out — or open one in incognito mode — you will find that headline, work experience, and education are largely blocked. What Google indexes is largely name and current employer, which is a fraction of what was available even two years ago. LinkedIn has effectively converted public profile data into login-gated data, leaving search engines with significantly less to index.
X-ray searches can still help identify that a person with a specific title exists at a specific company. The structure still works:
site:linkedin.com/in/ "VP of Platform Engineering" "Cloudflare"
But do not expect to see experience detail, tenure, or education in the results. That data now sits behind LinkedIn’s login wall.
Some sourcers are experimenting with Bing and DuckDuckGo, which may index different amounts of LinkedIn data than Google. Results vary and are not consistent enough to recommend as a reliable alternative. The more durable workaround is to use LinkedIn’s hidden operators directly — they reach data inside the platform that X-ray search can no longer surface from outside it.
Google X-Ray Search: Still Legal, Significantly Diminished
Google X-ray search — using site:linkedin.com/in/ followed by Boolean search terms to find LinkedIn profiles through Google’s index rather than LinkedIn’s own search — remains a legal and widely used sourcing technique. In practice its value has diminished considerably.
LinkedIn has systematically restricted what public profile data it makes available to search engines. If you view a LinkedIn profile while logged out — or open one in incognito mode — you will find that headline, work experience, and education are largely blocked. What Google indexes is largely name and current employer, which is a fraction of what was available even two years ago. LinkedIn has effectively converted public profile data into login-gated data, leaving search engines with significantly less to index.
X-ray searches can still help identify that a person with a specific title exists at a specific company. The structure still works:
site:linkedin.com/in/ "VP of Platform Engineering" "Cloudflare"
But do not expect to see experience detail, tenure, or education in the results. That data now sits behind LinkedIn’s login wall.
Some sourcers are experimenting with Bing and DuckDuckGo, which may index different amounts of LinkedIn data than Google. Results vary and are not consistent enough to recommend as a reliable alternative. The more durable workaround is to use LinkedIn’s hidden operators directly — they reach data inside the platform that X-ray search can no longer surface from outside it.
What LinkedIn Is Building Instead
LinkedIn continues to develop AI-assisted search features alongside and sometimes in tension with Boolean methods. Its AI search assistant — rolling out to premium tiers — interprets natural language queries and translates them into search parameters without requiring Boolean syntax. Collaborative Articles generate inferred expertise signals that feed into search ranking.
These enhancements increase discoverability for active, engaged LinkedIn members. They do not solve the underlying problem: the most valuable senior candidates are frequently the least active on the platform, the least likely to have complete profiles, and the least likely to appear in AI-assisted results calibrated toward engagement signals. Boolean search with hidden operators reaches those candidates more reliably than any AI-assisted feature LinkedIn currently offers — because it searches the data that exists in the profile, not the activity signals LinkedIn’s algorithm prefers.
What Are You Finding?
These operators are a living list. LinkedIn changes things quietly and often. If you have found an operator that no longer works, discovered one that is new, or noticed behavior worth reporting, we want to hear from you. Leave a comment below or reach out directly. Sourcing is a community sport — and the community knows things LinkedIn’s documentation will never tell you.
Intellerati is the executive search research practice of The Good Search. We use investigative methodology — including advanced Boolean search, hidden LinkedIn operators, and primary source research — to find the senior executives that databases and algorithms miss.
