Read and match
The cheapest candidate is the one you already sourced.
How search works
A real query language, for people who think in queries.
Recruiters who came up on job-board databases think in boolean, and stripping that away in the name of simplicity makes the tool slower for the people who use it most. So search takes a proper expression — AND, OR, NOT, grouping, phrases, and field comparisons for the things that are numbers.
- Saved searches —
The queries you run weekly, kept.
- Alerts on saved searches —
You are told when somebody new matches one, rather than remembering to re-run it.
- Search results are people —
Not application rows — so somebody who applied three times appears once, with their history under them.
- Protected attributes are refused —
A plain-language search that asks about gender, age, caste, religion or disability is declined rather than answered, and you can read the query it built before it runs.
What a result actually is
One person, and everywhere you have already had them.
A search result is not a row — it opens into every role that person has been considered for, across every client, going back as far as your data does. The rejection two years ago with its reason. The offer they withdrew from.
And the flag an agency needs most: whether they are live with more than one of your clients right now. Two desks that never compare notes discover that at the offer stage, and it costs both of them.
- Data EngineerMar 2024Client A · Rejected — below experience bar
- Senior Data EngineerNov 2024Client B · Withdrew at offer
- Data Platform LeadAug 2026Client A · In interview
- Senior Data EngineerSep 2026Client C · Submitted
What sourcers ask
Mostly about what the query can reach.
›Do we have to write boolean?
No — plain words work, and adjacent words are treated as AND. The query language is there for the people who want it, not imposed on the people who do not.
›Does the matcher replace search?
They answer different questions. Search finds people who meet criteria you state; matching evaluates a person against a role's requirements with evidence. Most work starts with the first and finishes with the second.
›Can we search candidates we got from a client?
Data you hold is searchable under the permissions and retention policies you set — see the compliance page for how candidate data is governed.
Book a demo
Run a query against a real database.
Bring the search you gave up on. Notice period is usually where it broke.