How ATS Systems Actually Work: The Mechanics Nobody Explains

Everything you have been told about ATS systems is probably wrong.

The internet is full of ATS advice. “Beat the ATS.” “ATS-proof your resume.” “The ATS is rejecting you before a human ever sees your application.” Most of this advice ranges from oversimplified to completely false.

I have used six different ATS platforms over 14 years of hiring. I have seen how they actually work from the administrative side, the side candidates never see. And the reality is very different from what the resume optimization industry tells you.

What an ATS Actually Is

An Applicant Tracking System is, at its core, a database with a workflow engine attached to it.

That is it.

It is not an AI. It is not a robot reading your resume and making decisions. In most implementations, it is closer to a very sophisticated filing cabinet that helps recruiters organize, search, and track candidates through a hiring pipeline.

Here is what an ATS actually does:

It collects applications. When you click “apply” on a job posting, your resume and information go into the ATS. It becomes a record in a database.

It parses your resume. The ATS attempts to extract structured data from your resume: your name, contact information, work history, education, and skills. It takes your document and turns it into searchable database fields.

It manages the pipeline. The ATS tracks where each candidate is in the process: applied, screened, phone interview, on-site, offer, hired, rejected. It is the system of record for the entire hiring workflow.

It enables searching and filtering. This is the part that matters most for candidates, and the part that is most misunderstood.

The Great ATS Myth: Automatic Rejection

The number one myth about ATS systems is that they automatically reject resumes that do not meet certain criteria. “75% of resumes are rejected by ATS before a human ever sees them” is a statistic you have probably seen. It is misleading at best.

Here is what actually happens in most companies I have worked with:

A job posting goes live. Applications come in. They land in the ATS. A recruiter opens the ATS and looks at the applicant pool.

If the pool is small (say, under 50 applicants), the recruiter will often manually review every single application. No filtering. No keywords. They just read through them.

If the pool is large (200, 500, sometimes thousands of applicants), the recruiter uses the ATS search and filter functions to narrow the pool. They might search for specific skills, filter by years of experience, or sort by location.

This is not automatic rejection. This is a human using search tools.

The distinction matters enormously. When your resume does not show up in a recruiter’s filtered search results, it is not because an algorithm decided you were unqualified. It is because your resume did not contain the specific terms the recruiter searched for.

Your resume is still in the system. It was not deleted. It was not rejected by a robot. It just did not appear in a search query.

Here is what I find interesting: the candidates who consistently show up in my search results are not better qualified. They are better at matching vocabulary. Their resumes mirror the job description language almost exactly. Not approximately. Exactly. The same phrase from my job posting appears in their summary, their bullet points, their skills section. And when I search for a different role, the same candidates appear again, but with a slightly different resume version that matches that job description just as precisely.

I did not understand how they were doing this until recently. Nobody has the time to manually rewrite a resume for every single job posting, not at the volume you need to be applying. More on this in a moment.

How Parsing Actually Works

The ATS parser is the component that takes your resume document and extracts structured information from it. This is where formatting actually matters, but not in the way most advice suggests.

Modern ATS parsers are significantly better than they were five years ago. The major platforms (Greenhouse, Lever, Workday, iCIMS, Taleo) have invested heavily in parsing technology. They can handle most standard resume formats without issues.

That said, parsers can still struggle with:

• Tables and multi-column layouts. The parser reads left to right, top to bottom. A two-column layout can result in jumbled text where your job title ends up merged with an unrelated skill.
• Text embedded in images or graphics. If your skills section is a visual chart or graphic, the parser cannot read it. That information does not make it into the searchable database.
• Headers and footers. Some parsers skip document headers and footers entirely. If your contact information is only in the header, it may not get parsed.
• Non-standard section headings. If you label your experience section “My Professional Journey” instead of “Experience” or “Work History,” the parser may not categorize it correctly.

The fix is straightforward: use a clean, simple layout with standard section headings. This is not about dumbing down your resume. It is about ensuring the system can read what you wrote.

What Recruiters Actually Search For

This is the information that changes how you approach ATS optimization. When recruiters search within an ATS, they typically use:

Job title keywords. If the role is for a “Product Manager,” the recruiter will search for “product manager” in the applicant pool. If your resume says “Product Lead” or “Product Owner” but never uses the exact phrase “Product Manager,” you may not appear in that search.

Hard skills. Specific technologies, tools, certifications, and methodologies. “Python,” “Salesforce,” “PMP,” “Agile,” “SQL.” These are almost always searched as exact terms.

Company names. Hiring managers often tell recruiters to look for candidates from specific companies. “Find me people from Stripe, Square, or PayPal” is a real request I have heard many times.

Years of experience. Most ATS platforms allow filtering by parsed years of experience. This is where the “must have 5+ years” filter lives.

Location. Especially post-pandemic, location filtering is heavily used. If your resume does not clearly state your location or indicate willingness to relocate, you may get filtered out of location-based searches.

The Real Optimization Strategy

Now that you understand how ATS systems actually work, here is how to approach them intelligently:

Mirror the job description language. If the posting says “project management,” use “project management” on your resume, not just “managed projects.” This is not keyword stuffing. It is using the same vocabulary as the people who will search for you.

Include both acronyms and full terms. Write “Search Engine Optimization (SEO)” so you appear whether the recruiter searches for the acronym or the full phrase.

Use standard section headings. Experience. Education. Skills. Certifications. Do not get creative with section names.

Keep the formatting simple. Single column. Standard fonts. No tables, no graphics in content areas, no headers/footers for critical information.

List specific tools and technologies. Do not say “experienced with CRM platforms.” Say “Salesforce, HubSpot, Pipedrive.” Recruiters search for specific tool names, not categories.

State your job titles clearly. If your internal title was obscure (“Innovation Catalyst III”), add the functional equivalent in parentheses: “Innovation Catalyst III (Senior Product Manager).”

The Hard Truth About Scale

Now you know the strategy: mirror the job description language, match the keywords, tailor for each role. It works. I see it work every day from my side of the screen.

But let me do the math that nobody in the career advice industry wants to do.

The average job search requires 50-100 applications to generate 5-10 interviews. That is not my opinion. That is the data I see in my own applicant pools. The candidates who land offers are the ones who applied broadly AND tailored specifically.

Tailoring a resume properly (reading the job description, identifying the key terms, rewriting your bullets to mirror the language, adjusting your skills section, updating your summary) takes 30-45 minutes per application. Let us call it 35 minutes on average.

50 applications × 35 minutes = 29 hours of resume tailoring alone.

That does not include writing cover letters. That does not include filling out application forms. That does not include research. Just the resume tailoring.

Now add the cover letter. A good cover letter that references the specific role takes another 20 minutes. And the application form (copying your information into fields, answering screening questions) adds another 10-15 minutes.

50 applications × 65 minutes each = 54 hours. That is more than a full work week.

Most people cannot do this. So here is what actually happens: they tailor the first 5-10 applications carefully. Then they get tired. Then they start sending the same generic resume to every job. Then they wonder why they stop hearing back.

I can see this pattern clearly in my ATS. The early applications in a posting’s lifecycle tend to be better tailored. The later ones are generic. Candidates are running out of energy, and their applications show it.

This is the fundamental problem of the modern job search: the system rewards tailoring, but tailoring at scale is humanly unsustainable.

Some candidates have figured this out. I mentioned earlier that I keep seeing the same people show up across multiple roles with perfectly tailored resumes each time. They are using AI tools that read the job description and generate a tailored resume version automatically.

The one I have heard candidates mention most, and the one whose output I can recognize because it is consistently well-matched, is Submix. It does three things that matter from my perspective as a hiring manager:

1. It reads the job description and generates a tailored resume. Not a generic “optimized” version. A version that mirrors the specific language of my specific posting. The keywords match my search queries because they were pulled from the same source: my job description.

2. It writes the cover letter. Matched to the role, referencing the company and position specifically. I can tell when a cover letter was written for my role versus copied from a template. Submix’s output reads like the former.

3. The candidate still reviews everything before submitting. This is what separates it from the blind auto-apply tools that flood my inbox with mismatched applications. Submix prepares the materials. The candidate checks them. Nothing goes out without approval. That means the applications are tailored AND intentional, which is exactly the combination that gets through.

The result: a candidate using Submix can submit 50 tailored applications in the time it would take to manually tailor 5. Every single application has the right keywords, the right formatting, the right language. Every one shows up in my searches.

Is it fair? That is a different question. But the hiring system was never designed for fairness. It was designed for efficiency. The ATS filters for keyword matches. Submix generates keyword matches. The candidates using it are playing the same game as the system. And from my side of the screen, they are winning.

The ATS is not your enemy. It is a search engine. And like any search engine, the key to showing up in results is making sure your content matches what people are searching for, at the scale that the market demands.

In the next chapter, we will break down the specific parsing differences between the major ATS platforms and how to handle each one.