12 Common Resume Formatting Mistakes to Fix Now

Format for Robots, Write for Humans

Most advice about common resume formatting mistakes mixes real technical risks with personal taste. That's not useful when you're doing a final pass before sending applications. You need to know what breaks parsing, what slows down a recruiter, and what just makes your resume look older than it is.

This list is for corporate professionals doing that last check. Not first-time writers. Not portfolio-heavy designers. Just someone with a solid resume who wants to catch the formatting mistakes that carry a real cost before they hit send.

The biggest myth is that every “modern” design choice is bad. It isn't. Some older ATS rules are still very real. Others are outdated and depend on the system, the file, and the layout. The point is to know which mistakes can stop your resume from being read, and which ones make it harder to scan.

1. Multi-Column Layouts That Break in ATS Systems

Two-column resumes are one of the easiest ways to make a strong resume harder to read.

The problem is not style. The problem is reading order. A human can usually follow a left sidebar and a main content column. An ATS often cannot. If the parser pulls text top to bottom across both columns, your skills, job titles, dates, and bullets can land in the wrong sequence. The resume still looks polished on screen, but the extracted text is messy, and messy text is what many systems search.

A common version looks like this: contact details and skills in a narrow left column, experience in a wider right column. In a PDF, that layout can look efficient. In parsed text, it can turn into a stack of mixed fragments. I have seen resumes where a certification lands in the middle of a job bullet, or a city and phone number get inserted between company name and title.

Practical rule: If your PDF does not copy and paste in the right order, do not trust the layout in an ATS.

The fix is straightforward. Use one main column for all core content. Keep your name, contact details, summary, experience, education, and skills in a single reading path from top to bottom. If space gets tight, cut weaker bullets, shorten older roles, or remove low-value sections instead of forcing the page into columns. If you need help diagnosing layout-related parsing issues, this guide on why a resume may not be passing ATS breaks down the common failure points.

Use a quick copy-paste test before you send it:

• Open the PDF and copy all text: Paste it into a plain text editor.
• Check reading order: Your name, contact info, experience, and bullets should appear in the same sequence a recruiter sees.
• Watch for merged lines: If dates, titles, and bullets collapse together, the layout is too complex.

A one-column resume is not conservative. It is easier to parse, easier to scan, and harder to break.

Here's a quick visual explainer:

2. Critical Information Hidden in Headers, Footers, or Text Boxes

This one catches experienced professionals all the time. They use the header to save space and put their name, phone, email, and LinkedIn there. It looks tidy. It's also risky.

Many ATS systems skip header and footer zones during parsing, which is why Santa Clara University's ATS formatting guidance specifically recommends keeping contact details in the main body of the document. Text boxes create a similar problem because they sit outside the normal reading flow.

The specific fix

Put your contact block at the very top of page one in standard body text. Not in a floating sidebar. Not in a footer. Not embedded in a logo.

Use something simple like this:

• Name: Full name on its own line
• Phone: Regular text
• Email: Regular text
• LinkedIn: Regular text
• Location: Optional, if relevant

A ready-to-copy header looks like this:

Jordan Lee
(555) 123-4567 | jordan.lee@email.com | linkedin.com/in/jordanlee | Boston, MA

If your summary or key skills are inside a text box, pull them back into the document body too. A recruiter can't call you if the parser never picked up your phone number.

3. Inconsistent Date Formats Across Roles and Experiences

Date formatting looks minor until it slows the reader down.

A hiring manager scanning your resume is trying to answer a simple set of questions fast: Where did you work, for how long, and what came next? If one role says “Jan 2023 - Present,” another says “2021 to 2022,” and a third says “03/19,” you force them to interpret the format before they can evaluate the work. In a document that gets a few seconds of attention on the first pass, that's a real cost.

This section is about readability, not style preference. Mixed date formats usually do not destroy ATS parsing on their own. They do create hesitation for human reviewers, and hesitation hurts.

Use one date system across the full resume

The cleanest default is month and year for every role:

• Past roles: Jan 2023 to Dec 2024
• Current role: Jan 2023 to Present
• Role order: Most recent first

That format gives enough precision without clutter. It also removes the small credibility problems that show up when one job gets detailed dates and another gets vague ones.

Here's where candidates get into trouble. They shorten older roles to year-only, switch to numeric dates in internships, or mix abbreviations and full month names because the resume was assembled from older versions. The result feels patched together, and the timeline becomes harder to verify at a glance.

Use the same structure everywhere. If you choose month and year, keep month and year for each role. If you choose abbreviated months, abbreviate them throughout.

A resume should read like a timeline, not a formatting compromise.

If space is tight, cut bullets from older jobs before you cut date clarity. Dates do important structural work. They help the reviewer understand progression, tenure, and gaps without having to reconstruct your history manually.

4. Inconsistent Bullet Punctuation

This mistake rarely kills parsing, but it absolutely affects credibility. If some bullets end with periods, others don't, and one bullet ends with a semicolon for no clear reason, the resume feels stitched together from old versions.

The fix is boring. That's why it works.

Pick one rule and apply it everywhere

You have two clean options:

• Sentence-style bullets: End every bullet with a period.
• Phrase-style bullets: End none of them with a period.

What doesn't work is mixing both styles inside the same role, or across the document without any pattern. A common real-world example is pasting bullets from LinkedIn into a Word file and leaving the punctuation exactly as imported.

Do one final punctuation sweep before export. It takes two minutes and makes the file feel finished.

If you want an easy rule, use periods only when bullets are full sentences. Skip them when bullets are short fragments. Just stay consistent within each section.

5. Mixing Verb Tenses Within the Same Role Description

This one sounds small until you read it out loud. “Managed vendor relationships and lead quarterly planning” creates friction immediately. The reader may not know why the bullet feels off, but they notice it.

A clean rule solves almost every case.

The tense rule

• Current role: Use present tense
• Past roles: Use past tense

That means a current job might say “Lead cross-functional planning” and “Manage reporting cadence.” A previous job should say “Led cross-functional planning” and “Managed reporting cadence.”

This matters most when you update an old resume in pieces. You add a new bullet to a current role, copy a line from a past review, and end up with mixed grammar inside the same entry.

Editorial check: Read each role top to bottom and listen for tense shifts. You'll hear them faster than you'll spot them.

This mistake won't usually break an ATS. It does make a human reader trust the document less.

6. Dense Paragraphs Instead of Bullets Under Roles

Dense paragraphs fail for a simple reason. Recruiters scan resumes in seconds, and a wall of text hides the parts that matter.

This is less about style than about retrieval. A paragraph forces the reader to parse your whole thought before they find the action, scope, or result. Bullets expose those details line by line. They also give resume parsers cleaner structure to work with, especially when each bullet covers one contribution instead of four ideas crammed into one sentence.

A practical before-and-after

Bad:

Worked across finance, operations, and procurement teams to support budgeting cycles, reporting requests, vendor coordination, and several process improvement initiatives while managing deadlines across multiple stakeholders.

Better:

• Managed budgeting support across finance, operations, and procurement
• Coordinated vendor and stakeholder requests across parallel deadlines
• Improved reporting workflows for recurring planning cycles

The content is nearly the same. The format is doing the work.

A good bullet usually carries one idea: what you owned, what you changed, or what you delivered. Paragraphs blur those boundaries. Bullets make them visible fast.

There is a trade-off. A short executive summary or profile can work as a paragraph because it is read as narrative. Role descriptions should not. If you need help keeping that structure clean, a plain-text resume format that preserves readable role bullets is usually more stable than a heavily styled layout.

If your resume is running long, this is one of the first fixes to make. Converting a paragraph into bullets usually exposes filler, repeated context, and bundled tasks that should have been separated or cut.

7. Inconsistent Indentation and Alignment

Misalignment doesn't always look dramatic. Usually it shows up as small drift. One bullet sits slightly farther in. Dates don't line up from role to role. A degree entry is offset by a few spaces because it was pasted from another file.

That kind of inconsistency makes a resume feel less controlled than it should.

What to standardize

Use one alignment system and keep it all the way through:

• Bullets at the same level: Same indent
• Role blocks: Same spacing before and after
• Dates: Same placement in every role
• Section headings: Same distance from the content below

If you're doing this in Word or Google Docs, hidden tabs and manual spaces cause a lot of the mess. Plain text structure is less fragile. That's why we recommend starting from a cleaner content model, like the one described in our plain-text resume format guide.

A common real-world failure happens after export. The file looked aligned in one editor, then shifts in PDF or on another machine. If your structure depends on manual spacing, it's unstable.

8. Font Sizes Shrunk Below 10pt to Force Content Onto One Page

Tiny body text is usually a content problem disguised as a formatting choice.

Once the main text drops below 10pt, the resume gets harder to scan at exactly the point where speed matters. A recruiter is not going to slow down and work for your layout. They skip, miss context, and move on. This is one of the few formatting decisions that carries a direct cost in human readability.

The fix is not squeezing harder. The fix is deciding what earns space.

What to cut before you touch font size

Reduce content in this order:

• Older experience: Shorten earlier roles that no longer prove much for the target job
• Repeated claims: Remove summary lines or bullets that say the same thing in slightly different words
• Low-value detail: Cut tools, coursework, side projects, or task lists that do not support the job you want
• Decorative spacing: Tighten oversized section gaps and inflated heading space before shrinking readable text

A second page is often the better trade-off. A readable two-page resume beats a crowded one-page resume with compressed text every time.

This problem also tends to travel with other formatting risks. Candidates who force text down to 9pt often start compensating with narrower margins, tighter line spacing, or font choices that look slimmer on screen but hold up poorly after export. If you need a safer set of defaults, use the guidance in our ATS-friendly resume fonts guide.

One more practical point. If you are experimenting with downloaded fonts to save space, check the licensing terms too. This guide to understanding font licenses is useful if you want to verify what you are allowed to use.

Good resumes are edited, not compressed.

9. Unusual or Decorative Fonts That Don't Embed Reliably in PDFs

Font choice is not a branding exercise on a resume. It is a file reliability decision.

Decorative typefaces, downloaded fonts, unusual character sets, and custom bullet symbols can fail at the PDF stage. If the font does not embed cleanly, the recruiter may see substituted characters, broken spacing, or a layout that shifts after upload. An ATS may still extract some text, but the document the hiring team opens can look sloppy or hard to scan.

What to use instead

Use common fonts that render predictably across devices and PDF viewers. Calibri, Arial, Times New Roman, Helvetica, and Georgia are usually safe. The goal is not personality. The goal is readable text that survives export, upload, and review without changing shape.

If you want a tighter shortlist, use our ATS-friendly resume fonts guide. It covers which fonts hold up well in PDFs and which ones tend to create avoidable problems.

One practical test catches this fast. Export the resume to PDF, open it on another device, and zoom in on bullets, dates, and punctuation. If spacing shifts or characters change, switch fonts.

If you are installing a font manually, check the legal side too. This guide to understanding font licenses is useful if you want to confirm what you are allowed to use.

10. Images, Icons, or Skill Bars Standing in for Written Detail

Graphics look polished. They fail at the two jobs a resume has to do: parse cleanly and scan fast.

An ATS reads words, labels, and context. A skill bar, star rating, or icon row strips out that context. Even when the file survives upload, the meaning does not. A recruiter sees a half-filled bar for Python or Excel and still has to guess what that means in practice.

The trade-off is simple. Visual shorthand saves a few words, but it removes searchable text and weakens the evidence behind your claims. That is a bad exchange on a document that gets reviewed in seconds.

What to replace them with

Use written detail the system can extract and a human can understand quickly:

• Instead of skill bars: List the tools in plain text
• Instead of icons: Write the actual label, such as Email, Phone, and LinkedIn
• Instead of star ratings: Show where and how you used the skill

A line like “Built internal reporting dashboards in SQL and Power BI” does more work than an analytics meter ever will. It gives the reader keywords, context, and proof in one sentence.

Icons can still cause problems even when they are only decorative. Contact icons sometimes separate labels from the actual information. Skill charts often push core terms into shapes or sidebars that parse poorly. If a formatting choice makes the text less explicit, cut it.

11. No Clear Visual Hierarchy Between Company, Role, and Dates

Not every formatting issue is about ATS failure. Some make scanning harder for humans. This is one of them.

If the company name, job title, and dates all look identical, the reader has to stop and figure out the structure of each role. That's wasted effort.

A cleaner structure

Use formatting to make each role legible at a glance:

• Job title: Most prominent
• Company: Secondary
• Dates: Visible, but lighter
• Bullets: Clearly tied to that role

For software developers in particular, standard section headings such as “Work Experience,” “Education,” and “Skills” help ATS systems categorize fields correctly, as noted in Resumevera's ATS resume guidance. Creative section names like “My Journey” or “What I've Built” may read as personality to you and as noise to a parser.

A good hierarchy doesn't need fancy design. It just needs consistency, contrast, and labels a recruiter can recognize instantly.

Readers should know where you worked, what you did, and when you did it before they read a single bullet.

12. Profile Photo Headshots

In most corporate and tech hiring contexts, a profile photo on the resume adds more risk than value. It doesn't help parsing. It doesn't improve scannability. It can also make the document feel dated.

There are exceptions. Some regions and industries do expect a photo. If you're applying in a market where that's standard, follow local norms. If not, skip it.

The rule most people should follow

For most US corporate roles, leave the headshot off. The page should lead with your name, experience, and fit for the role.

The same principle applies to other decorative add-ons that act like design shortcuts. An icon-only contact row, a stylized profile badge, or a heavily visual skills block may look current, but clean text usually reads better across both human and automated review.

One adjacent point is worth calling out. You should still keep your LinkedIn photo professional, because that's where a recruiter may click next. If you want help on that side, this guide on creating compelling LinkedIn photos for leaders is about profile presentation, not resume layout.

12 Common Resume Formatting Mistakes Compared

The Common Thread Stop Fighting Your Document

The recurring problem is simple. Candidates use formatting to force a document to look right, then act surprised when the same document breaks in an ATS or slows down a recruiter.

These mistakes fall into three practical groups: parsing failures, scan friction, and cosmetic choices that add little while increasing risk. Columns, text boxes, headers, footers, images, and font issues can strip out content or scramble reading order. Mixed dates, weak hierarchy, inconsistent alignment, and dense paragraphs usually stay readable, but they make a seven-second scan harder than it needs to be. Headshots, skill bars, and decorative icons sit in a third category. They rarely help enough to justify the space or the compatibility risk.

The cost is not equal. If a phone number sits in a header or text box, the system may miss it entirely. If bullet punctuation is inconsistent, the resume still works, but it signals weak control over detail. That distinction matters. Good editing focuses on the failures that change outcomes, not the ones that only bother perfectionists.

Some older advice also needs tighter framing. “Never use columns” is too broad. Newer parsers can handle some well-built PDFs, and human readers often do benefit from cleaner visual grouping. As noted in TekCom's analysis of current resume formatting trade-offs, better parsing has changed the risk profile in some environments. The trade-off still stands. Unless you know the target system can read your layout correctly, simple structure is the safer choice.

Start by removing structural waste. Cut empty summary language. Break paragraphs into bullets. Trim older roles that no longer carry hiring value. Standardize dates, indentation, and heading styles. Then decide whether one page is the right target. For experienced candidates, two pages are often the cleaner format because they preserve readable type and clear spacing.

Intentional rule-breaking is fine when the reason is real. Some creative roles reward stronger presentation. Some countries expect a photo. Some two-column resumes pass both parser and recruiter review without trouble. The standard is straightforward: use the format because it survives the workflow, not because it looks polished on your laptop.

I see the same pattern in writing rules too. People fight the medium instead of using conventions that travel well across tools and readers. Humantext's writing style guide makes that point in a different context. Consistency reduces friction.

The broader fix is to stop treating Word or Google Docs like a page-design app. Write in a structure that is easy to parse, easy to scan, and easy to update. The design should support the content, not hide it.

Cezar came back to a resume he hadn't touched in years and was able to iterate on it fast, because the styles stayed consistent no matter what he changed in the content. [Anecdote A10]

For keyword matching, mirror the job description naturally, then keep the formatting plain enough that those terms remain readable to both systems and people. this LinkedIn post discussing ATS screening thresholds

Been putting off that resume update for years? Resumey.Pro users like Cezar fixed that in an afternoon.