What Is an Applicant Tracking System? A Plain Explanation

An applicant tracking system is a database with a parser attached. That is the entire thing. It is worth starting there, because almost every myth about these systems comes from imagining something more dramatic: a gatekeeper, a filter, an algorithm deciding your fate. It is filing software, and understanding that changes what you should do about it.

What it actually does, step by step

It receives your file. You upload a PDF or a Word document to an application form. That file is stored, and then something more consequential happens to it.

It parses the file into fields. A parser reads the text and tries to work out which part is your name, which is your email, where employment history starts, which lines are job titles, which are dates, and which are education. The output is a structured record: a row in a database with columns.

It stores that record. From this point on, your resume file is an attachment. The thing the company works with is the record built from it, and if that record is wrong, the file being perfect does not help.

It lets recruiters search and filter. A recruiter with two hundred applicants does not read two hundred resumes. They filter: this location, this many years, this skill. Then they read what comes back.

It tracks the process. Which stage each candidate is at, who has interviewed them, what the notes say, who rejected whom and when. This is the part the software is actually named after, and the part candidates never think about.

Who uses one, and why

Essentially every company above a handful of employees, and a great many below that, because the free and cheap tiers are widely available. The reasons are mundane. A single posting can attract hundreds of applications, and email cannot manage that. Hiring is also legally sensitive in most jurisdictions, and companies need a record of who applied, who was considered and on what basis.

You have probably encountered several by name without noticing: Workday, Greenhouse, Lever, iCIMS, Taleo, Ashby, SmartRecruiters. When an application redirects you to an unfamiliar domain and asks you to create yet another account, that is the company's ATS rather than the company.

Four myths worth retiring

"The ATS rejects you automatically." Overwhelmingly it does not. Auto-rejection rules exist but are usually limited to knockout questions the employer set explicitly: are you legally able to work here, do you hold the required licence. Beyond that, nobody is rejected by the software. They are simply never returned by a search, which feels identical from your side and is a different problem with a different fix.

"75% of resumes are never seen by a human." This number circulates constantly and has no traceable source. It is also incoherent with how recruiters actually work, since the filtering is done by a person running searches. Be suspicious of any advice built on it.

"There is an ATS score you can raise." No applicant tracking system shows candidates a score. There is no number inside Workday or Greenhouse for you to move. Every ATS score you have seen, including ours, is a model built by whoever showed it to you, estimating a match. That is a reasonable thing to build, and it is only useful if the method is published.

"Hidden keywords in white text will get you through." They are trivially detectable, since the text is in the file regardless of colour, and being caught reads as dishonesty. They also do not achieve much, because a resume matching on terms and nothing else fails the moment a person reads it.

What actually goes wrong

The failures are specific and mechanical rather than mysterious.

• Two-column layouts interleave when a parser reads across the full page width, producing alternating fragments of sidebar and job history.
• Tables flatten into an unpunctuated run of words, which is why a skills grid so often disappears.
• Header and footer regions are frequently discarded, so contact details placed there can vanish entirely. This is how people become uncontactable.
• Images and graphics contain no text. A certification shown as a badge is, to the system, a certification you do not have.
• Inconsistent dates produce a garbled employment history and invent gaps that were never there.

Do they all behave the same way?

No, and this is why format advice is stated as a floor rather than a rule. Parsers vary in quality, and a layout one system handles gracefully another mangles. Since you cannot know which system is on the other end of a given application form, the sensible approach is to send something that every parser handles: one column, standard headings, real text. It costs you nothing and removes the variable entirely.

How to see what it sees

The most useful two minutes you can spend on this subject, and it needs no tool. Open your resume PDF, select all, copy, and paste into a plain text editor.

That is approximately what a parser extracts. Check five things: is the reading order right, or do columns interleave? Did your contact details survive? Are all the dates present and in one format? Did the skills section become a readable list or a run of words? Are your links visible as addresses rather than as the word "portfolio"?

If that pasted text reads as a coherent document, you have solved the parsing half of the problem and can move on to vocabulary. If it does not, fix that first, because keyword work on a file that extracts badly is effort spent on text that lands in the wrong fields.

What happens after you apply

The tracking half of the software is invisible to candidates and explains a lot of otherwise baffling behaviour. Your application enters a pipeline with named stages, and every action a recruiter takes is recorded against your record: viewed, screened, forwarded to the hiring manager, scheduled, rejected, and at which stage.

This is why the silence is usually not personal. A requisition can be paused, refilled internally, or absorbed into a reorganisation, and the candidates in the pipeline simply stop moving. It is also why applying repeatedly to the same company creates a visible pattern: each application is a record attached to you, and someone reviewing your history sees all of them.

Your record usually outlives the application. Most systems keep candidates in a searchable pool, which is the mechanism behind being contacted a year later about a role you never applied for. It is a decent argument for making the record accurate even when you expect a rejection: you are not only applying for this job, you are filing a description of yourself that a recruiter may search next spring.

Why the application form asks everything twice

Uploading a resume and then retyping the same employment history into fifteen form fields is the most universally hated part of applying, and it happens for a specific reason: the parser is not confident. Those fields are the structured record, and the form is asking you to confirm or correct what it extracted. That is worth knowing, because it means the fields are the data, not a formality. Where a form pre-fills something wrong, fixing it matters more than the resume you attached, since the corrected field is what gets searched.

The short version

Send a plain, single-column file with conventional headings to every application form. Use the words the posting uses, where they are genuinely true of you. Keep a designed version for the humans who will read it directly. That is essentially the whole discipline, and everything more elaborate than that is usually someone selling a solution to a problem you do not have.