How an Applicant Tracking System Actually Works

What the software is for

An applicant tracking system solves an employer problem, not a candidate one. A company with forty open roles needs somewhere to put several thousand applications, a way to know who looked at what, and a defensible record of each decision. That last requirement is the one people forget, and it explains a lot of otherwise baffling behaviour: employers in the United States have record-keeping obligations around hiring, and the software is where those records live.

So the product is a database with a workflow bolted on top and a compliance layer underneath. It is not a judge. It has no opinion about your career. When it does something that looks like judgement — surfacing one candidate above another in a list — it is almost always executing a search or a filter that a recruiter typed in that morning.

The journey your application takes

Details vary by product and employer, but this sequence holds broadly.

1. 1
   A requisition is opened

   Before any candidate exists, someone creates the job record: title, department, hiring manager, approvals, budget, and the posting text. Everything about your application is attached to that requisition number. When you hear that a role is "on hold", this object is what has been frozen.

2. 2
   You submit

   You upload a file and complete a form. These are separate inputs. The file becomes an attachment; the form becomes structured data immediately, with no interpretation required. That difference matters more than almost anything else on this page.

3. 3
   Your file is parsed

   The system extracts the text layer of your document and tries to map it into fields: name, contact details, employer, title, start and end dates, education, skills. This is a best-effort process. It succeeds most of the time on conventional layouts and degrades quickly on unconventional ones.

4. 4
   A candidate record is created

   The parsed fields, your form answers and your attachment are joined into one profile, checked against existing records so one person applying twice is not two candidates.

5. 5
   Screening logic runs

   Where the employer has configured knockout questions or minimum criteria, they apply here. This is genuine automation, and it is far more consequential than anything to do with your resume design.

6. 6
   The record enters a stage

   New, Under Review, Screen, Interview, Offer — the labels differ, the idea does not. From this point onwards a person moves you, or nobody does and you sit in the first stage until the requisition closes.

The form and the file are not the same thing

Candidates spend hours on the document and minutes on the form, which is close to backwards. Structured fields are unambiguous — a dropdown answer needs no parsing and cannot be misread — so filters built on them are exact, and recruiters trust them accordingly.

The uploaded file

Read once by a parser, then mostly read by humans later in the process. Its job is to be extractable and persuasive, in that order.

The application form

Becomes filterable data instantly. Work authorisation, notice period, location, salary expectation and years of experience typically live here.

Screening questions

Employer-written, requisition-specific, and often the only part of the process that rejects anyone automatically. Read them slowly.

Autofill from your resume

A convenience feature that inherits every parsing error. Whatever it fills in, check it before you submit — you are the last person who can.

Voluntary demographic questions

Held separately from the hiring record and not intended to be visible to evaluators. Declining is a normal choice.

What "parsing" actually means

Parsing is two jobs stacked on each other. The first is extraction: pulling a stream of characters out of a PDF or Word file in the order they were meant to be read. The second is interpretation: deciding that the string "Regional Operations Manager" is a job title, that the line beneath it is an employer, and that "Mar 2021 – Present" is a date range with an open end.

If you want to see the effect on your own document rather than take anyone's word for it, our free ATS checker shows you the text that comes out of your file and which terms from a posting are missing from it. That is the same raw material the system is working with.

Stages, and the silence between them

Every candidate record sits in a stage. Stages are configured per employer, so one company's "In Review" is another's "Recruiter Screen", and a status you can see from the candidate portal may be a simplified version of what the recruiter sees. Nothing moves a record except a person clicking, a scheduled integration, or a rule the employer wrote themselves.

• Applied or New. Where everyone lands. Large postings accumulate hundreds of records here, and many are never opened individually — they are reached through search instead.
• Under review. Often means a recruiter has the requisition on their list, not that your specific record has been read. It is a stage label, not a promise.
• Screen. Someone has decided you are worth a conversation. This is the first genuinely human signal in the process.
• Rejected, with a disposition code. Employers record a reason — not qualified, position filled, withdrew, offer declined. The code is for their audit trail; the email you receive is a generic template that rarely reflects it.
• Talent pool or silver medallist. Strong candidates who lost out are often tagged and searched again later, which is why a recruiter sometimes contacts you about a role you never applied to.

What the software genuinely does automatically

It is worth being precise here, because this is where myth accumulates fastest. Systems reliably do the mechanical things: deduplicate records, send acknowledgement emails, apply knockout logic the employer configured, timestamp every action, and return search results. Many products also offer ranking or matching features, and some employers switch them on.

What ranking does, where it is enabled, is order a list. A recruiter still opens the list. Treating a ranking score as a gate that silently deletes applications is an assumption, not a documented behaviour, and it is contradicted by the ordinary experience of recruiters who spend their days scrolling past low-ranked candidates. Where employers do use automated assessment tools to make selection decisions, those tools sit under employment-testing rules — the EEOC's guidance on tests and selection procedures is the relevant framework, and it is a reason employers are cautious about full automation rather than enthusiastic about it.

Government hiring is a different machine

United States federal applications run on a process with published rules, which makes them a useful contrast. A federal HR specialist has to verify that your experience meets each stated qualification, and cannot infer anything you did not write down. That is why federal resumes are long, explicit and repetitive by design — the guidance on what to include in a federal resume asks for hours per week and detail that would look absurd on a private-sector page.

What this changes about how you apply

Answer the form carefully, because it is exact and it filters. Make the document extractable, because search is how you get found in a large pool. Then spend the time you save on fewer, better-aimed applications.

If you would rather have a person look at the result than a parser, our free resume review covers the half of the problem software cannot see. And if you are starting from a blank page, the resume builder produces single-column, text-based documents by default, which removes most of the extraction risk before you write a word.