Resume Format for Applicant Tracking Systems: What Recruiters Control

The parsing problem nobody on the hiring team owns

When a strong candidate applies and never gets a call, recruiters usually assume someone reviewed the resume and passed. Often nobody saw it. The applicant tracking system parsed the resume, scrambled the content, and ranked the person below the cutoff. According to Harvard Business School and Accenture's Hidden Workers research, 88% of employers agree that qualified high-skills candidates get vetted out of the process because they don't match the exact criteria in the job description — and 94% say the same for middle-skills roles. Jobscan research cited in the same report found 99% of Fortune 500 companies use an ATS.

Resume format is usually treated as the candidate's problem. It isn't. If your pipeline systematically loses qualified people to parsing errors, that's a recruiting operations issue — and it's fixable on your side.

What an ATS actually reads

An ATS doesn't "see" a resume the way a recruiter does. A parser extracts text, then maps that text into fields: name, contact details, job titles, dates, skills, education. Everything that helps this mapping raises the candidate's rank. Everything that confuses it — columns, tables, graphics, unusual section names — either gets dropped or lands in the wrong field.

Workable's parsing guide describes it bluntly: the parser extracts text and ignores the rest. A beautifully designed two-column resume can arrive as alphabet soup.

7 format choices that break parsing

1. Two-column layouts. The parser reads left to right, line by line. A sidebar skills column gets interleaved with work experience.
2. Tables and text boxes. Content inside tables is often skipped or reordered.
3. Contact details in the header or footer. Many parsers ignore headers and footers entirely, so the candidate becomes uncontactable.
4. Creative section titles. "My Journey" instead of "Work Experience" confuses field mapping.
5. Skill bars, icons, and graphics. Competency percentages rendered as bars are invisible to the parser.
6. Inconsistent dates. Mixing "05/2023," "'23," and "present" breaks experience calculations.
7. Scanned or image-only PDFs. The parser sees an image, extracts nothing, and the application dies silently.

What recruiting teams actually control

Three fixes sit on your side of the table:

• Publish format guidelines in the application flow. A one-line instruction — "submit a single-column .docx or text-based PDF" — removes the most common failure before it happens.
• Audit your parser quarterly. Submit test resumes in the formats your candidates actually use, then check what the system extracted. The plain-text test (paste a resume into a text editor) is free and takes minutes.
• Replace negative filters with affirmative ones. The HBS research recommends shifting ATS filters from excluding (no degree, employment gap) to identifying candidates with the skills that correlate with role performance. HR Dive's coverage calls this the single highest-leverage change employers can make.

The India context

High-volume hiring in India compounds the problem. Enterprise and GCC hiring funnels routinely handle thousands of applications per role, and candidates arrive through Naukri, LinkedIn, and direct career portals — each exporting different resume formats. Recruiters who assume the job portal "cleans" the resume are wrong; parsing quality still depends on the source file. For a closer look at what these checks can and cannot tell you, see our breakdown of the ATS resume check myth.

Pair parsing with skills-based screening

Formatting fixes stop candidates from being lost. They don't tell you who's good. A resume that parses perfectly can still overstate skills, and one that parses badly can hide a strong performer. That's why teams pair ATS parsing with structured first-round screening — AI candidate screening that scores what people can actually do, not how well their resume survived the parser. If you're adding screening to an existing ATS stack, these ATS integration checks will save you a failed rollout.

Before you blame the candidate

The next time a hiring manager asks why a role is empty while the ATS shows 400 applications, don't start with "the talent isn't there." Check what the parser did to the top 50 resumes. You'll usually find qualified people the format quietly deleted. Structured interview assessments give those candidates a second, fairer signal — and give your team data that survives any format.