Applicant tracking systems have a reputation as robot gatekeepers that reject resumes at random. Having worked inside them for years, I can tell you the reality is less dramatic and more practical: an ATS is a database with a search box, plus a workflow for moving candidates through stages.
Understanding what it does — and does not do — changes how you should write.
What the system does
- Stores your application with the resume, cover letter, answers to application questions and any assessments.
- Parses the resume into fields — name, contact details, employer, title, dates, education, skills. This is the step most formatting advice is about.
- Indexes the text so recruiters can search across thousands of applications for terms like "SOC 2", "Spanish", "Figma" or "Class A CDL".
- Runs the workflow — knockout questions, stage changes, interview scheduling, email templates, compliance records.
- May rank or score candidates against the posting's requirements, depending on how the employer configured it.
What it does not do
It does not read your resume the way a person does. It does not understand that "led a team of eight" implies leadership unless the word appears somewhere it can match. It does not admire your design. And it rarely "auto-rejects" on formatting alone.
What actually removes candidates early:
- Knockout questions — work authorization, minimum experience, licenses, salary expectations. These are answered in the form, not read from your resume.
- Missing must-have terms — if the recruiter searches for a certification and your resume never says it, you are not in the result set.
- Unparseable structure — two-column layouts, tables, text boxes and images that lose your dates, titles or skills.
- Applying to the wrong requisition — the system routes by job ID; a resume sent to an old posting may sit in a closed workflow.
How recruiters actually use it
Most of the time, a recruiter opens a requisition, searches or filters the pipeline, and reads the top handful of results. That means your resume competes in two ways: first to be findable for the search terms, then to survive the human scan once opened. A resume can be beautifully written and never appear in that first search.
The ATS does not decide whether you are qualified. It decides whether a busy recruiter can find and understand you in the thirty seconds they have.
Why the parsing step matters to you
If your resume parses correctly, your job titles appear next to your employers, your dates line up, your skills land in the skills field, and your text is searchable. If it parses badly, the same document can look like a different person's career: dates attached to the wrong job, a degree with no institution, a skills list merged into an address.
The fix is not to write for robots. It is to use a structure that humans and parsers read in the same order — one column, standard headings, selectable text, plain lists. That is also the structure that reads best on a phone screen, which is where more and more first reads happen.
Bottom line
The ATS is a filing cabinet with a search function, not an oracle. Write evidence-rich bullets for the human, keep the structure parseable for the software, and make sure the specific terms from the posting appear where they belong. Start with our ATS checker to see how your current draft reads, then fix the structure before you rewrite a single bullet.
Paste your resume and a job posting for an instant, private readability score.