How to make an ATS-friendly résumé (India, with examples)

An applicant tracking system (ATS) is the software a company or job portal uses to collect applications, store résumés and let recruiters search and shortlist them. It does three things that affect you.

1. 1

   Parses the file

   It extracts text from your PDF or Word file and tries to sort it into fields: name, phone, email, job titles, employers, dates, degree, skills. If the layout confuses the parser, information lands in the wrong field or goes missing.

2. 2

   Matches keywords

   Many systems compare the words on your résumé with the job's requirements and show the recruiter a match score or ranking. Exact terms matter: “React.js” and “ReactJS” may or may not be treated as the same, depending on the system.

3. 3

   Lets recruiters search

   Recruiters filter and search the candidate database — for example, “Java AND Spring Boot”, location “Pune”, experience 2–4 years. If a skill is not written on your résumé in words, you will not appear in that search.

An ATS rarely “rejects” a résumé on its own the way people fear. The real risk is quieter: a badly parsed résumé shows up with blank fields, and a résumé without the right words never comes up in a recruiter's search.

A plain, single-column, text-based résumé with standard section headings is the safest ATS format. Design can still look professional — it just has to be built from real text, not graphics.

Quick test: open your PDF, select all the text (Ctrl+A), copy it and paste it into Notepad. If the text comes out in a sensible order with nothing missing, most parsers will read it too. If sections are jumbled or your skills disappear, the layout is the problem.

Take the words from the job description's requirements, check which ones genuinely apply to you, and write them in the same form in your summary, experience bullets and skills section. Here is a worked example.

Data Analyst — Bengaluru — 1–3 years
Requirements: Strong SQL and Excel (pivot tables, VLOOKUP). Experience building dashboards in Power BI or Tableau. Python (pandas) is a plus. Ability to present insights to business stakeholders. Experience with A/B testing preferred.

• Use the job title from the posting in your summary line if it honestly describes you (“Data Analyst with 2 years…”).
• Write both forms of acronyms once: “Search Engine Optimisation (SEO)”, “Applicant Tracking System (ATS)”.
• Put skills in context. A bullet that shows you used SQL counts for more with a recruiter than a word in a list.
• Do not stuff. Repeating a keyword ten times or hiding it in white text does not help with a human reader and can get you flagged.

For a deeper walk-through of tailoring every section, see how to customise your résumé for a job description.

Indian employers use a mix of global and local systems — commonly used systems include Workday, Taleo, SuccessFactors and Naukri RMS, along with many smaller tools and in-house portals. You usually cannot tell which one a company uses, and you do not need to.

The rules on this page work across all of them, because they all have the same basic job: turn your file into text, then let a recruiter search and filter it. A clean single-column résumé with the right keywords is readable everywhere. If you mainly apply through Naukri, read our Naukri ATS guide for how recruiters search the portal's database.

An ATS-friendly résumé looks plain at the top and specific in the body: contact details as text, a two-line summary with the target job title, then experience bullets that start with a verb and name the tools used.

• Single-column layout; nothing important in a sidebar, table, text box or image.
• Name, phone, email, city and LinkedIn as plain text at the top (not in the header/footer).
• Standard headings: Summary, Experience, Projects, Education, Skills, Certifications.
• Target job title from the JD appears in your summary.
• Must-have skills from the JD appear in Skills and inside at least one bullet — only if true.
• Bullets start with action verbs and include numbers where you have them.
• Consistent dates (Month Year – Month Year).
• Text-based PDF, under a few MB, with a clear file name such as Rohan_Mehta_Java_Developer.pdf.
• Copy-paste test passes: text comes out in the right order.
• Checked against the job description with an ATS score checker.