What are Ashby's search limitations?

Ashby uses nested dropdown filters instead of standard boolean search strings. This makes it difficult to run exclusion queries (e.g., searching for 'Software Engineer' but excluding 'Manager'), which experienced sourcers rely on to efficiently narrow large candidate pools.

Does Ashby support boolean NOT searches?

Ashby's filter system does not natively support the NOT operator that sourcers use in standard boolean strings. Users must work around this by building complex nested dropdown conditions, which takes significantly longer than typing a boolean query.

How does Mokka complement Ashby for sourcing?

Mokka adds outbound sourcing from 850M+ passive profiles and 250+ job boards, plus AI-powered candidate matching that goes beyond keyword search. Sourced candidates sync directly into Ashby with pre-screening scores and evidence from structured AI interviews.

Back to ATS gap report

Ashby: search limits that slow down sourcing

Deep dive • Updated 31 Mar 2026 • 5 min read

The bottom line:

Ashby delivers clean pipeline management and analytics, but its search system uses nested dropdown filters instead of standard boolean strings. Experienced sourcers lose time building queries that take seconds in other tools. And Ashby only searches candidates already in your system.

Dropdown filters vs. boolean search

Ashby replaced the traditional boolean search bar with a visual filter system. You build queries by selecting conditions from dropdown menus: "Title contains Software Engineer" AND "Location is San Francisco."

This works for simple queries. The problem shows up with exclusions. To search for "Software Engineer" but exclude "Engineering Manager," you need to build nested filter conditions instead of typing Software Engineer NOT Manager. For sourcers running dozens of searches per day, this friction compounds.

Ashby also limits search to candidates already in your database. There is no outbound sourcing from external talent pools built into the platform.

The sourcing gap

Search limitations are one piece of a larger gap. Ashby manages candidates who have already applied or been imported. It does not help you find the passive candidates who never applied in the first place.

Teams using Ashby typically add a separate sourcing tool (LinkedIn Recruiter, Findem, or similar) and manually import candidates. They may also add a screening tool for pre-interview depth beyond resume review. That is three platforms for one hiring workflow.

Ashby's analytics and structured interview kits are strong. But finding candidates and evaluating them beyond the resume requires external tools.

How Mokka complements Ashby

Mokka connects to Ashby and adds the sourcing and screening depth it lacks:

Outbound sourcing: Mokka's AI sourcing agent searches 850M+ passive profiles and 250+ job boards. Candidates are matched to your open roles and synced into Ashby automatically.
Evidence-based screening: Every candidate (sourced or inbound) completes a structured AI pre-interview via text, voice, or video. Mokka collects evidence of accomplishments and verifies claims, not just resume keywords.
Unified ranking: Sourced candidates and applicants go through the same evaluation pipeline. Mokka pushes ranked shortlists with explainable scores back into Ashby, so your team sees everything in one place.

Ashby stays your system of record. Mokka handles discovery and evaluation.