Quick answer
AI tools for HR split cleanly into two groups with very different risk profiles. Administrative tools — scheduling, note-taking, policy drafting, onboarding logistics — are safe, cheap and immediately useful. Decision tools — CV screening, candidate ranking, performance scoring — carry real legal exposure, are increasingly regulated, and require bias auditing you will have to pay for. Adopt the first group freely. Treat the second as a compliance project rather than a software purchase.
Most roundups in this category list twelve tools and mention the legal position in one sentence near the end. That ordering is backwards. In hiring, the regulatory question determines whether you can use a tool at all, which makes it the first filter rather than a footnote.
This is written for small companies and founders doing their own hiring rather than for enterprise HR departments with legal teams — which is precisely the group most likely to adopt a screening tool without realising what comes attached.
| Administrative AI | Decision AI | |
|---|---|---|
| Examples | Scheduling, notes, drafting, onboarding, FAQ | CV screening, ranking, video assessment, performance scoring |
| Who it affects | Your time | Someone’s employment |
| Failure cost | Mild annoyance | Discrimination claim |
| Regulatory load | Ordinary data protection | Specific AI hiring rules in several jurisdictions |
| Verdict | Adopt freely | Only with audit, disclosure and human review |
My take
Interview note-taking is the one I would adopt first and the one whose benefit is most underrated. Not because of the transcript — because of what it does to the interview. An interviewer who is writing is not listening, and is certainly not following up on the interesting thing the candidate just said. Removing the note-taking makes the conversation better, which improves your hiring decisions more than any screening algorithm would.
CV screeners, candidate rankers and automated assessment tools promise to cut a hundred applications to ten. Here is what a small company usually does not know before buying one.
Watch out
Regulation in this area is moving quickly and varies by jurisdiction, including by city. Nothing here is legal advice. Before adopting any tool that influences a hiring or employment decision, get advice covering every location you hire in — the obligations attach to you as the employer, and a vendor telling you their tool is compliant is not the same as your process being compliant.
The mechanism is worth understanding rather than taking on trust, because it explains why “we removed names and photos” does not solve it.
These systems learn from historical hiring data — who was hired, who succeeded. If past hiring favoured a group, the pattern the model learns is that group’s characteristics. It does not need a protected attribute to do this. University attended, postcode, gender-coded language in self-description, employment gaps, sports played: all correlate with protected characteristics and all survive anonymisation.
The well-documented case is Amazon, which abandoned an experimental recruiting tool after finding it penalised CVs containing the word “women’s”, having learned from a decade of male-dominated applications. Amazon had world-class engineering resources and could not fix it. A small company buying a vendor tool has considerably less visibility into what it learned.
There are legitimate reasons to — genuinely high application volumes make some filtering necessary. Six conditions I would insist on.
Worth noting because it undermines the premise. Candidates now use AI to write CVs and cover letters at scale, which is why application volumes have risen sharply, which is why employers reach for screening tools, which drives candidates to optimise harder.
Both sides are now running language models at each other, and the signal in a written application is worth less than it was. My honest conclusion: the response is not a better filter. It is to weight earlier stages differently — a short structured task, a brief real conversation — which is expensive per candidate and actually tells you something.
Adopt the administrative tools immediately. Note-taking, drafting, scheduling, policy documents, survey analysis. Real time saved, minimal risk, and in the case of interview notes it makes you better at the job rather than just faster.
Be sceptical of decision tools. Not because they never work, but because the obligations land on you, the bias is hard to see from outside, and the thing they optimise — filtering applications faster — is a symptom of a signal problem they also make worse.
If you are a small company drowning in applications, I would spend the money on a better-written job posting and a short paid task before I spent it on a ranking algorithm. Both improve the pool rather than sorting a bad one more quickly.
For the underlying tools, see the best AI content creation tools and what ChatGPT is and how it works. For automating the administrative side properly, workflow automation covers the rule-based approach.
The safe and immediately useful ones are administrative: interview note-taking such as Otter or Fireflies, job description drafting with any general model, AI-assisted scheduling, policy and handbook drafting, internal onboarding FAQ answering, and summarising free-text employee survey responses into themes. These save real time with minimal risk.
It depends on where you hire, and the obligations fall on you as the employer. New York City requires independent bias audits, published results and candidate notification for automated employment decision tools. The EU AI Act classifies recruitment and selection systems as high risk. Existing discrimination law applies regardless, and the software decided is not a defence anywhere.
They learn from historical hiring data, so if past hiring favoured a group the model learns that group’s characteristics. Removing names and photos does not fix it, because university attended, postcode, gender-coded language, employment gaps and hobbies all correlate with protected characteristics and survive anonymisation.
Amazon abandoned an experimental recruiting system after finding it penalised CVs containing the word women’s, having learned from a decade of predominantly male applications. The significance is that Amazon had world-class engineering resources and still could not fix it, which should temper confidence in vendor tools whose training data you cannot inspect.
A New York City law requiring employers using automated employment decision tools for candidates in the city to have an independent bias audit conducted, publish a summary of the results, and notify candidates that such a tool is being used. It is an ongoing obligation with real cost, and it attaches to the employer rather than the software vendor.
Six conditions: it ranks or shortlists but never rejects, with a human reviewing every rejection; ask the vendor what it was trained on and what bias testing exists; audit your own funnel demographics at each stage; tell candidates and offer human review; keep records of tool, version, criteria and reviewer; and periodically have someone properly read twenty rejected CVs.
Because candidates now use AI to write CVs and cover letters at scale. That raises volume, which pushes employers toward screening tools, which pushes candidates to optimise harder. Both sides are running language models at each other, and the result is that the signal in a written application is worth considerably less than it used to be.
Interview note-taking, and the benefit is not mainly the transcript. An interviewer who is writing is not listening or following up on what the candidate just said. Removing note-taking improves the conversation itself, which improves hiring decisions more than any screening algorithm. Always obtain consent and state what is being recorded.
Agent demos fail in production for boring reasons that have nothing to do with model…
A practical Triumphoid guide to notion vs google sheets for ai content calendars: my wordpress…
Most AI content tools are wrappers over the same models. The three you actually need,…
Your n8n production workflow just stalled with a 429 error, but your request logs show…
Visual configuration blueprints for inserting wait states and secure manual validation gates into production AI…
AI detectors measure predictability, not authorship. Why they flag human writing, what Google actually penalises,…