The short version. Before a recruiter reads your CV, software reads it. That software turns your document into plain text and tries to work out where your name, employers, dates and skills are. Two-column layouts, tables, text boxes, headers, footers and graphics routinely defeat it. When parsing fails, your application is not rejected on merit — it is scored as incomplete, and nobody ever finds out what you can do.
Almost every rejection story contains the same sentence: “I applied to forty companies and heard nothing from any of them.” Forty silences in a row is not forty independent judgements about your ability. It is a systematic failure, and in a large number of cases the failure is mechanical.
This is what applicant tracking systems actually do, which design choices break them, and how to check your own file today without paying anyone.
What an ATS is, and what it is not
An applicant tracking system is a database with a parser attached. It exists because a mid-sized company advertising one role can receive several hundred applications and needs them in a searchable, comparable form.
When you upload a CV, three things happen in sequence:
- Extraction. The file is converted to plain text. Everything visual — columns, colours, boxes, icons — is discarded. What remains is a single stream of characters in whatever order the extractor produced.
- Parsing. The system tries to map that text stream onto structured fields: name, email, phone, current employer, job titles, dates, education, skills. It does this with pattern rules and section headings.
- Retrieval. A recruiter searches or filters. Candidates whose parsed record matches the query surface first.
An important correction to a widespread myth. Mainstream applicant tracking systems do not assign a secret 0–100 “ATS score” and auto-reject below a cutoff. Most do not reject anyone automatically at all. What they do is rank and filter, and a CV that parsed badly simply never appears in the results a recruiter looks at. The outcome feels identical from your side, but the cause matters — because a parsing problem is completely fixable and a “score” is not something you can game.
The seven things that break parsing
1. Two columns
This is the single biggest cause of damage, and it is the format most modern templates use. A text extractor reads a page in a linear order. Faced with two columns it may read straight across both, producing lines like “Senior Analyst Python, SQL, Excel” where the job title from the left column has fused with skills from the right. Every subsequent field lands in the wrong place.
Do instead: one column, full width, top to bottom.
2. Contact details in the header or footer
Many extractors ignore header and footer regions entirely, because in most documents they contain page numbers and boilerplate. Put your phone number and email there and the system may register a candidate with no way to contact them.
Do instead: name and contact details as ordinary text in the body, at the very top.
3. Tables used for layout
A table holding your employment history looks tidy and parses unpredictably. Cell contents can be emitted column-by-column rather than row-by-row, scrambling which date belongs to which employer.
Do instead: plain paragraphs and simple bullet lists. If a table is genuinely the right structure — a skills matrix, say — accept that it may be read as a flat list and make sure each cell still reads sensibly alone.
4. Text boxes and shapes
Text inside a drawing object is not body text. Some extractors take it, some drop it silently. If your entire profile summary sits in a coloured box, it may simply not exist as far as the system is concerned.
5. Text rendered as an image
A designed CV exported as a picture, a scanned printout, or a photograph of a printed copy contains no machine-readable text at all. Some systems run OCR; many do not. This is also why any competent CV writer will refuse to work from a scan — text read from an image carries errors that are hard to spot and expensive to find later.
6. Non-standard section headings
Parsers look for conventional headings. “Professional Experience”, “Work Experience” and “Employment History” are all recognised. “My Journey”, “Where I’ve Been” and “Career Canvas” are creative and cost you the section.
7. Icons standing in for labels
A small envelope glyph before your email address means nothing to a parser. Neither does a pin before your city. Keep the words.
The format that survives
| Element | Safe | Risky |
|---|---|---|
| Layout | Single column, full width | Two or three columns, sidebars |
| File type | .docx, or a PDF exported from text | Scanned PDF, .jpg, .png, .pages |
| Contact details | Body text at the top | Header, footer, sidebar, image |
| Fonts | Calibri, Arial, Garamond, Georgia | Decorative or downloaded display fonts |
| Dates | MM/YYYY or Mon YYYY, consistently | Mixed formats, seasons, “present” in one place and “current” in another |
| Bullets | Standard round or square bullets | Emoji, arrows, custom glyphs |
| Headings | Experience, Education, Skills | Invented section names |
| Graphics | None | Skill bars, rating stars, charts, photo |
On PDF versus Word
Both are fine if the PDF was exported from a text document rather than scanned. Modern systems handle text-based PDFs well. Where the posting explicitly asks for one format, give it that one — ignoring a stated instruction is its own kind of rejection. If nothing is specified, .docx is the marginally safer choice because every parser handles it and because a recruiter can annotate it.
On photographs
Indian CV convention has historically included a photo. For roles at multinationals and for most technology employers, leave it out: it adds parsing risk, it adds nothing a recruiter needs at screening stage, and in several jurisdictions it creates a compliance problem the employer would rather avoid. Where a photo is genuinely expected — some government and public-sector formats, some hospitality roles — follow the convention.
Keywords: match honestly, do not stuff
Recruiters search the parsed database. If the posting says account management and your CV says client servicing throughout, a search for the former will not surface you — even though you have done exactly that job for six years.
The fix is not to invent skills. It is to use the industry's current vocabulary for work you have genuinely done.
| Often written as | Often searched as |
|---|---|
| Client servicing | Account management |
| MIS reporting | Business reporting, data analysis |
| Manpower handling | Team leadership, people management |
| Vendor coordination | Vendor management, procurement |
| Costing | Cost analysis, financial planning |
| Software testing | Quality assurance, QA automation |
Take the two or three postings you actually want. Note the nouns that repeat. Where one of those nouns describes something you have really done, use their word rather than yours. Where it describes something you have not done, leave it out — the interview will find you out, and a fraudulent match is worse than no match.
Do not put white text on a white background. The advice to hide a block of keywords in invisible text circulates every year. Parsers read the text layer, not the rendered colour, so it works mechanically — right up to the moment a human opens the file, selects all, and sees it. It is treated as deception, and it ends candidacies. It is also completely unnecessary, because honest keyword alignment achieves the same retrieval.
Parsing is necessary but not sufficient
A perfectly parsed CV that says nothing still fails. Once you are in front of a human being, seven seconds decides whether they read on, and the content problem is different from the format problem.
Duties versus results
“Responsible for handling client accounts.” This tells a manager what your job description said. Every applicant has one.
“Managed 40 accounts worth ₹2.3 crore; cut churn from 18% to 11% in eighteen months.” Same job. Completely different candidate.
Numbers
If nothing on your CV can be counted, nothing on it can be verified, and an unverifiable claim is discounted. Almost every role has figures in it — team size, budget, transaction volume, turnaround time, error rate, revenue influenced. Most people simply never wrote them down. Spend twenty minutes recovering them; it is the highest-return work you will do on the document.
Space follows relevance, not chronology
A 2014 internship with a full paragraph and a current role with one line is the most common structural error in mid-career CVs. Give the most room to the most recent and most relevant work, and compress everything older into a line each.
The summary
“Hardworking professional seeking a challenging role in a reputed organisation.” Every rejected CV in the pile says this. Three specific sentences about what you have actually built, managed or fixed will outperform it every single time.
Test your own file in ten minutes
You do not need a paid scanning service. Two checks catch most problems.
The copy-paste test
- Open your CV.
- Select everything and copy it.
- Paste into a completely plain text editor — Notepad on Windows, TextEdit in plain-text mode on a Mac.
What you see is approximately what the parser sees. Read it. Is your name at the top? Is your email present? Do job titles sit next to the right employers and dates? Are there fused lines where two columns have run together? If the plain text is coherent, you have cleared the biggest hurdle. If it is scrambled, the layout is the problem — not your experience.
The search test
Take a job posting you want. List the eight most important terms in it. Search your CV for each. A reasonable target is that most of the terms you can honestly claim appear at least once, in context, in a real sentence about real work.
A structure that works
- Name — largest text on the page, plain body text.
- Contact line — phone, email, city, LinkedIn URL. One line, body text.
- Summary — three or four lines. What you do, at what scale, with what result.
- Skills — a plain comma-separated list. Tools and methods you would be comfortable being questioned on.
- Experience — reverse chronological. Company, title, location, dates on one line; three to five achievement bullets beneath, each with a number wherever a number exists.
- Education — degree, institution, year. One line each.
- Optional — certifications, publications, languages. Only if they are relevant to the role.
One page for under five years of experience. Two pages beyond that. Three pages only for genuinely senior or academic profiles.
The bottom line
Most CVs that get no response are not weak. They are unreadable to the first system that touches them, and their owners spend months concluding they are not good enough.
Run the copy-paste test today. If the plain text comes out scrambled, you have found the problem, and it is a formatting problem — which is to say, an afternoon of work rather than a career crisis.
If you want a second pair of eyes. Send your CV and I will rewrite the top third — headline, summary and most recent role — free, and send it back the same day. No card, nothing to cancel, no follow-up if you go quiet. You keep it either way. Details here. Word file, Google Doc link or a text-based PDF please, not a scan.
Frequently asked questions
Do applicant tracking systems automatically reject resumes?
Most do not. They parse your CV into structured fields and let recruiters search and filter. A badly parsed CV is not formally rejected — it simply never appears in the results a recruiter looks at, which produces the same silence from your side.
Is PDF or Word better for an ATS?
Both work if the PDF was exported from a text document rather than scanned. If the posting names a format, use that one. If nothing is specified, .docx is marginally safer because every parser handles it and recruiters can annotate it.
Should an Indian resume include a photograph?
For multinationals and most technology employers, leave it out. It adds parsing risk, adds nothing at screening stage, and creates compliance issues in several jurisdictions. Include it only where the format genuinely expects it, such as some public-sector and hospitality applications.
How do I know if my resume is ATS-friendly?
Copy the entire document and paste it into a plain text editor such as Notepad. What you see is roughly what a parser sees. If your name, email, job titles and dates all appear in a sensible order with no fused lines, the format is safe. If it is scrambled, the layout is the problem.
Does keyword stuffing work?
No, and hiding keywords in white text is worse than useless — it works on the parser and ends your candidacy the moment a human selects the text. Honest alignment with the posting's vocabulary achieves the same retrieval without the risk.
How long should my resume be?
One page under five years of experience, two pages beyond that. Three pages only for genuinely senior or academic profiles. Length is not the issue; space allocated to irrelevant history is.
Why do two-column resume templates cause problems?
Text extractors read a page linearly. With two columns they may read straight across both, fusing a job title from the left with skills from the right. Every field after that lands in the wrong place, and the parsed record becomes incoherent.
Will fixing the format alone get me interviews?
It removes the mechanical failure. Content still decides the outcome: duties rewritten as achievements, real numbers wherever they exist, and space allocated to recent and relevant work rather than chronology.
Get the FutureProof brief — free, once a week
One email every Sunday: the AI tools worth paying for, the income ideas that actually worked, and the India-specific money moves for the week. No spam, unsubscribe in one click.
Want an article like this for your own site?
I research and write SEO-ready, fact-checked articles for founders, agencies and finance/AI brands. From ₹2,000 per 1,000 words, unlimited revisions, 3-day delivery, 100% money-back guarantee. Newsletter subscribers get 30% off with code FPSUB30.
See packages & prices →Tools I use →