aperture now ships with a built-in applicant tracking system.

now with built-in ats.

hiring

how to make sure ai hiring tools don't introduce bias

bias in hiring is older than ai. but ai changes the shape of the problem. it can remove human variance, or it can scale it. the difference comes down to what the platform was built to evaluate, what the team has tested, and what they will tell you. here is the practical view.

tl;dr

bias is not a checkbox. a serious vendor will tell you what they evaluate, what they ignore, and how they audit. you should test for disparities on your end too. the goal is not a perfect system. the goal is a system that is honest about what it sees, transparent about how it scores, and improvable when something looks off. here is what good looks like.

where bias comes from in the first place

in human screening, the largest single source of bias is something most teams do not name. it is interviewer variance. the same candidate gets a different evaluation from a different person, on a different day, asked different questions. that variance is not random. it correlates with attributes the interviewer was never supposed to factor in.

resume signals add another layer. names, schools, employment gaps, formatting choices, all of it shapes who gets a callback before anyone has spoken to anyone. these are well documented effects, not edge cases.

ai sits on top of this. it can either remove these signals from the evaluation, or it can learn them from training data and amplify them at scale. which one happens depends entirely on how the system was built.

what unbiased actually means

"unbiased" is not "the model treats everyone the same" in some abstract sense. that phrase is too easy to say. a useful definition has three parts.

first, the evaluation framework does not see protected attributes or strong proxies for them. with aperture, the AI does not see names, accents, gaps, or formatting. it sees how the candidate reasons about a structured set of behavioral prompts.

second, scoring is identical across candidates. the same six dimensions, the same rubric, the same conditions. interviewer variance is removed because there is no interviewer variance to remove.

third, outcomes are tracked for disparities by group, openly. a system that nobody is checking is a system you cannot trust, no matter how good the intent.

what to ask the vendor

most vendors will tell you they are unbiased. very few will tell you what they tested, what they measured, or what they would do if a disparity showed up. these are the questions that actually surface that.

questions worth asking

what does the model see during evaluation, and what does it explicitly ignore

what disparity tests have you run, against what reference groups, and how often

can you show the dimensions a score is built from, and the evidence behind each one

what would you do if a customer surfaced a disparity in their pipeline

can we audit our own outcomes against your scoring

how do you handle accents, non-native speakers, and non-traditional career paths

what good practice looks like

a serious platform looks the same for every candidate. the same structured behavioral interview, the same questions adapted to the same set of dimensions, the same scoring rubric, the same conditions. no resume signals enter the evaluation. no interviewer variance. no shortcuts.

scoring should be tied to specific evidence from the conversation. not "the model felt this candidate was strong" but "this answer demonstrated this dimension at this level for this reason." every score traces back to behavioral evidence. no black boxes.

this is how aperture is built. λ-CORE scores six dimensions, cognitive reasoning, domain knowledge, communication, behavioral indicators, collaboration, and adaptability. every output is a score, a confidence interval, and a pool rank percentile, all traceable back to what the candidate actually said. that traceability is the precondition for any honest conversation about bias.

what to check on your end

trust but verify. the vendor's word is a starting point, not the answer. you have data the vendor does not. use it.

on your side of the funnel

track outcomes by group at every stage, application to interview to offer to hire

compare pass-through rates across groups for drift, both relative to each other and to your prior baseline

look at scores at the boundaries, the top of the shortlist and the cut line

do not rely on the vendor's word alone, audit your own pipeline regularly

flag patterns early, when the sample is small enough to investigate properly

what to do if you find a disparity

do not panic. do not silently kill the tool either. a disparity in your funnel is information. it is the first step in fixing something, not the last word on whether the system works.

investigate the source. is the disparity larger or smaller than your prior baseline. does it appear at the AI step, or upstream in sourcing, or downstream in human review. is it concentrated in a specific role, a specific stage, a specific period.

then work with the vendor to fix it. a real partner will respond with data, with a hypothesis, and with a plan. a vendor that goes quiet, or insists nothing could possibly be wrong, has told you something important. the goal is not a perfect system on day one. the goal is a system that gets more honest over time. that is the standard worth holding any tool to, ai or human.

for the research behind why disparities hide in pooled averages in the first place, and how aperture is built to avoid the mechanism entirely, see does ai hiring cause racial bias, and how does aperture avoid it.

published march 1, 2026 by aperture team 9 min read

loading ...

back to blog