What is an ATS? How applicant tracking systems work

Every time you apply for a job online, your resume goes into an applicant tracking system, usually shortened to ATS. Career advice often treats it as a gatekeeper that throws most people out before a human looks. The software is more ordinary than that, and the real risks are more specific than that, which makes them easier to deal with.

This guide covers what an ATS is, what employers use it for, what happens to your application after you press submit, which popular claims have no public evidence behind them, and the short list of things you control. It uses no scare numbers. Where something differs between employers, which is most of it, the guide says so. If you want the formatting rules that follow from all this, they are in the ATS-friendly resume guide.

What an ATS is, in plain terms

An applicant tracking system is software employers use to run the paperwork of hiring. Someone in HR or a hiring manager creates the job in it, publishes the posting to the company's careers page (and often to job boards), and every application lands in one place instead of in a dozen inboxes.

Four jobs cover most of what it does.

Around those four sit smaller functions: posting to job boards, sending automatic emails, scheduling interviews, reporting how many people applied and where they came from, and keeping records the employer may need for policy or legal reasons.

Look at what is missing from the list: a verdict on whether you deserve the job. Judgement stays with the people using the system, plus whatever rules the employer chose to switch on, which a later section covers.

Who uses an ATS, and why

Four questions come up most. Why do employers bother, which names will you meet, what do you meet in different kinds of workplace, and how does an ATS differ from the other tools in the chain?

Why employers use one, and what it costs you

The employer's reasons are practical. A posting can attract far more applications than one person can handle by email. A system lets the same questions go to everyone, keeps every record in one place, lets several people leave notes on the same candidate, and gives the company a record if anyone later asks how a hire was made.

The costs land on applicants, and they are real.

Knowing the employer's reasons helps you read the process generously. The system is mostly there to keep a large, shared task in order. It is a tool, and you get the most from it by giving it clean inputs.

Which products exist, and what you will meet

Large employers commonly use one, because hundreds or thousands of applications cannot be handled in an inbox. Many mid-size employers and staffing agencies do too. A small business may have a basic hiring tool built into a payroll or HR product, or it may read emails and keep a spreadsheet. You will meet very different experiences: a hospital system's long portal, a retailer's tap-through application on a phone, a small contractor's email address.

Names you may recognize include Workday, Greenhouse, Lever, iCIMS, Oracle Taleo, SmartRecruiters, Ashby, Jobvite and BambooHR. They are examples of products that exist, and the list is not a statement about what any employer uses or how a product behaves inside. Two employers on the same product can set it up quite differently, with different stages, different screening questions and different people looking at different things.

You can often get a hint about the product from the web address of the application page, which sometimes includes the vendor's name. That tells you the brand. It does not tell you how the employer configured it.

ATS, job board, CRM: which is which

The vocabulary gets muddled, and the advice for each piece differs, so here is how they separate.

Most job boards pass your application to the employer's ATS, or let you apply on the employer's own page where the ATS lives. The resume checker sits outside the whole chain, which is worth remembering when you reach the section on scores.

What happens to your application, step by step

1. 1

   You submit

   Your file, your form answers and any screening questions go to the employer's system.

2. 2

   The file is read

   The system tries to turn your resume into fields: name, contact details, jobs, dates, education, skills.

3. 3

   A record is created

   Your answers, your file and the fields become one candidate record attached to that job.

4. 4

   Rules may run

   If the employer set them up, certain answers can tag you, move you to a stage or end the application.

5. 5

   People look

   A recruiter reviews new applicants by searching, filtering or working down a list.

6. 6

   You move or you stop

   Reviewed, shortlisted, passed on. Each change is logged and may trigger an email, depending on settings.

Most of what matters happens in steps two, four and five, so each gets its own look.

Step 2: the file is read

Many systems try to read the resume you upload and fill in a structured record from it. This is called parsing. The software looks for patterns it has seen before: a name at the top, an email address, a job title followed by an employer and a date range, a section called Education.

Parsing is pattern matching, and patterns break. Some systems show the recruiter the original file next to the parsed fields, so a person can still read your document as you wrote it. Others lean heavily on the fields. Workday's administrator documentation, which is public, says parsing results can vary with the format and word order of the resume, and it recommends resumes without images or image-based styles.

Here is how a single entry might be handled, using a made-up example.

1. 1

   Medical Assistant, Lakeshore Family Clinic Tucson, AZ | June 2021 to present

   On the page

   A person reads this as a job: a title, an employer, a place and a start date.

2. 2

   Title: Medical Assistant Employer: Lakeshore Family Clinic Start: 2021-06 End: present

   Fields that are easy to fill

   A title, a comma and a name is a pattern parsers see constantly. Month and year are easy to read.

3. 3

   Title: Medical Assistant, Lakeshore Employer: Family Clinic Tucson Start: (blank)

   Fields that can go wrong

   A line break in the wrong place or a date written as summer 2021 can split a name across fields or leave one empty.

4. 4

   A search for "Lakeshore Family Clinic" finds no match on this record.

   Why it matters

   In many setups search and filters run on the parsed fields. A person reading the file would see the job, and a search may not.

A messy parse can leave a record that looks thinner to a search than the file looks to a person. The fix is cheap: make the pattern easy to read. How to check your resume for ATS problems in 10 minutes shows how to see your own file the way a parser might.

Step 4: rules can run

This is the step people mean when they say software rejects people, and it is narrower than the myth. An employer can attach a rule to the answer to a screening question. The documented examples are about answers, not about your resume text.

Greenhouse's public help center describes it plainly: its application rules can tag a candidate, move them to a later stage or reject them based on how they answered custom application questions, depending on the plan the employer pays for. Greenhouse's application rules overview is the page. The rule acts on the answer you gave to a question. Nothing in that documentation describes a score for your resume.

Other products have their own versions. The point holds across them: an employer decides which questions to ask and what to do with the answers, and a yes or no you click quickly can have consequences.

Because the answers to screening questions can drive rules, it is worth knowing what they tend to look like. These four are invented, written the way many real forms phrase them.

1. 1

   Are you legally authorized to work in the country where this job is based?

   Work authorization

   A yes or no an employer may use to sort. Answer exactly and truthfully. The wording and the legal background vary by country.

2. 2

   Do you hold a current commercial driver's license, Class A?

   Required credential

   When a posting calls a credential required, it is often asked this way. A no may end the application, so read it twice before clicking.

3. 3

   Are you able to work weekends and some evenings?

   Availability

   For shift work this can be the deciding question. If your honest answer is partly, look for a comment box before choosing a button.

4. 4

   How many years of experience do you have with inventory control software?

   Years of experience

   A number field. Count what you actually did, and count it the way the question asks. A rough, honest number beats a stretched one.

Two habits protect you. Read each question as a literal yes or no, because a rule will. And if a question has no good answer for your situation, such as a license you are partway through earning, look for a free-text field, or contact the employer, rather than choosing the nearest button.

Some forms also carry voluntary questions, such as self-identification for the employer's reporting. Where they are optional, the form normally says so and lets you decline. The explanation printed on the form is the authority here, because it differs by country and by employer.

Step 5: people look

Eventually a person opens a list. How they work through it depends on the employer and on volume. A recruiter with a handful of applications may read each one. A recruiter with a flood may search the pool for the words that define the role, filter by location or a required credential, and read the strongest-looking group first.

Neither approach is mysterious. In both, being easy to read and easy to find matters, and nothing about it requires a trick.

A useful exercise is to take the reader's chair. Imagine forty applications for one role and an hour to get through them. What would you look at first? Probably the job title and the most recent employer, then whether the dates make sense, then whether the tools or credentials named in the posting appear. You would also stop reading the moment a document became hard to follow. You cannot know what any particular reader does, and the exercise is still a fair guide to where to put your effort: the top of the first page, the job titles, the dates, and the handful of terms the posting leans on.

One posting from the employer's side

It helps to see the whole life of a posting once. The timeline below is an invented illustration. Real ones run from days to months.

1. Day 1: the role is approved

   The hiring manager and recruiter agree on the title, the requirements, the stages and any screening questions, and enter them in the system.

2. Day 2: the posting goes live

   It appears on the careers page and may be sent to job boards. From here on, applications arrive and attach themselves to the job.

3. Week 1: first look

   The recruiter reviews new applications as they come in, or in a batch. Some are moved to a phone screen stage, and some are set aside.

4. Weeks 2 and 3: screens and interviews

   Phone screens happen. Interviewers leave notes and ratings in the candidate records. The hiring manager picks a shortlist.

5. Week 4 or later: decision

   An offer goes to one person. The others are closed out, sometimes by an automatic email, sometimes by a personal one, sometimes by nothing.

Two things follow. First, a posting that attracts many applications is reviewed in batches, which is why a clear, scannable resume matters. Second, silence at the end is common and says very little about your resume in particular. The role may have been filled, paused or closed before anyone reached you.

How recruiters find people

Search is the feature a job seeker feels most. A recruiter types a word or phrase, the system returns records containing it, and the recruiter narrows with filters such as location, stage or a tag.

Search behaves like search anywhere. It generally matches the words that were typed. Some systems handle plurals and word endings, and many will not connect an abbreviation to its long form or one job title to a similar one. How a given system treats this varies, so the safe habit is to write the term the way an employer would type it, and to include both the long form and the abbreviation once if both are common.

The right-hand column is not wrong, and a person reading it would understand. It just gives a search fewer words to catch. Choosing the term the employer used in the posting, where it is accurate, is the same habit as finding the keywords in a job description.

What the other side of the screen can sound like

The conversation below is invented, to show how search, parsing and judgement mix in one small, ordinary case. Real teams differ.

• Recruiter

  We had far more applications than I can read closely for the dispatch coordinator role. I filtered on location and the weekend availability question, then searched for dispatch and the scheduling software the team uses.

• Hiring manager

  Did you read them, or count matches?

• Recruiter

  I read the group that matched on the title and tools. Two had no dispatch in the text, but their last job was transport planner, so I opened those as well.

• Hiring manager

  Good. Anyone odd?

• Recruiter

  One resume came through as a single block of text. I could read it, but the fields were empty, so it never showed up in my filter. I found it by sorting by date.

• Hiring manager

  Add that one to the shortlist of six. Their last two jobs are exactly what we need.

In that story, a diligent recruiter and a convenient sort order rescued the record. You cannot count on either, which is why a file that reads cleanly is worth the ten minutes it takes to check.

Ranking, scoring and AI: what is public and what is not

Candidates do not see a score in an employer's system, and there is no standard one. A few facts are safe to rely on.

• Some products and add-on tools can rank or recommend candidates. Whether a given employer has switched one on, and what it looks at, is not public.
• The score a resume checker gives you is made by that checker, using its own rules. An employer does not see it.
• Whether or not a ranking tool is in use, how much of the decision is handed to software is the employer's choice, and the employer is the only one who knows.
• In some places, rules about automated hiring tools are being introduced. If you want to know what applies to you, check what your local authority says.

The honest summary is that how a particular employer's system treats you is something an outsider cannot know. That is uncomfortable, and it is also why advice that promises to beat the system should make you cautious.

Myths and what is publicly known

What you actually control

Strip away the myths and a short list is left. Each item is within your reach and costs little.

Two smaller things sit beside those. Some employers review applications as they arrive, and a posting that says applications are reviewed on a rolling basis is telling you so, which is a reason to apply early when you are ready. And a rushed application with a misclicked answer costs more than a day's delay, so ready beats early.

A short routine turns those three into habit.

Before you submit any application

• Open your PDF and check that you can select and search its text
• Compare your resume with the posting and mirror its terms where they are true
• Read every screening question as a literal yes or no
• Check auto-filled fields against your resume and fix any that are wrong
• Use the same name, email address and dates as your other applications
• Save the posting text and the version you sent, in case the page changes
• Note the date and the employer in a tracker so you can follow up

0 of 7 done

What this looks like in different fields

Your experience of an application depends heavily on the kind of employer. Here are four illustrative cases, and what to prepare for each.

After you apply: records, talent pools and reapplying

Your application does not vanish when the role closes. The employer may keep the record for a period set by its own policy and local rules, and recruiters can search past applicants when a similar role opens. Staffing and recruiting agencies often work from a pool of candidates they already hold.

That has two practical effects. A clean record helps you later as well as now. And consistency matters: if one application shows a job ending in March and another says May, a person comparing them will wonder which is right. Tailoring wording to each posting is fine and normal, so long as the facts, meaning employers, titles and dates, never change between versions.

If you applied before and were passed over, applying again for a different role is generally fine. Some employers limit repeat applications to the same posting, and the careers page or the confirmation email will say so.

Common mistakes

Where SnugCV fits

SnugCV builds a profile once from your uploaded resume, then rewrites the summary, skills order and bullets in a posting's own language for each job, copying employers, titles, dates and education unchanged. Both templates export a single-column PDF with real, selectable text, and every change comes with a plain-language note so you can check it. SnugCV makes no claim about what any employer's system will do with the file.

If you track what you have sent and where each application stands, the free job tracker is the other half of staying organized.

Keep going

Start with the practical follow-ups in this cluster: the formatting rules that matter for an ATS-friendly resume and a ten-minute check for ATS problems. For the words themselves, see how to find the keywords in a job description, and for the reasoning behind changing a resume per job, why tailor a resume for each job.