ATS Resume Format: What to Use and What to Avoid

An ATS resume format means a single-column layout with standard section headers (Work Experience, Education, Skills, Projects), plain fonts, and no tables, text boxes, columns, headers/footers, icons, or graphics — because systems like Workday and Oracle Taleo parse resumes into structured fields, and anything visually "designed" confuses that extraction. Save it as a .docx unless the application explicitly asks for a PDF; most Indian job portals and modern company career pages handle PDFs fine, but some older Taleo instances still parse .docx more reliably. Use expected, standard headings — the parser is matching your section titles against a known template, so "Relevant Experience" instead of "Work Experience" can leave a field empty. Below is the exact structure that consistently survives parsing across Naukri applications, Workday, and Taleo, plus a table of what to avoid and why.

Why This Confuses So Many Job Seekers in India

A lot of ATS resume format advice circulating online is written for the US market and doesn't map cleanly onto how Indian hiring actually works. Naukri, for instance, doesn't reformat or "grade" your uploaded resume the way some checker tools imply — it stores the file and lets recruiters search a separate database of parsed profile fields (RESDEX). Company career pages built on Workday or Taleo, on the other hand, do run a real-time parse the moment you upload during an application. That means the same resume can behave differently depending on where you're submitting it, which is exactly why a format that's boring, plain, and predictable is safer everywhere rather than optimal in one place and risky in another.

The Structure That Survives Every Parser

Every major ATS expects roughly the same skeleton, in roughly the same order, because that's the order most resume templates in their training and testing data used. Deviating from it doesn't get you disqualified, but it increases the odds that a field parses incorrectly.

Section order for a fresher resume (0-1 years)

• Name and contact details (plain text, in the body, not a header)
• Professional summary (2-3 lines, includes your target job title)
• Education (degree, institution, CGPA/percentage, graduation year)
• Skills (grouped: technical skills, tools, languages)
• Projects (name, one-line description, tools used, outcome)
• Internships (if any), in the same format as work experience
• Certifications

Section order for 1-2 years of experience

• Name and contact details
• Professional summary
• Work Experience (most recent first, with company, title, dates, bullet points)
• Skills
• Education
• Projects and certifications (combined if space is tight)

Formatting Elements That Break Parsing

Element	ATS-safe?	Why
Single column, top-to-bottom flow	Yes	Matches how parsers read text order by default
Two-column or sidebar layout	No	Parsers can read across columns and merge unrelated lines, especially in Taleo
Tables for skills, dates, or contact info	No	Table cell order isn't guaranteed to extract in the order you see it
Text boxes or embedded shapes	No	Text inside a floating object is frequently invisible to the text extractor
Icons for phone, email, LinkedIn	No	Icons carry no text; the label next to them may also get orphaned
Header/footer for name or contact info	Risky	A number of parsers skip headers and footers entirely by default
Bullet points (plain round or square)	Yes	Standard bullet characters are read as list items without issue
Standard fonts (Calibri, Arial, Georgia, Times New Roman)	Yes	No font-substitution or rendering issues on parsing servers
Decorative or script fonts	No	Some characters can be misread or dropped during text extraction

Fonts, File Types, and Margins

Stick to 10.5-12pt for body text and 14-16pt for your name, in one of the standard fonts listed above. Margins of 0.5-1 inch on all sides are safe and also keep a fresher resume to a single page, which is still the practical norm for 0-2 years of experience. Save as .docx by default; if a portal specifically requests PDF, export directly from Word rather than "printing to PDF" from a scanned copy, since a scanned or image-based PDF has no selectable text for a parser to extract at all. Avoid saving as .pages, .odt, or any format outside .docx and .pdf — older parsers, including some Taleo deployments, may not support them.

Naukri, LinkedIn, and company portal upload quirks

Naukri accepts both .docx and PDF for the resume you attach to your profile, but many recruiters searching RESDEX are working from your parsed profile fields rather than opening the attached file at all — which is exactly why keeping your Naukri profile's own skills and headline fields updated matters as much as the uploaded document. LinkedIn's "Easy Apply" typically forwards your uploaded file straight through to the employer's own ATS, so the same formatting rules apply there too. When a company's careers page explicitly says "upload your resume (PDF preferred)," follow that instruction over any general advice, since it usually means their specific ATS instance has been configured to handle PDFs reliably.

What Happens When Formatting Actually Breaks

It helps to know what a parsing failure looks like in practice, because it's rarely a rejection email. More often, a recruiter filtering candidates by "3+ years experience" or "B.Tech" simply never sees your profile in that filtered list, because your dates or degree sat inside a text box, a table cell, or a header that the parser skipped. Your total years of experience might get miscalculated if your employment dates are formatted unusually (like "Jun'22 - Present" instead of "June 2022 - Present"), which can push you out of an experience-range filter entirely. None of this shows up as visible feedback — you simply stop getting responses from a channel that should otherwise have worked, which is why testing your own resume (copy-pasting it into a blank document to see if the text comes out in a sensible order) is worth doing before every off-campus application round, not just once.

This matters at scale: TCS's NQT drive alone sorts freshers into Ninja (roughly ₹3.36-3.6 LPA), Digital (roughly ₹7-7.5 LPA), and Prime (roughly ₹9-9.5 LPA) tracks based on test performance, and each track still funnels thousands of resumes through a structured hiring system before a human reviews anything. A resume that fails to parse cleanly at that volume doesn't get a second look — there's no time for one.

Headings the Parser Actually Recognizes

Stick to the standard label even if a more creative one feels more "you." Parsers are pattern-matching against a known list of expected headings, not reading for meaning.

• Use "Work Experience" or "Professional Experience," not "My Journey" or "Where I've Worked"
• Use "Education," not "Academic Background" or "Learning"
• Use "Skills" or "Technical Skills," not "What I Bring" or "Toolkit"
• Use "Certifications," not "Credentials" or "Badges"

This directly supports keyword matching too — see our guide to resume keywords for how to fill these sections once the headings themselves are parser-friendly.

Settling the PDF vs Word Debate for Good

This comes up in almost every campus placement WhatsApp group, and the honest answer is: it depends on where you're submitting, so default to .docx and only switch when told otherwise. Naukri accepts either format for your uploaded resume. Most modern Workday instances parse PDFs and Word documents about equally well, since Workday has invested heavily in its parsing engine in recent years. Older Taleo deployments, still used by some large legacy employers in India, have historically been more consistent with .docx than with PDF, particularly for resumes built in design tools rather than Word itself. If an application form gives you a choice and doesn't specify, .docx remains the safer default precisely because it's the one format every version of every major parser has been built to handle from the start.

A Sample ATS-Safe Layout for Indian Freshers

Picture a single-column page in this order: your name and phone/email/LinkedIn URL as plain text at the top; a 2-3 line summary naming your target role and top 3 skills; an Education section with your degree, college, CGPA, and year; a Skills section split into "Technical Skills" and "Tools" as simple comma-separated lists, not a table or graphic skill-bar; a Projects section with 2-4 projects, each with one line on what it does and the tools used; and finally Certifications. Nothing in this layout needs a design tool — it can be built entirely in Word or Google Docs using headings, bold text, and bullet points, which is exactly why it parses cleanly everywhere from Naukri applications to a Workday-run campus drive. Resist the urge to add a skill-rating bar (five little dots or a progress bar next to "Excel" or "Python") — it looks polished on screen but almost never survives text extraction, and even when it does, a parser has no way to turn a visual bar into a usable data point.

Formatting Checklist Before You Export

1. Single column, no sidebar, no text boxes
2. Standard section headings from the list above
3. Contact details as plain text in the body, not a header/footer
4. Standard font, 10.5-12pt body text
5. No icons, photos, or skill-rating graphics
6. Saved as .docx (or PDF only if explicitly requested)
7. One page for 0-2 years of experience, two at most beyond that

Getting the format right is the foundation, but it only helps if the content behind it is also aimed at the right role. Pair this with our guides on how to pass ATS screening and what counts as a good ATS score to cover the keyword and ranking side of the same problem. None of this formatting advice is about making your resume look impressive — it's about making sure the impressive parts you've already earned actually get read by the person deciding whether to call you.

It's worth repeating the core idea once more because it's easy to forget under deadline pressure before a placement drive: a plain, boring, single-column resume built in Word will beat a beautifully designed one nine times out of ten, purely because it gets read correctly by whatever system stands between you and the recruiter.