How Recruiters Use ATS Systems

Applicant tracking systems get a lot of blame from candidates, and some of it is fair. But most candidates, and honestly a fair number of recruiters, have a fuzzy idea of what an ATS actually does day to day. At APTI Careers, we build AI-powered hiring tools and work alongside recruiting teams every day, so we see this confusion up close. It is not a single mysterious gatekeeper deciding who gets hired. It is a piece of software that recruiters configure, feed, and rely on to manage a process that would be unmanageable by hand at any real scale. Understanding how recruiters actually use these systems clears up a lot of confusion on both sides.

The core job an ATS is built for

At its simplest, an applicant tracking system exists to organize applications. Before these systems became standard, recruiters managed candidates through spreadsheets, email folders, and a lot of manual tracking. For a company hiring for one or two roles a year, that was manageable. For a company hiring for 50 roles at once, each getting hundreds of applications, it was not. The ATS solves that organizational problem first and foremost. It stores every application, tracks where each candidate sits in the process, and gives recruiters a shared system so nothing falls through the cracks when multiple people are involved in a hire.

Everything else the system does, scoring, filtering, ranking, is built on top of that core organizational function.

How recruiters set up filtering

Recruiting teams, or whoever configures the job posting in the system, typically define a set of required and preferred qualifications tied to the role. This might include specific keywords pulled from the job description, minimum years of experience, required certifications, or location requirements. The system then scans incoming resumes against these criteria and either scores them, tags them, or in stricter setups, filters out anyone who does not meet certain hard requirements before a recruiter ever sees them.

This setup step matters enormously, and it is often where the biggest problems start. A recruiter who copies overly strict requirements from a template, or sets a keyword list that only matches one specific way of describing a skill, can accidentally filter out strong candidates before the actual screening even begins. Recruiters who use these systems well spend real time thinking through what should be a hard filter versus what should just influence a ranking, because getting that wrong quietly shapes the entire applicant pool they end up reviewing.

"An ATS is not a mysterious gatekeeper deciding who gets hired. It is an organizational tool built to manage volume that recruiters must configure thoughtfully."

What recruiters actually look at day to day

In practice, most recruiters using an ATS are not obsessing over a single match score. They are working through a dashboard that shows applications organized by stage: new, screened, interviewing, offer, rejected. A typical day involves reviewing new applications that came in, often sorted by score or recency, moving strong candidates to the next stage, sending rejections or requests for more information, and updating notes on candidates who are further along in the process.

The score is one input among several the recruiter sees at a glance, alongside things like whether the resume was referred by an employee, how quickly the candidate applied after the posting went live, and any flags from earlier stages of screening. Experienced recruiters learn to weigh these signals together rather than leaning on any single number.

Where automation ends and human judgment begins

Most companies do not let the ATS make final decisions on its own, even when they set up automated filtering. The system typically handles the first pass, narrowing hundreds of applications down to a more manageable shortlist, and then a human recruiter reviews that shortlist directly. How much the system automates versus how much a human reviews varies a lot by company size and role volume. A small company hiring for a handful of roles might have a recruiter read every single application manually, using the ATS mainly for organization rather than filtering. A large company running high volume hiring for entry level or seasonal roles might rely much more heavily on automated filtering just to make the volume manageable at all.

This is also where a lot of candidate frustration comes from. A rejection that arrives within minutes of applying usually means the system auto filtered the application before a person ever saw it, which understandably feels impersonal. Recruiters at companies with heavy automation are often aware of this tradeoff and are actively working to reduce how much gets filtered without human review, because losing strong candidates to an overly aggressive filter is a real cost to the business, not just an inconvenience to the candidate.

How recruiters use ATS data beyond individual resumes

Beyond screening individual candidates, recruiters use the aggregated data inside an ATS to understand their hiring funnel as a whole. They can see how many applications a posting received, what percentage passed the initial screen, how long candidates typically sit at each stage, and where candidates tend to drop out of the process. This data helps recruiters spot problems that are not obvious from looking at any single application. If a posting is getting hundreds of applications but almost none are passing the initial screen, that usually means the requirements are set too strictly, or the job description does not match the kind of candidates actually applying, and the recruiter can go back and adjust it.

This funnel level view is genuinely useful, and it is one of the strongest arguments for using an ATS at all, separate from the screening and scoring features that get most of the attention and criticism.

Common mistakes recruiters make with these systems

• Setting filters too strictly: Copying old job postings without questioning whether every requirement still makes sense often excludes top-tier talent unnecessarily.
• Relying blindly on keyword matching: Keyword lists built around internal company jargon fail to recognize candidates from other industries who describe equivalent skills using different terms.
• Neglecting candidate experience: Overly lengthy default application forms cause highly qualified applicants to abandon the application halfway through.

How different company sizes configure these systems differently

The way an ATS gets used varies a lot based on company size and hiring volume, and understanding this helps explain why candidates sometimes get very different experiences applying to similar sized roles at different companies. A small company with an in house recruiter handling a handful of open roles often uses the ATS mainly as a lightweight tracking tool, with light or no automated filtering, because the volume simply does not require it. In that setup, a human is realistically reading most or all of what comes in.

A mid sized company scaling up hiring often introduces more automated filtering as volume increases, sometimes reactively after a recruiter gets overwhelmed by application counts that used to be manageable by hand. This transition period is often where filtering gets configured hastily, using generic templates or overly broad keyword requirements, simply because nobody has had time to build it out carefully yet.

A large enterprise running high volume hiring across many roles typically has a dedicated recruiting operations function whose job includes actively tuning and monitoring ATS configuration, testing different filtering approaches, and analyzing funnel data regularly. These companies tend to have the most sophisticated setups, but ironically are also the ones most likely to rely heavily on automated filtering simply because the volume leaves no realistic alternative.

The recruiter's perspective on false negatives

Experienced recruiters are often more worried about false negatives, strong candidates the system filters out incorrectly, than they are about false positives, weaker candidates who make it through. This might seem counterintuitive, since a false positive wastes a recruiter's time reviewing an unqualified candidate, while a false negative simply means never seeing a strong one. But recruiters who have been in the field long enough have usually experienced the frustration of discovering, often by accident, that a genuinely excellent candidate got filtered out early due to an overly strict setting, sometimes only realizing it when that same candidate got hired successfully somewhere else.

This awareness has led many recruiters to push back against overly aggressive automated filtering, preferring a wider initial funnel that requires more manual review time over a narrow one that risks losing strong candidates before anyone ever sees them. Recruiters who advocate for this tradeoff internally are often the ones who produce the best long term hiring outcomes, even though their approach looks less efficient on paper in the short term.

Where AI-conducted interviews fit into this picture

An ATS is good at organizing applications and managing volume, but it was never designed to actually evaluate whether someone can do the job. That gap is exactly what led us to build APTI Careers. Rather than relying purely on resume filtering, our platform brings structured, AI-conducted interviews earlier into the process, with video proctoring and integrity verification built in, so recruiters get real evaluation data alongside the organizational benefits an ATS already provides.

Used well, an ATS and a structured interview process complement each other. The ATS keeps the pipeline organized and manageable. The interview process gives recruiters actual signal about candidate ability, something keyword matching alone was never built to provide.

Combine better organization with better evaluation.

If your team is looking at ways to combine better organization with better evaluation, we would be glad to show you how APTI Careers fits into that picture.