What Is an ATS and How Does It Work?

What Is an ATS and How Does It Work?

What an ATS really does with your resume: parsing, knockout questions, recruiter search and match scores, and what to change because of it.

If you have applied for a job through a company careers page, Naukri, or LinkedIn, your resume almost certainly went into an applicant tracking system (ATS) before any person saw it. Most job seekers have heard the term, but the popular picture of an ATS as a robot that "auto-rejects" resumes is only partly right. Understanding what the software really does makes it much easier to decide what to change on your resume and what to ignore.

What an ATS is

An applicant tracking system is the database and workflow tool a hiring team uses to manage candidates. It stores every application, tracks which stage each person is at (applied, screened, interview, offer), lets recruiters leave notes, schedules interviews, and produces reports for hiring managers. Common examples you will run into are Workday, Greenhouse, Lever, SuccessFactors, iCIMS, Taleo and SmartRecruiters at larger companies, and Zoho Recruit, Freshteam or Keka at many Indian startups and mid-sized firms.

The important point: an ATS is primarily a recruiter's filing cabinet with a search bar. Screening is one of its features, not its whole purpose.

What happens to your resume after you click Apply

A typical application passes through these steps:

  • Upload and parsing. The system extracts text from your PDF or Word file and tries to split it into fields: name, phone, email, current company, job titles, dates, education, and skills.
  • Profile creation. Those fields become a candidate record. Many portals then ask you to "review" the auto-filled form; whatever is in that form is what recruiters see in their list view.
  • Screening questions. Questions like notice period, current location, expected CTC, or "Do you have 3+ years of React?" are often configured as knockout questions. A wrong answer can move you to a rejected bucket automatically.
  • Search and ranking. Recruiters filter and search the pool by keywords, location, experience and other fields. Some systems also show a match score comparing your resume with the job description.
  • Human review. A recruiter opens a shortlist, skims resumes, and decides who gets a call.

Parsing: where good candidates get lost

Parsing is the step most people never think about, and it causes a surprising number of problems. The parser reads your file and guesses which text belongs to which field. When the layout is unusual, the guesses go wrong.

Common parsing failures:

A quick self-test: open your PDF, select all the text, and paste it into a plain text editor. If the order looks scrambled or pieces are missing, an ATS is likely to see the same mess.

  • Two-column layouts where the parser reads left to right across both columns, mixing your skills list into your job descriptions.
  • Contact details placed in the document header or footer, which some parsers skip entirely, leaving your profile without a phone number.
  • Job titles and dates inside text boxes or tables that come out as a jumble or are dropped.
  • Creative section names like "My Journey" instead of "Experience", so the system cannot tell where your work history begins.
  • Scanned or image-based PDFs that contain no selectable text at all.

Knockout questions are the real auto-reject

The closest thing to automatic rejection is not your resume formatting but the screening questions attached to the job. If a role requires candidates to be in Bengaluru or willing to relocate, and you answer "No", many systems filter you out before a recruiter looks. The same applies to minimum years of experience, notice period limits ("Can you join within 30 days?"), and mandatory certifications.

Answer screening questions honestly, but read them carefully. "Willing to relocate" and "currently in the city" are different questions. If your notice period is 60 days but negotiable or you can buy it out, look for a free-text field to say so instead of selecting a flat "No".

How recruiters actually search

When a recruiter has 400 applicants for a backend role, they rarely read all 400. They type something like "Java AND Spring Boot AND (Kafka OR RabbitMQ)" into the search, filter for 3–6 years of experience and a city, and start with that list. On Naukri's recruiter side (Resdex), the same thing happens across the entire database, not just people who applied.

This is why keywords matter. If your resume says "built event-driven services" but never mentions Kafka, you will not appear in that search even if you used Kafka every day. The fix is not stuffing; it is naming the actual tools, languages and methods you used, in the places where you used them.

Match scores: useful signal, not a verdict

Many newer systems calculate a percentage match between your resume and the job description. The calculation varies by vendor, but it usually weighs skills overlap, job title similarity, years of experience and sometimes education. Recruiters may sort by this score, which means a resume that uses the job's own vocabulary tends to float higher.

Do not obsess over hitting 100%. A score in the 70s with a clear, readable resume will usually do better with the human reviewer than a 95% that reads like a keyword list. The score gets you onto the shortlist; the human decides whether you get the call.

What this means for your resume

Practical rules that follow directly from how the software works:

  • Use a single-column layout with standard section headings: Summary, Experience, Skills, Projects, Education, Certifications.
  • Put your name, phone, email, city and LinkedIn URL in the body of the document, not in the header area.
  • Write job titles, company names and dates in a consistent format, for example "Software Engineer — Infosys — Jul 2022 to Present".
  • Mirror the exact terms from the job description where they are true for you: "Spring Boot", not just "Spring"; "Power BI", not "BI dashboards".
  • Spell out abbreviations once: "Continuous Integration/Continuous Deployment (CI/CD)".
  • Export to a text-based PDF from Word or Google Docs, or upload a .docx if the portal recommends it.
  • Keep your portal profile (Naukri, LinkedIn, Workday account) consistent with your resume, because recruiters often look at the profile fields first.

A short example

Here is the same experience written two ways. The first is common; the second is what both the parser and the recruiter can work with.

Before: "Worked on cloud stuff and made deployments faster for the team."

After: "Moved 14 microservices from manual deployments to a GitHub Actions CI/CD pipeline on AWS (ECS, ECR), cutting release time from half a day to under 30 minutes."

The second version contains the searchable terms (GitHub Actions, CI/CD, AWS, ECS), a concrete scope (14 services) and a result. Use numbers only when they are real and you can explain them in an interview.

Where tools can help

Tailoring keywords for every application is tedious, and that is the part most people skip. The Algnetic ATS resume builder parses your resume the way an ATS does, compares it against a specific job description, and shows which relevant skills are missing or buried, so you can fix the wording without rewriting from scratch. Whatever tool you use, keep the final say on what goes into your resume — it should only ever contain things you can talk about confidently in an interview.

Key takeaways

  • An ATS is a recruiter's database and search tool; automatic rejection mostly comes from screening questions, not formatting.
  • Parsing errors are real and avoidable: one column, standard headings, contact details in the body, text-based files.
  • Recruiters search by keywords, so name the specific tools and skills you have actually used.
  • Match scores help you get onto the shortlist, but a readable resume is what gets you the interview.

Let Algnetic apply to matching jobs for you · More career guides

Related guides

https://algnetic.com/blog/what-is-an-ats-and-how-does-it-work