QA & Software Testing

How to make an ATS-friendly resume in India (2026)

The Indian resume carries a lot of baggage an ATS can't read — a photo, your date of birth, a 'Declaration'. Here's how applicant tracking systems actually work, and the India-specific things to keep, cut, and fix.

Updated 24 June 2026

Most advice on this topic exists to sell you a template or a "resume score" tool, and most of it leans on a scary, made-up statistic. This guide does neither. Once you understand what an applicant tracking system actually does — and what the traditional Indian resume gets wrong about it — the fixes become obvious, and you can make them in an evening without paying anyone.

First, the myth: you've probably read that "an ATS auto-rejects 75% of resumes before a human sees them." That figure is not real and has been widely debunked. What's true and better-sourced is subtler — applicant tracking systems can quietly filter out qualified people through rigid criteria and bad parsing (Harvard Business School's "Hidden Workers" research documents this). The goal isn't to beat a robot; it's to not get lost in one.

What an ATS actually does (and doesn't)

An ATS is software almost every mid-to-large company — and every job portal — uses to collect, parse, store, and search applications. When you apply, your resume is read into structured fields (name, skills, companies, dates) so a recruiter can search and sort hundreds of applicants. Two things follow from that, and they're the whole game:

  • It parses you into fields. Confusing formatting lands your information in the wrong field or drops it entirely — so a strong candidate becomes an empty or scrambled record.
  • It lets recruiters search by keyword. If the terms a recruiter searches for aren't on your resume in plain language, you simply don't show up — no matter how qualified you are.

So "ATS-friendly" means two practical things: format so you parse cleanly, and use the real keywords so you're findable. That's it. There is no secret score to game.

The India-specific baggage to cut

This is where Indian resumes differ from generic advice. The traditional format taught in many colleges and on older portals is full of things that confuse a parser, waste space, or actively work against you — habits worth dropping in 2026:

  • The photo. Common on Indian resumes, but it's invisible to the ATS, eats space, and invites bias. Unless a role explicitly asks for one, leave it off.
  • Date of birth, marital status, gender, religion, nationality, father's name. None of this belongs on a professional resume — it's not parsed usefully and it's an artifact of an older era. Cut it.
  • Full home address. A city (and "open to relocation" if true) is plenty; a full postal address is unnecessary and dated.
  • The "Declaration" line and signature. "I hereby declare that the above information is true…" adds nothing. Remove it.
  • Current/expected CTC. Don't put your salary on the resume. It anchors you before you've shown your value — handle it in the conversation instead (see salary negotiation in India).
  • Fancy Canva/template designs. The two-column, icon-heavy, photo-and-skill-bar templates that look great on screen are the single biggest parse-breaker. They scramble in most ATS.

The format that survives (and reads better anyway)

The good news: the format that parses best also reads best to a human, so there's no trade-off. The same single-column, plain principles apply to every role — this is the role-agnostic version of the ATS-ready format for QA engineers, and it's exactly why CareerIntel ships the resume deliverable ATS-plain, with no visual design applied to it.

  • Single column. Multi-column layouts are the number-one parse-breaker — the reader runs across both columns and scrambles the content.
  • Standard section headings — Summary, Skills, Experience, Projects, Education. Don't invent "My Journey" or "What I Bring."
  • No tables, text-boxes, or columns for layout, and no graphics/icons/skill-bars — content inside them is routinely mangled or skipped, and a chart of "Java: 90%" means nothing to a machine or a recruiter.
  • Nothing important in the header or footer — some parsers ignore them, so keep phone and email in the body.
  • Standard, readable fonts (Arial, Calibri, Times) and a reverse-chronological order.
  • File type: a .docx is the safest universal choice; a text-based (not image-exported) PDF is usually fine. Always follow any format the posting specifies.
  • Length: 1–2 pages for most people. The Indian habit of a 4–5 page CV that lists every project in full dilutes the strong parts.

Keywords: mirror the job, honestly

Recruiters search by skill, so the genuinely relevant terms for your target role need to be present in your own words, where you actually have the skill. Read the job description and make sure its real requirements are reflected — same language, no invention.

The rule is mirror the job description honestly — never keyword-stuff. Listing skills you can't defend fails the moment a human is involved, and a hidden block of white-text keywords is detected and reads as dishonest. Honest findability beats clever gaming every time — it's the same anti-fabrication principle the whole CareerIntel package is built on.

Lead with outcomes, not duties

Parsing cleanly only gets you read; what you actually wrote decides the rest. The most common failure across every role is a resume of responsibilities instead of results.

Before: "Responsible for handling client requirements and coordination." After: "Owned requirements for 3 enterprise clients; cut requirement-clarification rework ~30% by introducing a structured sign-off checklist." The rewrite is specific, quantified, keyword-rich, and plain text any parser reads perfectly. The deeper content fixes — the ones that apply whatever your function — are in the resume mistakes that hide your value.

A portal profile is an ATS too

On Naukri, LinkedIn, and most company career portals, the profile you fill in is structured ATS data — recruiters search it the same way. So the same discipline applies: complete the fields, use real keywords in your headline and skills, keep it current, and don't rely on an attached PDF to carry information your profile fields are missing. For where these portals fit in a wider search, see running a job search as a system.

Test your own resume for free (no paid tool)

  1. 01The copy-paste test. Select all, copy, paste into a plain text editor. If the result is readable and in sensible order, a parser will likely handle it. Scrambled or missing chunks mean your formatting is the problem — usually columns, tables, or a template.
  2. 02Read it as plain text. Are your headings, dates, and skills all intact and in order with no formatting?
  3. 03The keyword check. Put your resume and a target job description side by side. Are the role's real, relevant skills present, in matching language — without anything you can't defend?

If those three pass, you're already ahead of most applicants — no subscription required.

Where CareerIntel fits (honestly)

Making your resume ATS-ready yourself is genuinely doable with the checks above. But if you'd rather not DIY it, the ATS-plain resume is one of the three deliverables CareerIntel produces — rewritten around your real, verified achievements and tailored to your target roles, by a human, in 4 business days.

Get a recruiter-ready, ATS-plain resume

An ATS-ready resume rewritten around your real achievements, plus scored target roles and verified company research — delivered in 4 business days, every claim checked against its source.

See a real sample

FAQ

Is it true that an ATS auto-rejects most resumes before a human sees them?
No — the popular "75% are auto-rejected" figure is not real and has been widely debunked. Most systems don't silently reject you with a secret score; a recruiter still looks. What's true is subtler: rigid filters and bad parsing can cause qualified candidates to be missed. So the goal is to parse cleanly and be findable by keyword, not to beat a robot.
Should I put a photo on my resume in India?
Generally no. A photo is invisible to the ATS, takes up space, and can invite bias. Unless a specific role explicitly requests one, leave it off — along with date of birth, marital status, gender, and the old "Declaration" line. These are artifacts of an older format that add no value in 2026.
Should I mention my current or expected CTC on my resume?
No. Putting your salary on the resume anchors you before you've shown your value and is better handled in the conversation. Keep the resume about your skills and achievements, and deal with compensation separately when it comes up.
PDF or Word for an ATS in India?
A .docx is the safest universal choice for parsing. A text-based (not image-exported) PDF is usually fine too. Avoid exporting your resume as an image, and always follow any specific format a job posting requests.
Do those nice two-column resume templates work with an ATS?
Often poorly. The two-column, icon-heavy, photo-and-skill-bar templates from design tools look good on screen but are the single most common cause of scrambled parsing. A clean single-column layout parses reliably and reads just as well to a human.

Keep reading

Sources

  1. Harvard Business School — "Hidden Workers: Untapped Talent" (how ATS criteria filter out qualified candidates) (accessed 2026-06-24)
  2. Jobscan — How applicant tracking systems work (accessed 2026-06-24)