ATS Resume Formatting Guide

Most resume advice obsesses over wording. But the wording does not matter if the software stores a scrambled version of your file. ATS resume formatting is about one thing: making sure the applicant tracking system can read your document top to bottom and drop each piece into the right field. Get the layout wrong and your best job ends up missing or chopped in half before a recruiter sees it. Here is exactly how to lay out a resume that parses clean.

Why layout decides whether you parse clean

When you upload a resume, the system reads the raw text and sorts it into fields like name, work history, and skills. It reads in a rough top-to-bottom order, following how the text sits in the file. Anything that breaks that flow can confuse it. (We walk through the parsing step in detail in how an ATS reads your resume.)

So the goal of formatting is not to look fancy. It is to be boring in a way the machine understands. A clean single-column document with standard headers reads correctly almost every time. A designed two-column template with graphics is where things break.

The do list

These are the moves that keep your resume readable.

Use a single column. One column, top to bottom. The parser reads it in the order you wrote it, and nothing gets stitched together wrong.
Use standard section headers. Write the obvious words: Experience, Work Experience, Education, Skills, Certifications. The parser looks for these to know where a section begins. Clever headings like “Where I’ve Made an Impact” mean nothing to it.
Put your name and contact info in the body. Keep them in the main text near the top, not in the document header or footer region, which some parsers skip.
Use standard fonts. Arial, Calibri, Helvetica, Georgia, Times New Roman. Common fonts render and extract reliably.
Keep dates in a plain format. Month and year, like “Mar 2023 to Present,” placed next to the role. Consistent dates help the system build your timeline.
Use simple bullets. A standard round bullet and a line of text. That is all you need.
Spell out then abbreviate. Write “Search Engine Optimization (SEO)” once so you match a search for either term.

The don’t list

These are the things that cause misreads.

No tables. A table looks tidy but the parser may read across rows and merge unrelated cells. Skills land in the middle of a job, dates detach from roles.
No multi-column layouts. Same problem as tables. The reader can run straight across both columns and blend two different lines.
No text boxes. Text inside a box is often invisible to the parser. A whole sidebar of skills can read as empty.
No graphics, charts, or rating bars. Those skill-level bars carry no readable text. The parser sees a picture and reads nothing from it.
No logos, icons, or headshots. They add no machine-readable content and only raise the odds of a misread. A US resume does not need a photo.
No critical text in headers or footers. If a field gets skipped there, the recruiter never sees it.

Fonts, file type, and naming

Fonts. Stick to the common set above at 10 to 12 point for body text. Decorative or downloaded fonts can extract as gibberish or not at all.

.docx versus PDF. Both work in most modern systems, and Greenhouse, Ashby, Lever, and Workday all handle them. A clean, text-based PDF is a safe default because it preserves your layout. Two cautions. Never upload a PDF that is really a scanned image, because there is no selectable text to read. And if an application form specifically asks for .docx, give it .docx. When in doubt, a simple single-column file parses well in either format.

File naming. Name the file like a professional document: FirstName-LastName-Resume.pdf. It is the version a recruiter may see and download, and it is easier to find later than resume-final-v3.pdf.

Where keywords belong

Formatting gets you read. Words get you matched. The two work together, because a keyword buried inside a graphic or a text box does not count if the parser cannot see it.

Put your important terms in plain text, inside real sections:

Skills section for the concrete tools, languages, and methods.
Experience bullets where you show the skill in action with a result attached.
Summary line for a couple of the role’s core terms, written naturally.

Resist the urge to paste a hidden block of keywords in white text or a tiny font. Recruiters and modern systems catch that, and it reads as exactly what it is. The better path is weaving the right terms into real sentences, which we cover in resume keywords without stuffing.

Keeping your formatting clean and your keywords visible is fiddly to do by hand for every posting. Linora reads the job description and gives you a tailored resume draft that keeps a clean, parseable structure while mirroring the role’s language. You review it and submit it yourself. See how it works at getlinora.com.