Resume ATS Optimisation Guide for Indian Job Seekers 2026

Applicant Tracking Systems parse your resume into structured data: your name, email, education, skills, companies, job titles, and dates: and score it against the job description. High-scoring resumes are surfaced to recruiters; low-scoring ones are filtered out. ATS systems used by Indian companies include Workday (Amazon, Microsoft India), Greenhouse (many startups), Taleo (TCS, Accenture), SmartRecruiters (several MNCs), and iCIMS (Infosys). Most of these share the same parsing limitations: they struggle with columns, tables, headers/footers, text boxes, and graphics. A beautifully formatted two-column resume that looks great in PDF will often parse as garbled text in the ATS: rendering you invisible regardless of your qualifications.

Format your resume as a single-column document in a standard font (Arial, Calibri, Times New Roman, or Cambria: all parse reliably). Use standard section headers ('Education', 'Work Experience', 'Projects', 'Skills'): creative headers like 'My Journey' or 'Where I Have Been' are not parsed correctly. No tables, no columns, no text boxes, no graphics, no icons. No header or footer content (some ATS cannot parse these). File format: PDF if the application accepts it; .docx if the form requires Word (some older enterprise ATS parse .docx more reliably than PDF). Bullet points are fine: use standard •, -, or the ATS-safe versions, not custom shapes. Dates: spell out months (January 2024, not 01/24) for maximum compatibility.

The most important ATS factor: keyword matching between your resume and the job description. How to do this: copy the job description into a free word cloud tool: the largest words are the most frequently used terms and highest-weight ATS keywords. For a 'Senior Java Backend Engineer' role, the keywords might be: Java, Spring Boot, microservices, REST API, AWS, Kubernetes, SQL, distributed systems. Your resume must contain these terms: exactly as written, not synonyms. If the JD says 'microservices architecture', your resume should say 'microservices architecture', not 'distributed application design'. The trick: add a 'Skills' section at the bottom that lists all relevant technologies and frameworks from the JD that you legitimately have experience with. ATS scores this section heavily.

Every bullet point in your experience section should start with a strong action verb and quantify the result where possible. Weak: 'Responsible for working on the backend system.' Strong: 'Designed and implemented a payment retry microservice in Spring Boot that reduced failed transaction rate by 23%.' The formula: [action verb] + [what you did] + [using which technology/method] + [resulting in what measurable outcome]. Strong action verbs for engineering roles: Designed, Implemented, Architected, Reduced, Improved, Automated, Optimised, Built, Deployed, Migrated, Led, Refactored, Integrated. For quantification: think in terms of percentage improvement, scale (users served, requests per second, data volume), time saved, cost reduced, or business metric impacted. Even approximate numbers ('~30% reduction', 'serving 500K daily active users') are far better than no numbers.

Optimal structure for Indian engineering resumes: (1) Header: name, email, phone, LinkedIn URL, GitHub URL: on one or two lines. No photo (not required, sometimes a bias risk). No date of birth, no Aadhaar number, no marital status. (2) Summary (optional for experienced candidates): 2–3 lines describing your experience, primary technologies, and career focus. For freshers, a skills section is more valuable than a summary. (3) Experience: most recent first. For each role: company name, job title, dates (month and year), and 3–5 bullet points using the action-verb-result formula. (4) Education: degree, college, CGPA if above 7.5, relevant coursework. For freshers, education should come after projects. (5) Projects (critical for freshers): project name, 2–3 bullets with tech stack and outcome, link to GitHub or deployed URL. (6) Skills: programming languages, frameworks, databases, cloud platforms, tools: all explicitly listed.

Mistake 1: Using a template from Canva or Novoresume. These produce graphically rich resumes that ATS cannot parse. Use a simple Word or Google Docs template instead. Mistake 2: Using a 'Objective Statement' that says nothing. 'Seeking a challenging and rewarding position in a reputed organisation' is meaningless to any recruiter. Replace with a specific 2-line summary or remove entirely. Mistake 3: Listing technologies without context. 'Skills: Java, Python, AWS, React, SQL, MongoDB, Docker, Kubernetes, Terraform' with no context about depth or actual use. Move to a structured skills section and ensure each technology appears in your experience bullets with actual context. Mistake 4: Including Class 10 and Class 12 marks. Unless applying for a campus-entry service IT role, education detail should be college degree only. Mistake 5: Exceeding 2 pages for less than 8 years of experience. 1 page for 0–3 years, 2 pages for 4–10 years.