A single sheet of paper with blank placeholder lines and a green checkmark passing over a scanner bar

How to Format a Resume to Pass the ATS

0Shares

You tailor the resume, the online tool gives it an 80 percent match, you hit submit, and you are rejected within a day. It can feel personal. Often it is mechanical: a piece of software read your resume, could not make sense of the layout, and filed you under “unreadable” before a person ever looked.

Most mid-size and large employers run resumes through an applicant tracking system, or ATS, that parses your document into structured fields. A beautiful resume that a parser cannot read is worse than a plain one it can. The good news is that ATS-friendly formatting is not about tricks, it is about clean structure, and once you know what breaks a parser you can avoid all of it. Here is how to format a resume that survives the software and reaches a human.

Bottom Line First

An ATS reads your resume and sorts its contents into fields like name, job title, and dates. Formatting that confuses it, mainly tables, multiple columns, text boxes, images, and contact details in the header, can scramble or hide your information. A single-column layout with standard section headings, a common font at 10 to 12 points, and simple bullet points parses reliably. Structure matters more than whether you send a PDF or a Word file.

What an ATS Actually Does

An applicant tracking system is software that receives, stores, and sorts job applications. When your resume arrives, the ATS parses it, meaning it tries to pull your details into a database: your name here, each job title there, dates, employers, skills. Recruiters then search and filter that database.

The failure point is parsing. If the system misreads your layout, your job title can end up merged with a date, or your contact information can vanish entirely, and a recruiter searching for your exact background never sees you. As one job seeker who tested how these systems parse resumes found, the same content can score very differently depending purely on how it is laid out. Your goal is to make parsing effortless.

The Formatting That Breaks Parsers

These are the design choices that look fine to you and turn to gibberish inside an ATS. Avoid them.

  • Tables. Parsers frequently read tables in the wrong order, scrambling cells into an incoherent string. Do not lay out sections in tables.
  • Two-column layouts. The clean-looking sidebar is a top offender, because the parser often merges the left and right columns unpredictably.
  • Text boxes. Content inside a text box is regularly skipped entirely, so skills or contact details placed in one may never be read.
  • Header and footer contact info. Many systems ignore the document header and footer, so a name or phone number placed there can be lost. Keep them in the main body.
  • Images and icons. Graphics are invisible to parsers, so skill bars, rating dots, or an icon next to your email communicate nothing to the software.

The Formatting That Works

The reliable format is almost boring, which is the point. A parser has no trouble with it.

  • A single column. One column, top to bottom, is the safest structure for clean parsing.
  • Standard section headings. Use plain labels the software expects, like Work Experience, Education, and Skills, rather than clever custom titles.
  • A common font, 10 to 12 points. Arial, Calibri, Helvetica, or Times New Roman parse dependably. Your name can go a little larger, but keep body text readable and avoid anything under about 9 points.
  • Simple bullet points. Standard round or square bullets are fine. Skip decorative symbols.
  • Normal margins. Around three-quarters of an inch to an inch keeps the layout clean without cramping the text.

PDF or Word? Settling the Myth

This is the question everyone asks, and the honest answer annoys people because it is not a clean rule. A Word document has long been the safe default, and it still is. But most modern systems, including the major ones, now parse a clean, text-based PDF just as well.

The real variable is not the file type, it is the structure inside it. A messy, multi-column Word file can parse worse than a simple single-column PDF, and a PDF stuffed with tables and text boxes will fail no matter how modern the ATS is. So the format debate matters less than getting the layout right. When a job posting specifies a file type, follow it. Otherwise, a clean single-column document in either format is fine.

Keywords Without the Stuffing

Recruiters search the parsed database using terms from the job, so your resume should genuinely contain the language of the role you want. If the posting says “project management” and “stakeholder communication,” and those describe your work, use those exact phrases rather than a personal synonym.

That is matching, not stuffing. The old hacks, hiding a wall of white-text keywords or repeating a term unnaturally, tend to get flagged and read as spam by both software and the humans who eventually see it. Mirror the job’s real vocabulary where it honestly applies, and let the rest of the resume back it up.

Key Takeaways

  • An ATS parses your resume into fields, and a layout it cannot read can filter you out before a human looks.
  • Tables, two-column designs, text boxes, header or footer contact info, and images all break parsing.
  • A single column, standard headings, a common 10 to 12 point font, and simple bullets parse reliably.
  • Structure matters more than PDF versus Word, though a clean text-based version of either works.
  • Use the job posting’s real keywords where they genuinely apply, and avoid white-text or repetition tricks.

Frequently Asked Questions

Should I send my resume as a PDF or a Word document?

Either can work if the layout is clean. Word has been the traditional safe choice, but most modern systems parse a text-based PDF just as well. What matters far more is a single-column structure without tables or text boxes. If a job posting requests a specific format, follow that instruction.

Why was my resume rejected if it had a high match score?

Match scores from third-party tools do not always reflect how the employer’s actual ATS parses your file, and a rejection can also come from a recruiter, not the software. Formatting that scrambles your job titles or dates can lower your real searchability even when a separate tool rates the content highly.

Do two-column resumes really fail ATS systems?

They often cause problems. Many parsers read across the page and merge the two columns, jumbling your content. A two-column resume can look polished to a person while turning into scrambled text inside the software, so a single-column layout is the safer choice.

How many keywords should I put in my resume?

There is no magic number. Include the real terms from the job description that genuinely describe your experience, phrased the way the posting phrases them. Avoid repeating keywords unnaturally or hiding them in white text, since those tactics get flagged and do not help with human reviewers.

What To Do Next

Before your next application, open your resume and run a quick audit: is it a single column, are your name and contact details in the body rather than the header, and is anything living inside a table, text box, or image? Fixing those is usually a fifteen-minute job, and it is the difference between a resume the software can read and one it quietly discards. Get the structure right, mirror the job’s real language, and you put the decision back where it belongs, with a person. For more coverage, see ShoutPost’s Business and Education sections.

Leave a Reply