ATS
Most ATS advice is folklore. This is what the software actually does with your file, and what it never does.
An applicant tracking system is the database an employer keeps candidates in. It parses the file you upload into fields, stores the result against the vacancy, and gives recruiters a way to search and filter what they have collected. That is the whole of it, and almost everything alarming written about these systems describes a machine that does considerably more.
The distinction matters because it changes what you should do. If the system were a judge, the sensible response would be to game its scoring. Because it is a filing cabinet with a search box, the sensible response is to be legible in it: upload a file that parses cleanly, and use the words the employer uses for the work you have actually done.
There is one place where genuine automation happens, and it is not the resume. The screening questions on the application form — work authorisation, qualifications, notice period, location — are evaluated on submission and can close an application immediately. Those are questions you answer, which means they are worth answering carefully rather than quickly.
Key terms
- ATS (applicant tracking system)
- Software an employer uses to receive, store and progress job applications. It handles the requisition, the candidate record, the interview stages and the compliance trail. It is bought to run a hiring process, not to evaluate resumes, and the evaluation features it offers are optional.
- Parsing
- The conversion of an uploaded file into structured fields — contact details, employers, titles, dates, education, free text. Everything the system later does operates on the parsed record rather than on the document you saw, which is why the gap between the two is where applications go missing.
- Knockout question
- A screening question on the application form whose answer can disqualify you immediately: right to work, minimum qualification, willingness to relocate, notice period. This is the automatic rejection people attribute to resume scanning, and it runs on your own stated answers.
- Match score
- An optional similarity score between a parsed resume and a job requisition, used where it exists to order the candidate list. It affects what a recruiter reads first rather than who is excluded, and many teams sort by date instead.
Frequently asked questions
Do most resumes really get rejected by software before a human sees them?
That claim is repeated constantly and is not a good description of how these systems are configured. The realistic failure is quieter: a recruiter searches the stored records for the terms that matter to them, and a resume that parsed badly or used different vocabulary is simply not in the results. Nothing rejected it; it was never returned by the search.
What file format should I upload?
A text-based PDF unless the application asks for something else, in which case give them what they ask for. The only format that reliably fails is an image-based PDF or a scan, because it contains no text at all. You can check yours in two seconds by trying to select a word inside it.
Should I match the job description word for word?
Match its vocabulary where you have genuinely done the thing, and nowhere else. If the posting says "transaction monitoring" and you wrote "reviewed flagged payments", use their term — it describes the same work and it is what a recruiter will search for. Do not insert terms for work you have not done: it fails at the interview, which is a worse place to fail.
Is a plain-text resume the safest option?
It is the safest for parsing and among the worst for the human stage, which is the stage that actually decides. A clean single-column document with ordinary bullets and bold headings parses just as reliably and is far easier to read. Optimise for both, because passing the first stage only matters if you can also pass the second.