Applicant tracking systems (ATS): what they do, and where they fall short

Almost every company above a handful of employees runs hiring through an applicant tracking system, and almost nobody outside recruiting quite understands what it does — which is how a small mythology has grown up around it, most of it about résumés being silently devoured by keyword-hunting robots. It's worth separating what an ATS actually is from the folklore, because the real limitations are different from the imagined ones, and they change how you should build the rest of your process.

The short version: an ATS is a system of record and workflow. It's excellent at logistics and neutral on quality — it will organize a biased process exactly as efficiently as a fair one. This guide explains what it genuinely does, debunks the keyword myth, names where ATS-centric hiring actually goes wrong, and covers what to pair it with so the workflow tool isn't quietly making your selection decisions for you.

What an ATS actually does

At its core an ATS does four mundane but valuable things: it collects applications into one place, stores a structured record for each candidate, moves people through defined pipeline stages, and coordinates the communication and scheduling around all that. For a team handling hundreds or thousands of applicants, this is genuinely essential — without it, hiring dissolves into lost emails and forgotten candidates. It is, in other words, infrastructure.

What it is not is an evaluator. An ATS has no opinion about who's good; it presents a list and tracks what humans do with it. That distinction is the whole point of this article, because the moment people treat the ordering of that list as a judgment of merit, a logistics tool starts driving selection decisions it was never designed to make.

The keyword myth

The most durable piece of ATS folklore is that it auto-rejects any résumé missing the exact keywords from the job description, which has spawned an entire industry of “beat the ATS” advice. The reality is more boring: while modern systems can filter and rank, the idea that they silently bin qualified candidates over a missing synonym is largely overstated. Most rejection still comes from a human skimming the list the ATS presents — which means the fairness problem lives in the skim, not the software.

This matters because it redirects your attention to the real risk. Optimizing résumés for keywords is mostly wasted effort; fixing how the list gets reviewed is where the leverage is. That's the same insight behind reducing bias: the damage happens in the fast human judgment, so that's where the structure needs to go.

Where ATS-centric hiring falls short

The limitation isn't a flaw in any particular ATS — it's a category boundary. Because the ATS surfaces résumés and tracks stages, teams that lean on it as their primary decision aid end up making the same résumé-driven, proxy-heavy judgments it was never meant to improve. It will faithfully run a process built on pedigree and keywords, complete with tidy dashboards, and give you no signal at all about who can actually do the work.

The fix isn't to replace the ATS — you still need the workflow — it's to put a real evaluation layer in front of the human skim. A skills-based assessment or a structured AI interview changes what the list is ordered by, so the ATS is tracking a merit-based pipeline rather than a pedigree-based one.

How Spoon complements your ATS

Spoon isn't trying to replace your system of record; it's the evaluation layer that makes the record worth tracking. Candidates are assessed through the same structured, skills-first interview and surfaced as an anonymized, merit-ranked shortlist — so what flows into (or alongside) your ATS is ordered by demonstrated ability, not by who had the most keyword-optimized résumé. See how it fits the wider tool stack or how it works for companies.

Frequently asked

Keep reading