Your resume can be perfect on paper and still die in a database. Before anyone reads a word, software has to parse your file into name, employer, dates, titles, and skills. If it cannot do that cleanly, it does not matter how good you are.
Formatting is the one part of the hiring gauntlet you fully control. This guide gives you the rules, a template you can copy, and a checklist to run before you hit submit.
If you want to understand the why first, read our companion piece on how AI hiring screens actually work. This post is the practical half.
The One Rule That Explains All the Others
Write for the parser, then for the human. The parser wants plain, predictable, machine-readable text. The human wants proof you can do the job. Most resumes fail the first test and never get a chance at the second.
Everything below is a consequence of that single rule.
Seven Rules of an ATS-Safe Resume
1. One column, top to bottom. Tables, sidebars, and multi-column layouts scramble the reading order. The parser reads left to right, line by line, and turns a two-column layout into gibberish.
2. Use standard section headers. Write Experience, Education, and Skills. Creative headers like “Where I Have Made Magic” mean nothing to a parser and can send that whole section into the wrong field.
3. No tables, text boxes, graphics, or icons. Text inside a table or text box is often skipped entirely. That means your best accomplishment can simply not exist as far as the software is concerned.
4. Keep contact info in the body, not the header or footer. Many parsers ignore headers and footers. Put your name, phone, email, city, and state in the main text.
5. Use a standard font and standard bullets. Arial, Calibri, or Helvetica at 10 to 12 points. Plain round or dash bullets. Decorative glyphs can render as garbage characters.
6. Format dates consistently. Pick one format, like “Mar 2022 to Present,” and use it everywhere. Mixed formats confuse tenure calculations.
7. Submit the right file type. When in doubt, send a PDF built from a simple document. If the posting asks for Word, send .docx. Never send a scan or an image.
The Section Order That Works
Order matters because rankers weight early content. Put the strongest, most relevant material near the top.
- Name, contact, and target title. Your target title should match the job you are applying for.
- Summary, two or three lines. Optional, but useful when your background needs a bridge to the role.
- Skills. Only if the role is technical. Mirror the exact tool and platform names from the posting.
- Experience. Reverse chronological. Results first, duties last.
- Education. Drop graduation years if you are worried about age inference.
- Optional extras. Certifications, publications, projects. Keep them short.
Keywords Without Stuffing
Keyword matching is real, and it is easy to get wrong in both directions.
- Mirror the job title exactly. If the posting says “Marketing Manager,” your headline says Marketing Manager, even if your internal title was “Growth Lead.”
- Reuse the posting’s exact phrases where they honestly describe your work. “Customer lifecycle” and “customer journey” are not the same string to software.
- Spell out acronyms both ways once, like “customer relationship management (CRM).” You do not know which form the system scans for.
- Do not stuff. Hidden text, white text, and repeated keyword walls are detected and get you filtered as spam. Optimize for clarity, not for gaming.
The Copyable Template
Here is the structure in plain text. Replace the placeholders with your details, keep the headers literal, and save the result as a simple PDF or .docx.
Common Mistakes, Fixed
- Two-column design. Fix: single column, full width, top to bottom.
- Skills buried in icons or a graphic. Fix: a plain “Skills” section with a comma or bullet list.
- Only duties, no results. Fix: lead each bullet with the measured outcome, then the action.
- Contact info in the page header. Fix: move it into the body under your name.
- One resume for every application. Fix: keep a master copy and tailor the top third per role.
- Fancy file name. Fix: Firstname-Lastname-Resume.pdf.
Before and After: Fixing Real Bullets
The fastest way to see the difference is side by side. Here is the same experience written two ways.
- Before: Responsible for social media.
After: Grew Instagram from 2,000 to 12,000 followers in eight months. - Before: Helped with customer support.
After: Cut average response time from 9 hours to 90 minutes across a 12-person queue. - Before: Managed a team and a budget.
After: Led 5 people and a 400k budget, hitting target for six straight quarters.
Every “after” leads with a measured result, uses plain language, and mirrors terms a screener will scan for. What disappears matters just as much: adjectives, vague duties, and anything a reader cannot verify.
What the Parser Sees When Your Format Is Wrong
It helps to picture the failure. Take a two-column resume. The parser reads across, not down, so lines from your sidebar get stitched into the middle of your job history. Your skills list lands inside the description of a role you left in 2019. Your job title attaches to the wrong employer. Dates come out scrambled, so your tenure looks like a gap.
None of that is a judgment about you. It is a data problem, and the recruiter never learns it happened, because by the time a human would have looked, the system has already ranked you low and moved on. This is why the most impressive resume can lose to a plainer one. The plainer one was simply readable.
Pre-Submit Checklist
Run this every time:
- Single column, no tables, no text boxes, no graphics
- Standard section headers, spelled the usual way
- Contact info in the body, not the header or footer
- Target title matches the job posting
- Top third has at least three measured results
- Acronyms spelled out at least once
- One consistent date format throughout
- File is a clean PDF or .docx, named clearly
- No hidden or white text, no keyword walls
- Read it once as a human, out loud
The Short Version
- Format for the parser first, the human second.
- Simple structure and standard headers beat clever design every time.
- Mirror the job title and exact phrases, but never stuff keywords.
- Results in the top third, duties last.
- Run the checklist before every single application.
FAQ
Does the ATS reject me automatically? Usually it filters or ranks you before a human reviews. The effect feels the same. The fix is the same too: make your file easy to read.
Can I use a resume builder or Canva template? Only if it exports to a single-column, text-based document. Anything designed as a poster or infographic will parse badly.
Should I include a photo? No, not for US employers. It adds nothing for the parser and invites bias in review.
Does a referral really skip all of this? Often, yes. A referral usually means a person pulls your file forward, and the ranking matters far less. If you have any connection to the company, use it before you apply.
How long should the resume be? One page under roughly ten years of experience, two at most after that. Length is not the problem, but unreadable density is.
Why does any of this matter?
The formatting rules exist because software, not a person, often reads your application first. If you want to understand what that screen is actually doing, and why it goes wrong, read our companion analysis on how AI hiring screens work.
About The Author
