more filter interactions
in CX tickets

Filters and search should speed up screening, but in our ATS, they were barely used. This created a paradox: recruiters were spending hours manually screening candidates one by one, avoiding the very features designed to save them time.
"Without predictability in results, each filter became a gamble that could lead to empty results, causing recruiters to prefer the exhausting manual screening over the uncertainty of using filters."
We started a mixed investigation to better understand the cause of the problem and how we could solve it:
The lack of predictability in results caused empty searches, where recruiters ended up choosing to manually screen candidate by candidate, ignoring the available filters and increasing screening time.
As a solution, we proposed giving users control over the results

During ideation, we conducted an audit of filter options, eliminating color criteria and adapting gender identity options to mitigate legal risks for clients and promote a selection process more focused on skills, reducing unconscious biases in screening.
To ensure the solution met the objective of helping recruiters avoid empty results when applying filters, we validated the solution with usability tests with medium-fidelity prototypes. After the tests, we only needed to add some filter options, but the counter solution proved efficient.
By collaborating with developers in the early ideation stages, we ensured that the counter solution was technically feasible and that the development time for this solution was predictable, accelerating delivery of the functionality.

The Handoff of this functionality was done with the usability guidelines and UI standards of the new Design System we were implementing. Through integration of Figma MCP with IDEs and a shared design tokens file, it was possible to further accelerate development and maintain platform design consistency.
Comparing the pre and post-launch periods (3 months vs. 1 month), the numbers confirmed the hypothesis:
more filter interactions
in CX tickets
"Screening became more fluid. I no longer need to keep going back and forth between screens to make decisions."