ATS-friendly resume format: the rules that keep you readable

You can write the strongest resume of your career and still lose to a layout choice. The software that reads your file first does not care how it looks. It cares whether it can pull your name, your roles, and your dates into the right fields. Get the format wrong and a clean section of your experience can land in the database as a blur a recruiter never searches for.

Formatting for an applicant tracking system (ATS) is not about gaming a machine. It is about removing the small obstacles that make parsing fail. None of this costs you a single word of content. It is a checklist you run once and reuse on every application.

One column, always

The single biggest formatting decision is column count. Many polished templates split the page into a narrow sidebar and a wide main area. To you that reads as two neat columns. To a parser reading left to right, top to bottom, it often reads as one scrambled stream: your skills sidebar interleaved line by line with your job history.

Use a single-column layout. Your name and contact details at the top, then your sections stacked straight down the page. It looks plainer, and that is the point. A plain layout reads in the one order the software expects, so nothing gets shuffled.

The same warning covers tables and text boxes. A two-column skills grid built from a table can survive in one system and collapse in the next. If you cannot verify how a given employer's system handles it, do not gamble your skills section on it.

Standard section headings

A parser finds your work history by looking for a heading it recognizes. Give it the obvious words. "Work Experience", "Experience", "Education", "Skills" are read correctly almost everywhere.

Clever headings cost you here. "Where I've Made an Impact" might be true, but the system may not file what follows it as your job history, and a recruiter filtering by experience may never see it. Save the personality for the bullets underneath. Let the headings be boring and findable.

Keep your job entries in a consistent shape too: job title, company, dates, then the bullets. When every role follows the same pattern, both the software and the human skimming behind it know exactly where to look.

Fonts, bullets, and other small parsing traps

A few low-effort choices quietly decide whether your file reads cleanly:

• Fonts. Use a common, readable typeface: Arial, Calibri, Georgia, Times New Roman, or a similar standard. Decorative or heavily styled fonts can render as the wrong characters when the text is extracted.
• Bullet characters. Use a plain round or square bullet. Emoji, arrows, checkmarks, and other symbols sometimes drop out or turn into junk characters on parse, leaving a gap where your achievement should be.
• No text in images. If your name, a skills graphic, or a "rating bar" lives inside an image, the parser reads none of it. Anything that has to be searched must be real selectable text.
• Nothing critical in headers or footers. Some systems skip the header and footer region entirely. Your phone number or email tucked up there can vanish. Keep contact details in the main body of the page.

None of these change what you are claiming. They just make sure the claim actually arrives.

Consistent dates and a clean file name

Dates are a field the system tries to extract directly, which is why an inconsistent format trips it up. Pick one style and hold it the whole way down: "Jan 2022 - Mar 2024" or "01/2022 - 03/2024". Mixing "2022" in one role with "January 2022" in the next makes the parser guess, and a wrong guess can shorten your tenure on screen.

Spell out an end date rather than leaning on a symbol alone. "Mar 2024" or "Present" reads more reliably than a lone dash for a current role.

Then name the file like a professional handed it over. "Firstname-Lastname-CV" beats "resume_final_v3_REALLY-final". A clear file name is easy for a recruiter to find later in a folder of two hundred others, and it never hurts to look organized before anyone has read a word.

Save it in the format they ask for

When a posting names a file type, use it. If it says PDF, send a PDF. If the upload form only accepts DOCX, send DOCX. A modern, text-based PDF (one exported straight from your editor, not a scan or a photo of a printout) is read cleanly by most current systems and preserves your layout for the human reader.

The trap is a PDF that is secretly an image, like a screenshot saved as a PDF. There is no real text in it to extract, so the parser sees an empty page. Quick test: open your file and try to select a line of text with your cursor. If you cannot highlight it, the software cannot read it either.

Where JobScalr fits

Clean formatting is the floor, not the finish. JobScalr is a mobile app that reads a specific job posting against your resume, gives you an honest match score from 0 to 100 with the reasoning behind it, and rewrites your resume and cover letter to fit that posting without inventing skills or experience you do not have. It keeps the structure ATS-readable so the content you worked on is the content that actually gets parsed. The final review still belongs to you. It just spares you the formatting fiddle on every single application.