How applicant tracking systems work, from upload to interview list

What an ATS is, and who uses one

An applicant tracking system is the software an employer uses to post jobs, collect applications, store candidate records, and move people through stages from applied to hired. The big names include Workday, Greenhouse, Lever, iCIMS, SAP SuccessFactors, Taleo and SmartRecruiters; there are hundreds of smaller ones. Nearly every large company and most mid-size ones use one; many small businesses use the built-in tools of a job board, which do the same job in simpler form.

The ATS exists for the recruiter, not the candidate. Its purpose is to make a few hundred applications per role manageable for one or two people. Everything it does to your resume follows from that.

Step 1: Upload and parsing

When you upload a resume, the system extracts the text and tries to structure it: name, email, phone, location; each job with title, employer and dates; education; skills; certifications. This is parsing. Many systems then prefill the application form from the parsed data, which is why you sometimes see your own job title in the wrong box.

Parsing is where layout matters. Columns, tables, headers, icons and image-based PDFs confuse the extraction, and a resume that parses badly enters the system with missing or scrambled fields. From that point on, every later step works from the scrambled version.

Step 2: Knockout questions and hard filters

Most applications include a few yes/no questions: do you have the right to work here, do you hold the required licence, are you willing to relocate, do you have at least N years of experience. These are the only place where the system rejects on its own. A "no" on a question the employer marked as required moves the application to a rejected status, usually with an automatic email. No human reads it.

Hard filters can also run on parsed data, for example a minimum years-of-experience computed from your dates, which is why inconsistent dates are dangerous.

Step 3: Ranking and matching

For applications that pass the knockouts, most systems compute some kind of match against the job description. The usual method compares the terms in the posting (title, skills, tools, qualifications) with the terms in your parsed resume, weighting exact matches on the title and required skills most heavily. Some newer systems use semantic matching that recognises synonyms; most still rely mainly on literal overlap.

The output is a score or a rank, shown to the recruiter as a percentage, a star rating or simply a sort order. This is not a pass/fail; it is the order in which the recruiter will look.

Step 4: What the recruiter actually does

A recruiter opens the role, sees the list sorted or filtered by match, and starts reading from the top. For a role with 300 applicants, they may read 30 to 50 resumes properly and skim another 50. The rest are never opened. They are not rejected by the software; they are simply never reached, which from the candidate's side feels the same.

Recruiters also search the database directly: "Python AND Django, within 50 km, applied in the last 90 days". A resume with the right terms shows up in these searches for other roles, months later. This is a second reason to use the posting's vocabulary.

Step 5: Stages, notes and the "black hole"

From the shortlist, candidates are moved through stages: phone screen, interview, offer. Each move can trigger an email. Candidates not moved stay in "applied" indefinitely, which is the black hole: nobody decided to reject you, nobody got to you, and the system has no stage for "never read". Many companies eventually bulk-reject everyone left when the role closes, which is the rejection email that arrives three months later.

What this means for your resume

• Parse first: single column, standard headings, text-based file, consistent dates. If the extraction fails, nothing else helps.
• Answer knockouts honestly and exactly; they are the only automatic rejection.
• Use the posting's vocabulary for every requirement you meet, so the ranking puts you in the part of the list that gets read.
• Put the match where the recruiter looks first: title, summary, top bullets.
• Apply early. Recruiters read from the top of a list that fills over days; early applicants are read when the shortlist is still empty.
• Check the resume against the posting before sending; it is the only way to see what the system will see.

Three myths, briefly

• "The ATS rejects 75% of resumes." Knockout questions reject some; the rest are ranked, not rejected. The figure usually quoted has no traceable source.
• "You need a 100% keyword match." You need to be in the top portion of the list. Above 80% with all must-haves present is typically enough.
• "Submitting a referral skips the ATS." The referral is logged in the same system; it changes who reads you and when, not whether the resume is parsed.