DEV Community

Aremu Feranmi
Aremu Feranmi

Posted on

What if an Applicant Tracking System could explain why a candidate was rejected?

Hiring systems increasingly rely on automated scoring, but when an ATS makes a decision, it can be difficult to understand what actually influenced the outcome.

AI Bias Firewall (AIBF) is an open source project designed to provide an explainable bias detection layer for Applicant Tracking Systems.

AIBF can:

• Analyze ATS scoring decisions
• Identify potential protected attribute proxies
• Measure how different factors contribute to a decision
• Flag potentially biased outcomes for human review
• Generate plain language explanations
• Learn from HR feedback through model retraining

One of the interesting aspects of AIBF is its open source and method documented approach, allowing developers and researchers to inspect, test, and improve the system.

The project uses synthetic data, so no real candidate information is included in the repository.

For developers, researchers, and professionals working in AI/ML, HR technology, responsible AI, algorithmic fairness, or explainable AI, AIBF is worth exploring.

🔗 Explore AIBF on GitHub: https://github.com/jbarach2012/AIBF_API

ResponsibleAI #ExplainableAI #AlgorithmicFairness #AI #MachineLearning #HRTech #OpenSource #GitHub

Top comments (5)

Collapse
 
maria_bryan_88081208cbd profile image
Maria B. Ryan •

This is a strong approach to making automated hiring decisions more transparent and auditable. I particularly like the focus on identifying the factors behind an ATS decision rather than treating the final score as a black box.

The combination of explainable attribution, human review, and feedback-based model improvement makes this especially relevant to responsible AI in HR. It will be interesting to see how AIBF performs across different ATS models and more complex real-world hiring scenarios.

Collapse
 
junior_jimmy_1a2c8dcb1eb1 profile image
Junior Jimmy •

This is a genuinely important direction for AI in hiring. The biggest problem with automated ATS decisions is often not just whether a candidate is rejected, but the lack of transparency around why that decision happened.

AIBF's approach to combining explainability, bias detection, and human review is particularly valuable. Identifying protected-attribute proxies and showing how individual factors influenced a decision could help organizations move away from "black box" hiring systems toward more accountable AI.

The open-source and documented methodology is also a major strength—it gives developers and researchers the opportunity to inspect, test, challenge, and improve the system rather than simply trusting proprietary algorithms.

Responsible AI in HR needs transparency, continuous evaluation, and meaningful human oversight. Projects like AIBF can help make those principles more practical.

Collapse
 
adebisi_oluwajoba_6ba5603 profile image
Adebisi Oluwajoba •

Great initiative. Explainability is one of the biggest missing pieces in AI-driven hiring. AIBF's focus on detecting potential bias and clearly explaining ATS decisions makes it a valuable project for building more transparent and accountable HR technology. Definitely worth exploring for anyone working in Responsible AI and HRTech.

Collapse
 
marcus_aurelius_691085937 profile image
Marcus Aurelius •

Very interesting approach to making ATS decisions more transparent. The focus on feature-level attribution, explainable outputs, and human review is especially important in responsible AI for hiring.

I’d be interested to see how AIBF performs across different ATS models and real-world datasets as the project evolves. Definitely a space worth watching.

Collapse
 
robert_smith_7ed5fb7cc54b profile image
Robert Smith •

This is a crucial step forward for the HR tech ecosystem. As global regulations like New York City’s Local Law 144 and the EU AI Act increasingly mandate rigorous auditing for automated employment decision tools (AEDTs), black-box scoring is no longer viable. AIBF’s focus on exposing proxy variables—where seemingly neutral data points like zip codes or graduation years stand in for protected attributes—is exactly the type of defensive layer engineering teams need to deploy. Making it open-source accelerates the benchmark standards we desperately need for algorithmic accountability.