ATS Friendly Resume Format for India: Rules + Template

What an ATS actually does with your resume

When you upload a resume, the ATS extracts the text and tries to split it into structured fields: your name, phone, email, each job with its title, company and dates, your education and your skills. That structured record is what recruiters search, filter and sort. The original file is still attached, and a human usually opens it once you make the shortlist.

This means two things matter. First, the text must be extractable and in a sensible reading order. Second, the words recruiters search for must actually appear in your resume. A beautiful design that confuses the parser loses on the first point. A clean file that says 'worked on backend stuff' instead of naming Java, Spring Boot, MySQL and Kafka loses on the second.

• Contact details: name, phone with +91, email, city, LinkedIn URL
• Work history: job title, employer, location, start and end dates
• Education: degree, specialisation, college, year, CGPA or percentage
• Skills: tools, languages, platforms and domain terms, matched against the recruiter's search
• Free text: your summary and bullets, which recruiters read once you show up in results

PDF or Word: which file type to upload

A text-based PDF, exported from Word, Google Docs or a resume builder, is read correctly by most current systems and keeps your formatting identical on every screen. A .docx file is the most universally parsed format and is the safer choice when you are applying through an older corporate portal or a government-linked system.

The simple rule: follow the instruction on the job posting if there is one. If not, a text-based PDF is fine for most portals, and keep a .docx copy ready. The one format to avoid completely is a scanned PDF or a photo of your resume. To check, open your PDF and try selecting a sentence with your cursor. If you cannot select individual words, the ATS cannot read them either.

Name the file properly, for example 'Priya-Sharma-Data-Analyst-Resume.pdf'. Recruiters download dozens of files called 'Resume_final_v3.pdf' and a clear name helps a human find yours again.

Layout, fonts and formatting that parse cleanly

Most parsing problems come from layout choices that look good to humans but confuse software. You do not need a boring resume, but you do need a predictable one.

• Single column, top to bottom. Two-column templates and sidebars are the most common reason text is read out of order.
• No tables or text boxes for core content. Some parsers skip text inside them or merge cells into one long line.
• Contact details in the main body, not in the page header or footer, which some systems ignore.
• Standard fonts: Calibri, Arial, Helvetica, Georgia, Garamond or Times New Roman, 10 to 12 pt for body text.
• Simple round bullets or hyphens. Fancy symbols, arrows and emoji can come through as question marks.
• No skill bars, star ratings, pie charts or icons. A parser cannot read '4 out of 5 dots' and a recruiter cannot verify it.
• Consistent date format such as 'Jun 2022 to Present' or '06/2022 to Present', used the same way everywhere.
• Plain section headings like Experience, Education and Skills, not creative ones like 'My Journey' or 'What I Bring'.
• Margins of roughly 0.5 to 1 inch and enough white space that a human can skim it.

The section order that works for most Indian applications

For experienced professionals, use a reverse-chronological format: your most recent job first. Freshers can move Education and Projects above Experience, because those are their strongest sections. Whatever order you choose, use standard headings so the parser knows where each section starts.

Indian resumes often carry habits from older templates. A photo, date of birth, gender, marital status, father's name, languages known, hobbies and a signed declaration at the bottom are rarely needed for private-sector roles. Drop them unless the employer specifically asks, and use the space for skills and achievements instead.

• 1. Contact details (name, phone, email, city, LinkedIn, GitHub or portfolio if relevant)
• 2. Professional summary (two to four lines)
• 3. Skills (grouped: languages, frameworks, tools, domain)
• 4. Work experience (reverse chronological, three to six bullets per role)
• 5. Projects (essential for tech roles and freshers)
• 6. Education (degree, college, year, CGPA or percentage)
• 7. Certifications and achievements

A plain-text ATS resume template you can copy

Paste this into Google Docs or Word, replace the placeholders, and apply only simple formatting: bold headings, one font, normal bullets. Keep it to one page if you have under five years of experience, and two pages at most if you have more.

FULL NAME
City, State | +91 98XXX XXXXX | name@email.com | linkedin.com/in/yourname | github.com/yourname

PROFESSIONAL SUMMARY
[Job title] with [X] years of experience in [domain/stack]. Strong in [2 to 3 core skills]. Recently [one specific result with a number]. Looking for [target role] roles.

SKILLS
Languages: Java, Python, SQL
Frameworks: Spring Boot, React
Tools and Cloud: AWS (EC2, S3), Docker, Git, Jenkins
Domain: Payments, REST APIs, Microservices

WORK EXPERIENCE
Job Title | Company Name | City | Jun 2022 to Present
- Action verb + what you did + tool used + measurable result.
- Action verb + what you did + tool used + measurable result.
- Action verb + what you did + tool used + measurable result.

Job Title | Company Name | City | Jul 2020 to May 2022
- Action verb + what you did + tool used + measurable result.
- Action verb + what you did + tool used + measurable result.

PROJECTS
Project Name | Tech used | Link
- One line on the problem, one line on what you built and the result.

EDUCATION
B.Tech, Computer Science | College Name, City | 2020 | CGPA 8.1/10

CERTIFICATIONS
AWS Certified Cloud Practitioner | 2024

Common parsing mistakes and quick fixes

These are the problems we see most often when a resume reads well to the eye but badly to software. Each one has a simple fix.

• Only abbreviations: write 'Search Engine Optimisation (SEO)' or 'Continuous Integration (CI/CD)' once, so both search terms match.
• Different spellings from the job description: if the JD says 'Spring Boot', do not write 'SpringBoot'; if it says 'MS Excel', include 'Microsoft Excel' too.
• Skills hidden in images: a logo strip of tools looks neat but contains zero readable text.
• Links hidden behind words: write the full URL (linkedin.com/in/yourname) so it survives a plain-text export.
• Dates without months, or overlapping dates that make your timeline look confusing in the parsed profile.
• Job title and company on the same line with no separator, which can merge them into one field.
• Keyword stuffing in white text or a giant skills dump. Parsers may pick it up, but recruiters notice, and it damages trust.
• Long paragraphs instead of bullets, which are hard to skim even if they parse correctly.

How to test your resume before you apply

The quickest test costs nothing: open your resume, select all, copy, and paste it into Notepad or any plain-text editor. If the text appears in a sensible order with headings, dates and bullets intact, a parser will most likely read it the same way. If your skills sidebar appears halfway through a job description, fix the layout.

The second test is to upload the file to a job portal that auto-fills a profile and check what it extracted. Wrong job titles, missing dates or an empty skills list tell you exactly what to fix.

Finally, compare your resume against the actual job description. HireToolX's ATS Scorer checks how well your resume matches a specific JD and flags missing keywords and formatting issues, so you can fix gaps before a recruiter ever sees the file.