An applicant tracking system is the database an employer keeps applications in. The posting is written in it, published from it, and every application lands in it as a record: your resume parsed into fields, your answers to the form, a status, and a log of who looked. It does three things: store, sort and route. It does not decide. The folklore says a robot rejects you. The truth is duller. A clerk files you, and a person who is busy reads the files in the order the clerk sorted them.
Key points
- An ATS stores applications, sorts them, and routes them to people. A person decides.
- Your record is the parsed resume plus the form answers plus a status. The resume is read as fields.
- A knockout question is the one automatic rejection: a form question with a wrong answer.
- Recruiters search and filter the records. The search is on words, which is why the posting's words matter.
- Every hiring system has a careers page, and that page is where the posting is true.
What it stores
When you apply, the system creates a candidate record and attaches an application to the posting. The record holds:
| Field | Where it comes from |
|---|---|
| Name, email, phone, location | Parsed from the resume, then the form |
| Roles, with titles, companies and dates | Parsed from the resume |
| Skills | Parsed from the resume, and from a form question if there is one |
| Education | Parsed from the resume |
| Form answers | The application form: work authorisation, salary, start date, custom questions |
| Source | Where you came from: the careers page, a job board, a referral |
| Status | New, reviewed, screening, interviewing, offer, rejected, and the employer's own stages |
| Notes and scores | What the people who looked wrote down |
The resume file is attached too, and a recruiter who opens the record sees it. But the search and the filters run on the fields, which is why the guide on parsing matters.
You are not applying to a person. You are creating a record a person will search.
How it sorts
The system does not rank you. It sorts by whatever the recruiter asks for: date, source, a search term, a filter on a form answer. The common views are newest first, and a search for the posting's terms.
A recruiter with four hundred applications for one role reads the first fifty of a sorted view, finds eight to call, and stops. The order of the view decides who is in the fifty. Applying early helps with the newest-first view. Having the posting's words helps with the search view. Nothing else about the resume changes the order.
Knockout questions
The one automatic rejection is the knockout question. A form question with a required answer: do you have the right to work here, do you have the licence, are you able to work on site three days a week. A wrong answer moves the application to rejected without a person reading it.
Three things to know. The questions are visible on the form before you submit. The answers are checked against the record later, so a wrong "yes" is found at the offer. And the question is sometimes a template nobody meant: "do you have a bachelor's degree" on a role that does not need one. The guide on jobs without a degree is about that case.
What the recruiter sees
A list of records, sortable and searchable, with a status column. One click opens a record: the parsed fields on the left, the resume on the right, the form answers below. A rejection is one click, with a reason code and, optionally, a template email.
The recruiter's job is to turn four hundred into eight. They do it fast. The things that survive a fast read are the summary, the first role, and whether the posting's terms are there. The guides on the summary and on bullets are about those ninety seconds.
Routing
After the screen, the system routes. A hiring manager gets a shortlist. Interviewers get a scorecard to fill in. Everyone's notes attach to the record. An offer is generated from the record. If the employer uses the same system for onboarding, the record becomes the employee file.
This is why the same company uses the same system for every role, and why applying to two roles at one company creates two applications on one record, which the recruiter sees side by side.
The three things it never does
- It never ranks resumes by quality. There is no score. Products that sell a score are not the hiring system.
- It never reads the cover letter for keywords. The letter is attached and read by a person, if at all.
- It never shares your record with another employer. Records belong to the company. The same vendor at two companies is two databases.
Which systems
The board on this site reads from the hiring systems employers publish through: Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, iCIMS, Taleo, BambooHR, JazzHR and dozens more. Each one has a form with its own shape, and the guides on applying through each one cover the shape.
Questions
Can I see my status in the ATS?
Some show it to you on a candidate portal: Workday, iCIMS, Taleo. Most do not, and the status you see on a job board's "application viewed" is the board's, not the employer's.
Does the ATS tell the recruiter I used a job board?
Yes, as the source field. It does not change the outcome. It tells the employer which boards work.
If I withdraw, does the record go away?
The application moves to withdrawn. The record stays. Reapplying later attaches a new application to the same record, which is fine and is what the system expects.
Is my data safe in there?
As safe as the employer keeps it. Privacy law in the EU and in some US states gives you the right to ask what they hold and to have it deleted. The vendors' privacy pages say how.
Does a referral bypass the ATS?
No. A referral is a source value, and often a flag the recruiter filters on first. It gets your record read early. It does not skip the record.