ATS Resume Format for Indian Engineers: The Exact Template That Works in 2026
- Use a single-column, PDF format — two-column layouts break most Indian ATS parsers.
- The 5 must-have sections in order: Contact → Summary → Work Experience → Skills → Education.
- Quantify at least 3 bullet points per role — numbers are the single biggest ATS and recruiter signal.
- Mirror the exact keywords from the job description, especially the role title.
- Run your resume through an ATS checker before applying to each company type.
An estimated 90% of Indian companies with 50+ employees now use Applicant Tracking Systems to screen resumes before a human recruiter reads them. That means your resume needs to pass two tests: the ATS parser's structural scan, and a recruiter's 10-second skim. This guide covers both — with the exact format, section order, and keyword strategy that works for Naukri RMS, Greenhouse, Workday, Darwinbox, and Keka.
Step 1: Get the file format right first
Before you touch the content, get the container right. Indian ATS parse resumes in one of three ways: they read PDF text layers, extract from Word/DOCX, or use OCR on scanned images. Each has a different failure mode.
PDF (recommended)
Preserves formatting exactly. Readable by all major ATS used in India when the PDF is text-based (not scanned). Always submit as PDF unless the application portal explicitly asks for Word.
.DOCX (acceptable)
Accepted by Naukri and LinkedIn. Risk: fonts and formatting may reflow depending on the recruiter's Word version. Use only if the portal won't accept PDF.
Scanned PDF / Image-based PDF
Completely unreadable by ATS. If you scanned a printed resume, the ATS gets a blank document. Always use a text-layer PDF from Google Docs, Word, or LaTeX.
Step 2: The correct section order for Indian tech resumes
ATS systems parse resumes sequentially. Sections in the wrong order — or with non-standard headings — get misclassified. Here is the section order that works for Indian tech roles at every experience level, with the exact heading text ATS recognise:
Name + phone + email + LinkedIn + city. At the very top, never in the footer.
3–4 lines. Include your role title + YOE + top 2 skills. Use heading: 'Summary' or 'Professional Summary'.
Reverse chronological. Most recent role first. Use heading: 'Work Experience' or 'Experience'.
Dedicated section with 15–20 keywords grouped by category. Use heading: 'Skills' or 'Technical Skills'.
Degree, college, year, CGPA. Use heading: 'Education'.
Freshers and < 3 YOE only. 2–3 projects with tech stack and measurable outcome.
AWS, GCP, Google Analytics etc. Keep separate from Education.
Step 3: What to put in each section
Contact Information
Full name, phone, professional email, LinkedIn URL, city
✅ Do
- Use a plain email — gmail.com or outlook.com only
- Add your LinkedIn URL (linkedin.com/in/yourname) — many Indian ATS parse this
- Include city and state — recruiters filter by location
- Add GitHub URL if you're a developer (many Indian product companies check this)
❌ Don't
- Don't add a photo (triggers unconscious bias; most Indian ATS ignore it anyway)
- Don't use your college email — it signals you haven't updated your resume
- Don't add your full address — city and state is enough
- Don't use fancy icons or social media handles (Instagram, Twitter)
Professional Summary
3–4 line paragraph with your role title, years of experience, and top 2–3 skills
✅ Do
- Lead with your exact job title: 'Senior Software Engineer with 5 years of experience in backend development (Java, Spring Boot, AWS)'
- Include 2–3 of the most important keywords from your target job description
- State your current company type (startup, MNC, product company) — Indian recruiters use this as a signal
- Keep it to 3 lines maximum — ATS extract this but recruiters read it quickly
❌ Don't
- Don't use 'Objective' as the heading — it's outdated and ATS-unfriendly
- Don't use vague phrases like 'dynamic professional' or 'results-oriented'
- Don't make it longer than 4 lines — it competes with your experience section
Work Experience
Each role: job title, company, start–end dates (month + year), bullet points
✅ Do
- Use the exact job title from your offer letter — not a self-promoted version
- Format dates as: 'Jan 2022 – Present' or 'Mar 2020 – Dec 2022'
- Write 4–6 bullet points per role — start each with an action verb
- Quantify at least 3 bullets: 'Reduced API latency by 40%', 'Led a team of 6', 'Served 2M daily users'
- Include company name exactly as it appears on Glassdoor — ATS databases cross-reference company names
❌ Don't
- Don't use paragraph form for job descriptions — ATS parse bullets better
- Don't use year-only dates like '2021–2023' — month+year is required for ATS accuracy
- Don't list responsibilities only — 'Responsible for' is invisible to ATS keyword matching
- Don't use tables or columns inside your experience section — most ATS mangle multi-column layouts
Skills
A dedicated skills section with 15–20 technical and functional keywords
✅ Do
- Create a separate 'Skills' or 'Technical Skills' section — don't bury skills inside job bullets only
- Use exact tool names: 'React.js' not 'React'; 'PostgreSQL' not 'SQL databases'
- Group by category: Languages | Frameworks | Tools | Cloud | Databases
- Add soft skills that appear in target JDs: 'Cross-functional collaboration', 'Stakeholder management'
❌ Don't
- Don't rate your skills with dots or stars (1 out of 5) — ATS can't parse visual ratings
- Don't list 30+ skills indiscriminately — focus on the 15–20 most relevant to your target role
- Don't rely on skills scattered in experience bullets — you need a dedicated section
- Don't add outdated tech just to fill space: listing 'HTML' in 2026 as a senior dev looks odd
Education
Degree, college name, year of passing, CGPA/percentage
✅ Do
- List degree first, then college: 'B.Tech in Computer Science — VIT University, 2020'
- Add CGPA or percentage even if average — ATS checks for education completeness, not quality
- Include relevant coursework only if you're a fresher or have less than 2 years experience
- List certifications (AWS, GCP, Google Analytics) in Education or a separate Certifications section
❌ Don't
- Don't include your 10th and 12th scores once you have 3+ years of experience
- Don't add education details in a table — ATS parsing breaks on table-based layouts
Projects (Fresher / < 2 YOE)
2–3 projects with tech stack, what you built, and measurable impact
✅ Do
- Use the same format as work experience: project name, dates, 3–4 bullets
- Include the GitHub link or live URL if available
- Lead with the problem solved: 'Built a loan eligibility predictor using Python + scikit-learn — 87% accuracy on test set'
- List every major technology used — ATS score keywords from projects too
❌ Don't
- Don't include college assignments — only include self-initiated or internship projects
- Don't leave projects without outcomes — 'built a todo app' adds no signal
Step 4: Formatting rules that ATS care about
These rules apply regardless of which ATS the company uses. They prevent your resume from being structurally garbled before a recruiter ever reads it.
| Element | ✅ ATS-safe | ❌ Avoid |
|---|---|---|
| File format | PDF — always | Word (.docx) unless explicitly requested |
| Font | Arial, Calibri, or Times New Roman — 10–12pt body | Custom fonts, decorative typefaces — ATS may not render them |
| Length | 1 page for < 5 YOE · 2 pages for 5–12 YOE · 3 max for 12+ | 1 page at 8 YOE (too compressed) or 4+ pages (ATS truncates) |
| Columns | Single column throughout — especially for experience and skills | Two-column layout — Naukri RMS and most Indian ATS misread column 2 |
| Section headings | ALL CAPS or Bold: WORK EXPERIENCE, EDUCATION, SKILLS | Lowercase headings or icons as headings — ATS may skip unlabelled sections |
| Margins | 0.5 to 1 inch on all sides | 0.25 inch margins to squeeze content — parsing errors on narrow text |
| Tables inside resume | Avoid completely | Contact info in a table, skills in a grid — ATS parse tables unpredictably |
| Headers and footers | Avoid or keep blank | Contact info in the header — many ATS don't parse the header area |
| Bullet points | Simple • — > characters | Custom Unicode bullets, arrows, or emoji — garbled in ATS output |
| Colours and graphics | Black text on white background | Coloured section bars, icons, profile photos — invisible or garbled in plain-text ATS parse |
The two-column trap: Two-column resume layouts look polished in Canva or Figma, but Naukri's RMS, Greenhouse, and Darwinbox all parse left-to-right, row-by-row. In a two-column layout, your job titles end up next to your education, your skills get interleaved with your contact details — the recruiter sees a scrambled mess. Stick to single column.
Step 5: The keyword strategy that actually works
ATS keyword matching is the single biggest variable in whether you get shortlisted. Here's how to do it without gaming the system.
Mirror the job description
Copy the exact phrases from the JD. If it says 'REST APIs', don't write 'RESTful services'. ATS matching is literal in most Indian platforms.
Use both the acronym and the full term
Write 'Machine Learning (ML)' at first use. Some ATS search for 'ML', others for 'machine learning' — covering both doubles your match rate.
Include the role title you're applying for
If you're applying for 'Senior Data Engineer', that exact phrase should appear in your summary and at least once in your experience. ATS often rank exact title matches highest.
Don't keyword-stuff
Repeating 'Python Python Python' 10 times doesn't help. ATS detect keyword density abuse and modern systems penalise it. Aim for each key skill appearing 2–3 times naturally across the document.
Check Naukri's skill taxonomy
Before submitting to Naukri, search your top 5 skills in Naukri's skill search box. If Naukri suggests a different casing or variation (e.g. 'Node.js' vs 'NodeJS'), use Naukri's version on your uploaded resume.
ATS differences: Naukri vs Greenhouse vs Workday vs Darwinbox
Not all ATS are equal. Here's what you need to know about each platform commonly used by Indian tech companies:
Naukri RMS
Used by
Most large Indian companies, MNCs with India offices
Parser strength
Strong — reads PDFs well, handles most standard formats
Known issues
Strips formatting in multi-column resumes; struggles with tables; penalises resume freshness (re-upload every 3 months)
Pro tip
Upload as PDF. Use Naukri's own skills taxonomy for the Skills section.
Greenhouse
Used by
FAANG India offices, funded Indian startups (Razorpay, CRED, Zepto, Meesho)
Parser strength
Excellent — handles PDFs reliably, good keyword extraction
Known issues
Strict about date formats — use 'Month Year' consistently; non-standard section headings may be missed
Pro tip
Tailor your Summary and Skills section to exactly mirror the Greenhouse JD keywords.
Workday
Used by
MNCs (Microsoft, Google, Amazon, SAP, Oracle India)
Parser strength
Good but requires strict formatting — struggles with complex layouts
Known issues
Often requires you to manually re-enter fields after upload anyway; the PDF parse is a first-pass only
Pro tip
Always fill in every manual field in Workday even after uploading your resume — the parsed data is often incomplete.
Darwinbox / Keka
Used by
Mid-size Indian companies (100–2,000 employees), high-growth startups
Parser strength
Moderate — functional for standard formats but weaker keyword matching than Greenhouse
Known issues
Inconsistent handling of non-standard bullet characters; sometimes fails on font-heavy PDFs
Pro tip
Plain PDF, standard fonts, standard bullets. Don't rely on Darwinbox's parse — ask to email your resume directly to the recruiter if possible.
The 6 most common ATS resume mistakes Indian engineers make
Using a Canva or Zety template
Most visual resume builders create multi-column, font-heavy PDFs that break ATS parsers. Your qualifications end up jumbled or completely blank on the recruiter's screen.
Writing 'Responsible for X' instead of 'Built / Led / Reduced / Shipped X'
ATS score action verbs and quantified outcomes. Passive phrases like 'responsible for' match fewer keywords and signal weaker contributions to the recruiter.
Only one generic resume for all applications
A resume for a Senior SWE at a product company and a Senior SWE at a service company need different keyword emphasis. At minimum, tailor the Skills section and Summary for each company type.
Omitting the Skills section
Skills buried only inside job bullets are less reliably extracted. ATS systems score dedicated skills sections higher, and Naukri specifically uses the Skills section for recruiter search filters.
Using a photo or infographic
ATS ignores images entirely. Worse, image-heavy PDFs sometimes cause the ATS to skip entire pages. You're reducing parseable content for zero benefit.
Listing 'CTC: ₹12 LPA' or 'Notice period: 90 days' inside the resume body
These belong in your profile fields on Naukri/LinkedIn, not inside the resume document. ATS treat them as junk text. In a direct application, they give recruiters a reason to filter you out early.
Check your resume before you apply
Pathvio's free ATS Resume Checker scores your resume across all 7 categories in this guide — instantly, with specific fixes ranked by impact. No sign-up, no upload to our servers.
Check my ATS score free →Frequently asked questions
Related guides
- Your Naukri Resume Score, Explained — once your format is right, push your Naukri profile score above 80 to appear in more recruiter searches.
- Skill Gap Analysis for Your Tech Career in India — identify which skills to add to your resume next to move to the next salary band.
- Software Engineer Salary in India (2026) — benchmark your current salary against the market before your next application.
- Free ATS Resume Checker — scan your resume and get a score + prioritised fixes in under 60 seconds.