How to Search Your Candidate Database in Plain English
Natural-language candidate search lets you type what you're looking for, such as "five-plus years of SaaS sales and Python", and returns people from your talent pool who match, instead of requiring you to build a Boolean string. It works best on the data you already hold: resumes you've screened.
How it differs from keyword search
A keyword search needs the exact word. A natural-language search can recognise that "account executive" and "AE" are related, and can weigh several conditions together. It saves you from missing someone because they phrased a skill differently.
Writing good queries
Be specific about the must-haves: skill, years of experience and, if needed, industry. Add one or two conditions, not ten. Then use filters, such as location, to narrow the results.
When to use Boolean instead
Boolean strings are still the right tool for searching external sites such as LinkedIn, where natural language isn't supported. Use plain English inside your own database and Boolean outside it.
Check the results, don't trust them blindly
Search surfaces candidates worth a look; it doesn't prove fit. Open the profile and compare against the job's requirements before reaching out.
In Rezumz
Recruiter AI Search covers your whole talent pool with plain-English queries plus location and industry filters. The free Boolean Search Builder is available for external search.
Frequently asked questions
Does AI search replace Boolean search?
Not entirely. It works well within your own candidate data; Boolean strings remain useful on external platforms.
How specific should my query be?
Specific enough to name the must-have skill and experience level, short enough to read as a single request.
Will it find candidates who aren't in my database?
No. It searches candidates you've already added or screened.