Why We Made Candidate Search Work Across Your Whole Pool
Small thing we shipped that I think matters more than it sounds: AI Search now works across your entire candidate pool, not just one job's applicants.
Most ATS tools scope search to whatever position you have open. But someone who applied 6 months ago, didn't get that role, but would be great for what you're hiring now that person usually just gets forgotten. We wanted a search that could surface them anyway.
So now you can type something like "React devs in Berlin, 5+ years" and it searches everyone who's ever applied to your org, in plain English, no filters to configure. Under the hood it leans on the same structured CV data every other AI feature uses if an application's missing that data for some reason, the search just re-parses it first instead of silently skipping it.
Honestly the hardest part wasn't the search itself, it was resisting the urge to scope it narrowly "for performance reasons." Cross-org search is more expensive to run well, but it's also the only version that's actually useful in the moment you need it.
Curious if others have run into this features that are technically harder to build broad, but useless if you scope them down.
The “search the whole pool” decision is interesting.
Curious whether users immediately understand the value of that broader search, or whether they still think in terms of the job they’re currently hiring for.