How to Write a Resume That Gets Past ATS Filters

You can write a genuinely excellent resume and still have it rejected before a human ever sees it. Most companies — and nearly all large employers — run applications through an Applicant Tracking System (ATS) before any human review. Understanding how ATS screening works is the prerequisite to writing a resume that gets through.

How ATS Systems Work

An ATS is software that:

1. Parses your resume into structured data (name, work history, skills, education)
2. Compares your parsed data against the job description requirements
3. Scores or ranks candidates based on keyword and criteria matches
4. Surfaces top matches to recruiters while filtering out low-scoring applications

The key insight: ATS doesn't read your resume the way a human does. It extracts data. If your formatting is complex, or if your relevant experience is buried in non-standard sections, the ATS may misparse your resume and under-rank you — even if you're highly qualified.

Formatting: What ATS Can and Can't Parse

Safe formatting choices:

• Single-column layouts
• Standard section headings ("Work Experience," "Education," "Skills")
• Plain text or docx format (not PDFs with complex formatting, unless the job application specifically accepts PDF)
• Standard fonts (Arial, Calibri, Times New Roman, Helvetica)
• Bullet points using standard • characters

Risky formatting choices that ATS often misparse:

• Two-column layouts (the ATS may read columns left-to-right across columns, scrambling content)
• Text boxes (content inside may be skipped entirely)
• Headers and footers (contact information in a footer may not be extracted)
• Tables (some ATS systems skip cell content)
• Graphics, icons, and images (ATS ignores images)
• Creative fonts and special characters

The harsh truth: The beautifully designed resume template with skills bars, icons, and a sidebar? It may look great to a human — but the ATS may read it as gibberish.

The Right Resume Structure

Use these section names (exact names matter — "Professional Experience" is safer than "My Journey"):

1. Contact information — name, email, phone, LinkedIn URL, city/state (not full address)
2. Summary or Professional Summary — 2–3 sentences with your title, years of experience, and key value proposition
3. Work Experience — listed in reverse chronological order
4. Education
5. Skills
6. Optional: Certifications, Projects, Publications

Writing ATS-Optimized Bullet Points

Every bullet point should follow this formula: action verb + task/responsibility + quantified result.

Before:

Responsible for managing social media accounts and growing the company's online presence.

After:

Grew LinkedIn following from 2,000 to 15,000 in 12 months by publishing 3 industry posts per week, increasing engagement rate from 1.2% to 4.8%.

The after version:

• Starts with a strong action verb (Grew)
• Specifies what you did
• Quantifies the result with real numbers

ATS systems look for numbers and measurable outcomes — and so do human recruiters.

The Keyword Strategy

The single most important thing you can do to improve ATS performance: mirror the language in the job description.

1. Read the job posting carefully.
2. Identify repeated keywords (skills, technologies, job titles, certifications).
3. Incorporate those exact keywords into your resume — naturally, not as a list.
4. If the job says "project management," don't write "project coordination."
5. If the job says "Python," don't write "Python programming language" — use the exact term.

Where to place keywords:

• Summary section (front-loaded keywords get full weight)
• Work experience bullet points (with context)
• Skills section (for exact term matching)

Build Your Resume

Use DevZone's Resume Builder to create a clean, ATS-compatible resume with proper formatting and structure. The templates are designed to parse correctly while still looking professional to human reviewers.

The Skills Section

List skills in a simple, comma-separated or bulleted format:

Programming Languages: Python, JavaScript, SQL, Go
Frameworks: React, Django, FastAPI
Tools: Docker, Kubernetes, Git, Jira

Don't use skill bars (showing "Python: ████████░░ 80%") — ATS can't parse percentages attached to skill names, and human reviewers find them less credible than just listing the skill.

Common Resume Mistakes That Kill ATS Scores

Objective statements instead of summaries. "Seeking a challenging position..." is meaningless. A summary that names the role and your relevant experience tells both ATS and humans what you're applying for.

Generic descriptions. "Responsible for helping customers" gives ATS nothing to match. "Resolved 50+ technical support tickets daily, achieving 98% satisfaction score" gives it keywords and evidence.

Irrelevant work history. If you're applying for a software engineering role and your resume lists 5 years of restaurant work from 15 years ago, that padding dilutes keyword density and can lower your ATS score.

Education buried at the bottom for senior roles. For experienced professionals, education goes after work experience. For recent graduates, it can go near the top.

Missing the resume to the job. The single most effective thing you can do is customize your resume for each application. Not a full rewrite — but adjust the summary, reorder bullet points, and ensure the top keywords from the job description appear prominently.

FAQ

Should I submit a PDF or Word document?

When given the choice, use Word (.docx) unless the application specifically requests PDF. Many ATS systems parse Word documents more reliably than PDFs. If you're submitting a PDF, ensure it's a text-based PDF (not a scanned image), created directly from Word or a resume tool.

How long should my resume be?

One page for 0–5 years of experience. Two pages for 5–15 years. Three pages only for senior executives or academics with extensive publications. ATS doesn't penalize length — humans get fatigued reading more than 2 pages.

Can ATS detect keyword stuffing?

Some modern ATS systems use NLP (natural language processing) and can detect suspicious keyword stuffing. More importantly, human reviewers definitely notice it. Add keywords naturally in context, not as a wall of text.

Is it true that some ATS systems reject if you use the wrong font?

Font alone won't cause rejection, but ATS can struggle to extract text from PDFs created from non-standard fonts. The safest approach: write in a standard font, export to PDF from Word or Google Docs, and test your PDF by selecting and copying the text — if you can copy it, the ATS can extract it.