MyPrepGuruGuides › Resume & ATS
ATS-Friendly Resume Formatting: What Helps, What Is Myth
Search for resume advice and you will find confident rules: never use a table, always use a PDF, never use a PDF, avoid color, keep it to one page. Some of these have a kernel of truth. Others are repeated so often that people treat them as law.
This guide sorts formatting choices into those that commonly cause trouble and those that are mostly myth. It builds on our explainer on how ATS keyword matching works, so if you want the bigger picture first, start there.
The same caveat applies here: systems differ, and employers configure them differently. We cannot know how a given company's setup will read your file, and no formatting choice guarantees any outcome. The aim is to reduce avoidable risk while keeping your resume pleasant for a human to read, because a person will eventually read it.
What parsing is, in one paragraph
When you upload a resume, many systems try to extract the text and sort it into fields: name, contact details, employers, titles, dates, education, skills. That process is called parsing. A clean, predictable layout tends to be easier for software to read. A decorative or unusual layout can sometimes lead to jumbled text or missing fields. The trouble is usually about structure, not about whether the resume looks plain or fancy to the eye.
Formatting choices that commonly cause trouble
These are risks, not certainties. Many modern parsers handle some of them fine, but you cannot see which kind you are dealing with.
Multiple columns. Text may be read straight across both columns, mixing a sidebar of skills into the middle of a job description. A single main column is a safer default.
Tables and grids. Cell contents can be read in an odd order or dropped. If you use a table for layout, consider replacing it with simple paragraphs and bullets.
Text boxes, shapes and graphics. Content inside them may be skipped. Keep anything important in the main body.
Contact details in the header or footer. Some parsers ignore these areas. Putting your name and contact line at the top of the main body is a low-cost precaution.
Skills as images or rating bars. A row of dots or a "90%" bar conveys little to software, and little to a human too, since the scale is arbitrary. Write skills as words.
Icons in place of labels. A tiny phone icon followed by a number usually reads fine to a person, but an icon instead of text can confuse a parser. Plain text is safer.
Unusual section names. Headings such as "My Story" or "Where I've Been" may not be recognized. Standard labels like Experience, Education and Skills are widely understood.
Inconsistent dates. Mixing "Jan 2022," "01/22" and "2022" can make tenure harder to calculate. Pick one format and keep it.
Scanned or image-based files. A photo or scan of paper may contain no selectable text at all.
A table of choices and safer habits
| Choice | Possible issue | Safer habit |
|---|---|---|
| Two-column template | Mixed reading order | One main column |
| Skills in a graphic | Not read as text | List skills in words |
| Name only in header | May be missed | Name and contact in the body |
| Creative headings | Sections not recognized | Standard headings |
| Many fonts and effects | Odd characters, uneven rendering | One or two common fonts |
| Special bullet symbols | May appear as stray characters | Standard round bullets |
| Photo or logo | Takes space and adds nothing a parser can use | Leave it out unless asked |
Myths worth setting aside
Myth: you must use plain black text on white with no styling at all. Modest formatting is fine. Bold for job titles, a slightly larger name, and consistent spacing typically cause no problem and help human readers scan. The risk comes from structure that confuses reading order, not from bold type.
Myth: PDFs are always bad (or always required). There is no universal answer. Follow the employer's instructions first. If you have a choice, a text-based PDF or a standard Word document are common and often parse well. What matters is that the file contains real, selectable text. A quick test: open the file, select all, copy, and paste into a plain-text editor. If the text appears in a sensible order, that is a reassuring sign. If it is scrambled, simplify the layout.
Myth: a special "ATS template" is required. Templates marketed this way are often just simple, single-column documents. You can make one yourself in any word processor. Be skeptical of anyone selling certainty.
Myth: a one-page limit is an ATS rule. Length is mostly a human preference and varies by field and seniority. Page count is not something we know parsers to care about. Write what is relevant and trim what is not.
Myth: you must repeat every keyword many times. Repetition for its own sake reads badly and does not help a person. Use the employer's wording where it truthfully applies, and put skills in the context of real accomplishments.
Myth: hidden white text will fool the system. It is a poor bet. It can look dishonest if discovered, and it does nothing for the human reader. Skip it.
Myth: a formatting error means automatic rejection. No one outside an employer can promise what happens to a given file. A parsing glitch might simply mean a messy profile that a recruiter reads around, or it might be more serious. You cannot know, which is why a clean file is a sensible habit rather than a magic fix.
Choices that are mostly about readability
Some decisions have little to do with software and much to do with the person reading:
- Font size: big enough to read comfortably, with consistent sizes for similar elements.
- White space: margins and gaps that keep the page from feeling crowded.
- Reverse-chronological order: the most recent role first is the common convention, though other structures can suit some situations.
- Bullets that start with action verbs and carry specifics: this matters more than any layout choice. Compare "Responsible for reports" with "Built a weekly sales report that replaced three manual spreadsheets" (hypothetical).
A simple formatting checklist
- One main column, standard headings, consistent dates.
- Name and contact details in the body of the page.
- Skills written as words, not graphics.
- Common fonts, standard bullets, modest styling.
- Text-based file in the format the employer requests; copy-and-paste test passed.
- File named sensibly, such as "FirstName-LastName-Resume."
- A final read-through by a human, preferably out loud.
Formatting is the small part
Formatting avoids problems; it does not create strengths. Once the file is clean, spend your time on the content: specific bullets, the right emphasis for the posting, and details you can discuss. See how to tailor your resume to a job description for that routine, and being ready to explain every line for what happens after the resume gets you into the room.
Where Resume Feedback fits
MyPrepGuru's Resume Feedback gives a keyword and skill-overlap estimate of your resume against a job description, with matched and missing keywords. It is our own estimate for practice. It does not predict any real ATS result, and it cannot tell you how a particular employer's system will parse or rank your file. Its value is in showing which terms from the posting appear in your resume and which do not, so you can decide, honestly, what to add or leave out.
Practice this
Run the copy-and-paste test on your current resume file and note anything that comes out jumbled or missing. Fix the layout, then read the plain-text version aloud, since that can help you catch scrambled order and awkward wording. After that, pick the bullets that match a job description you care about and practice explaining them aloud. A voice mock interview built from that job description is a good way to check that your formatted resume and your spoken story line up. It is for practice, not for use during a real interview.