← All posts

14 May 2026 · Rehurz

Crafting a Resume That Actually Passes the ATS

Many job applications are filtered out before a human recruiter ever reads them. The culprit is usually not weak experience, but a resume that an applicant tracking system could not parse or match to the right keywords. If your goal is to make your resume pass ATS screening and land in front of someone who can actually move you forward, this guide walks you through what actually matters.

Quick answer: An ATS-friendly resume uses a clean single-column layout in .docx or plain PDF format, mirrors the exact keywords from the job description (particularly job titles, required skills, and tools), uses standard section headings, and strips out tables, text boxes, images, and anything in the header or footer. The ATS does not evaluate your writing quality; it extracts text and checks for keyword matches. Get the parsing and terminology right, and your resume reaches a human reviewer.

What an Applicant Tracking System Actually Does

An ATS is software that companies use to collect, organize, and filter job applications at scale. When you submit your resume, the ATS parses its text, extracts structured data like your name, contact details, job titles, skills, and education, and stores everything in a searchable database.

Recruiters then search or filter that database. They might search by job title, a required certification, years of experience, or a specific tool like "Python" or "Salesforce." If your resume's text did not parse correctly, or if the terms you used don't match what the recruiter searched for, your application simply never surfaces.

A few things an ATS does NOT do: it does not grade your writing. It does not read your bullet points and evaluate how compelling they are. It does not care about your font choices, color palette, or creative design. In fact, those things often cause parsing failures. The ATS is a text extraction and matching engine. Treat it accordingly.

One widespread myth is that a specific, precise percentage of resumes are rejected by ATS alone. The real picture is more nuanced: ATS filtering, recruiter search habits, and plain application volume all interact. What is certain is that a resume that parses poorly, or that does not contain the terms a recruiter searches for, has very little chance of being seen.

The File Format Decision

The safest format for most ATS submissions is .docx. Microsoft Word files are consistently parsed well across virtually all major ATS platforms; the text is cleanly structured and the tooling around parsing Word documents is mature and reliable.

PDF is widely accepted, with one important caveat: it needs to be a text-based PDF, not a scanned image or a design export that embeds text as paths or outlines. If you created your resume in Canva, Figma, or a similar design tool and exported it as PDF, there is a real chance the ATS cannot read any of it. Save a plain .docx version as a backup and submit that unless the posting specifically asks for PDF.

Avoid .pages files, .odt, or any format not explicitly mentioned in the job posting. When in doubt, use .docx.

Formatting That Survives Parsing

The most reliably ATS-friendly resume layout is a single-column, top-to-bottom text document. Everything the ATS needs to read should flow linearly, the way a screen reader processes content.

These formatting choices survive parsing consistently:

  • Standard fonts (Arial, Calibri, Times New Roman, Georgia)
  • Bullet points using standard hyphen or filled circle characters, not decorative symbols
  • Bold and italic used sparingly for emphasis within text
  • Section headings as plain text, slightly larger or bolded
  • Margins between 0.5 and 1 inch

What to Avoid Completely

These are the most common resume formatting mistakes that break ATS parsing:

Tables and multi-column layouts. ATS systems read left to right, line by line. A two-column resume that looks clean to a human often becomes scrambled text when the ATS parses it, mixing content from both columns in unpredictable ways.

Text boxes. Content inside a text box is frequently invisible to ATS parsers entirely. If your contact information, skills summary, or headline is sitting in a text box, it may simply not exist from the ATS's perspective.

Images and graphics. The ATS reads text, not pixels. Skill rating bars, profile photos, icons, and decorative charts add nothing to parsing and can interfere with surrounding text that the parser is trying to extract.

Headers and footers. Many ATS platforms ignore content in the header and footer regions of a document. Putting your name or phone number only in the header is a surprisingly common mistake that can cause your application to be stored without your name attached.

Unusual fonts and decorative elements. Non-standard fonts may render as garbled characters in the parsed output. Simple is better here.

Matching Keywords From the Job Description

This is where most applicant tracking system resume submissions fail, and it often has nothing to do with actual qualifications. ATS keyword matching is fundamentally a text comparison problem. If the job description says "project management" and your resume says "project oversight," those phrases may not match for many systems. If the posting lists "React.js" and your resume says "ReactJS," some parsers will recognize them as equivalent and some will not.

The practical fix: read the job description carefully and use the same terms it uses. Pay particular attention to:

  • Job title. If the company calls the role "Senior Software Engineer," use that exact phrase somewhere in your resume, ideally in your most recent job title or a profile summary at the top.
  • Required skills and tools. List the exact tools, technologies, or methodologies the posting mentions. If it says "AWS Lambda," don't just write "cloud computing."
  • Certifications and qualifications. If the posting asks for "PMP certification," spell it exactly that way, not "project management certification."
  • Recurring phrases. If the job description uses "stakeholder management" or "cross-functional collaboration" repeatedly, those phrases are worth mirroring in your bullet points where they genuinely reflect your experience.

Do not stuff keywords in white text or use hidden text tricks to game matching. Modern ATS platforms flag this, and it looks terrible to any human who reviews the parsed output.

Section Structure That Works

Use section headings that ATS systems are built to recognize. The standard set is:

  • Summary or Profile (optional, but useful for placing keywords early)
  • Work Experience or Professional Experience
  • Education
  • Skills
  • Certifications (if applicable)
  • Projects (common in tech, especially for early-career candidates)

Avoid creative headings like "My Story," "Where I've Been," or "What I Bring." The ATS parser looks for known heading patterns to classify the content that follows. An unrecognized heading may cause the content below it to be miscategorized or skipped.

Within Work Experience, use a consistent format: company name, job title, dates (month and year), followed by bullet points. Dates formatted as "Jan 2022" or "January 2022" both parse well. Formats like "2022-01" can cause issues with some systems.

Keep bullet points action-oriented and specific. Start with a verb ("Designed," "Led," "Built," "Reduced"), describe what you did, and include a quantified result where you have one. The ATS does not evaluate writing quality, but a human reviewer will, so write bullets that work for both audiences.

A Practical ATS Checklist Before You Apply

Run through this before each submission:

  • File is .docx or a text-based PDF (not a design export)
  • Single-column layout with no tables, text boxes, or side-by-side columns
  • Name and contact details appear in the body of the document, not only in the header or footer
  • Standard fonts only, no decorative symbols used as bullets
  • The job title from the posting appears somewhere in your resume
  • Required skills and tools from the job description are listed using the exact terminology from the posting
  • Section headings are standard (Work Experience, Education, Skills, Certifications)
  • No images, icons, skill bar graphics, or decorative elements
  • Dates are consistently formatted throughout
  • You have read the job description and confirmed your resume reflects the language it actually uses

Frequently Asked Questions

Does an ATS rank resumes or just filter them? It depends on the system. Some ATS platforms assign a relevance score based on keyword presence and placement; others make resumes searchable and let recruiters filter and sort manually. Either way, clean parsing and keyword matching are what determine whether your resume surfaces at all. Think of it less as a score to maximize and more as a text-matching problem to solve.

Should I have different resume versions for different roles? Yes, if the roles differ meaningfully in title, required tools, or skills language. You don't need to rewrite from scratch every time, but tailoring your summary, job title framing, and skills section to match the specific posting's language is worth the time. A single generic resume submitted across very different functions will consistently underperform targeted versions.

What if the company uses LinkedIn Easy Apply? LinkedIn Easy Apply typically sends your LinkedIn profile data directly to the employer, not just a parsed PDF. Fill in all form fields accurately and completely; don't rely on your resume upload to populate everything automatically. If a field asks for a skill, list it explicitly.

Can a recruiter see my original resume after ATS parsing? Usually yes. The parsed version is what gets searched and filtered, but recruiters can typically click through to view your original document. This means your resume needs to work for both the ATS and a human reader. Formatting that is too sparse, or bullet points crammed with keywords at the expense of clarity, will hurt you at the human review stage even if you pass the initial filter.

Is it worth paying for an ATS-optimization service? The core principles covered here are well-established and do not require a paid service. Standard formatting, keyword mirroring from the job description, and clean file formats cover the vast majority of parsing issues. Tools that show you a "compatibility score" can be useful for a quick sanity check, but the diagnostic fix is always the same: cleaner formatting and closer keyword alignment with the specific posting.

Preparing for the Interview Itself

Getting your resume past the ATS is the first hurdle, not the final one. Once a recruiter opens your document and decides to move forward, you need to perform in the actual interview. Many candidates who have strong, well-formatted resumes get caught off guard in that conversation because the resume got them in the door but the preparation was not there.

Prepare for the interview itself with Rehurz: a live voice mock interview that reads your uploaded resume and the job description, then runs a real conversation tuned to your role, domain, and seniority level. It is not a fixed question bank. It listens to your actual answers, catches what you glossed over, and asks the follow-up a sharp interviewer would ask. After the session, you get a role-specific scorecard with per-question feedback, ideal answers written from your own transcript, and a curated set of resources to close the gaps before the real interview.

Your first interview is free, no card required. See how it feels to be cross-questioned on the exact resume you spent time optimizing.

Getting your resume past the ATS puts it in front of a person. What happens next depends on how you show up in the conversation. Spend the time to get both right.