Lever · Global · Plain Boolean
Lever Boolean search
Lever is one of the few ATS vendors that publishes a field-prefix syntax on top of plain Boolean. That makes it the most precise box on this list — and the one where a bare keyword string leaves the most on the table.
Basis: Vendor documents the operators.
Your Lever string
Free · no login · nothing sent anywherePut the role and the skills in. This builds the string for Lever in its own grammar — with the operators and quotes that box actually parses.
Add one job title and one skill and the string appears here — built in Lever’s own grammar, in your browser.
Set these beside the string
- Filter chips sit under the search field and combine with the string — company, location and title chips are the documented examples.
- The Resume: chip restricts matching to content parsed from the resume, excluding the same word appearing in a note or a feedback form.
- Structured Contact Location gives each profile one standardised location to search against, instead of many permutations of a city name.
ATS Boolean string
("Account Executive" OR "Sales Manager") AND (Salesforce OR MEDDIC) AND ("New York")Composed from titles “Account Executive”, “Sales Manager” and skills “Salesforce”, “MEDDIC”, New York, 6 years. Paste it as-is.
What the vendor documents
- AND, OR and NOT connect field-specific search terms, and parentheses group them into clauses.
- Field prefixes search one field: title:, org:, location:, school:, source:, tags:, email: and card: — each has a singular and a plural form that behave identically.
- There must be no space between the colon and the term, and multi-word terms must be wrapped in quotation marks.
- The search matches candidate names and any parseable content attached to the profile — resumes, notes and feedback forms.
- Tags are case-sensitive.
What it does not say
- The prefix list is Lever's own and is not a general ATS convention. title: here does not mean title: on another platform.
- Our generator emits the plain-Boolean ATS string, not the field-prefixed one: a field prefix changes which field is searched, and that is a scoping decision only the recruiter can make.
- Because search covers notes and feedback forms as well as resumes, a term can match a candidate who never wrote it on their CV.
The filters that do the work
- Filter chips sit under the search field and combine with the string — company, location and title chips are the documented examples.
- The Resume: chip restricts matching to content parsed from the resume, excluding the same word appearing in a note or a feedback form.
- Structured Contact Location gives each profile one standardised location to search against, instead of many permutations of a city name.
Why the search returns nothing
- A space after the colon — title: "Executive" rather than title:"Executive" — changes what Lever searches.
- A tag search that appears broken is usually a capitalisation mismatch, not a missing tag.
- Leaving a city out of the prefix and putting it in the string matches CV text; the location chip is what filters by geography.
How to paste it
- 1
Open the candidate search — the search bar in the platform header, or Advanced search from the results page.
- 2
Paste the plain-Boolean string. Add a field prefix only where you need to scope a term, with no space after the colon.
- 3
Use the filter chips for company, location and title rather than repeating those facts in the string.
Where each claim comes from
Every claim on this page carries a status. documented means the vendor's own page says it. reported means an independent source shows it. our claim means we say it and nobody else does.
- field prefixes (title:, org:, location:, school:, source:, tags:, email:, card:)documented
Lever's Help Centre documents field-specific search terms with singular and plural prefixes that behave identically: `title:`, `titles:`, `org:`, `orgs:`, `location:`, `locations:`, `school:`, `schools:`, `source:`, `sources:`, `tag:`, `tags:`, `email:`, `emails:`, `card:`, `cards:`.
Read the source - no space between the colon and the termdocumented
Lever states explicitly that there must be no space between the colon and the search term, and that multi-word terms must be wrapped in quotation marks.
Read the source - AND / OR / NOT joining field termsdocumented
Lever documents using AND, OR and NOT to connect field-specific search terms, and grouping them into clauses with parentheses — for example `(location:Orlando AND org:Microsoft) NOT tag:"Do not contact"`.
Read the source - search scope includes notes and feedbackdocumented
Lever states the algorithm looks for candidate names and any parseable content attached to a profile — resumes, notes and feedback forms — and that the `Resume:` filter chip narrows the match to resume-parsed content only.
Read the source - tags are case-sensitivedocumented
Lever states tags are case-sensitive, and suggests changing capitalisation or using the tag filter instead when a tag search appears not to work.
Read the source
Lever Boolean search FAQs
Does Lever support Boolean search?
Yes. Lever's Help Centre documents AND, OR and NOT joining field-specific search terms, with parentheses for clauses — for example (location:Orlando AND org:Microsoft) NOT tag:"Do not contact".
What are Lever's field prefixes?
title: and titles:, org: and orgs:, location: and locations:, school: and schools:, source: and sources:, tag: and tags:, email: and emails:, card: and cards:. There must be no space between the colon and the term.
Why does the string here not use those prefixes?
Because a prefix decides which field is searched, which is a scoping decision only you can make. The string carries the terms; the prefix carries the scope. Add prefixes by hand when you need them.
Why does my tag search return nothing?
Lever states tags are case-sensitive. Change the capitalisation to match how the tag was created, or use the tag filter on the left of the results page instead.
Related
Start your next shortlist tonight.
Open a workspace, paste a JD, and screen the first pipeline. Plans from $9/mo, no auto-renewal.