Special Characters on Your Resume: Which Ones Break ATS and Which Are Safe

special characters changes parsing because ATS systems rebuild paragraphs and sections from line breaks, not from design intention. Workday, Greenhouse, and Taleo usually handle ordinary settings like standard hyphens, round bullets, and plain punctuation well, but the phrase resume symbols ats safe turns risky when the export pushes bullets, dates, or URLs into the same visual line. That is why a clean-looking file can still create a messy extract.

The parser notices dense layout first. In ATS Preview, I keep seeing files that use decorative Unicode bullets, stars, and checkmarks that replace plain text turn experience bullets into one wall of text, which makes employer names and date ranges harder to isolate. The problem is not style preference; it is that the system loses the markers it uses to tell one field from the next.

Human readers feel the same friction even when the file technically uploads. A resume with standard hyphens, round bullets, and plain punctuation and standard section gaps lets Greenhouse or Lever keep Experience, Skills, and Education separate, while a compressed layout forces recruiters to re-read basic structure. Good formatting reduces friction for both the parser and the person. The moment the extracted lines stop matching the visible page, that formatting choice has already become too risky to keep.

resume special characters ats problems usually show up as merged bullets, chopped sections, or unstable reading order. A Word file that uses decorative Unicode bullets, stars, and checkmarks that replace plain text can export to PDF with the dates wrapped onto the next line, which weakens chronology and makes the phrase ats resume bullet characters harder to trust. Small layout tweaks create surprisingly large extraction changes.

Spacing mistakes often hide inside template defaults. I see resumes with one section set to standard hyphens, round bullets, and plain punctuation and another set to symbols that render as boxes or wrap awkwardly in export, which makes the raw output alternate between readable lines and compressed fragments. The phrase special characters resume parsing loses value when the parser cannot tell where one bullet ends and the next one starts.

The failure feels random until you compare the extract with the page. Greenhouse and Taleo both surface this clearly: the visual resume looks balanced, but the parsed version merges the location, the title, and the first metric into one block. That is why testing beats guessing. A little extra white space is cheaper than a resume whose dates, links, or bullets no longer stay attached to the right fields.

The correct format keeps structure obvious without wasting space. Start with standard hyphens, round bullets, and plain punctuation, keep headings on their own line, and let bullets breathe enough that dates, tools, and metrics such as a clean bullet or title line without broken symbols stay attached to the right role. The phrase resume em dash ats only works when the parser can see where one idea ends and the next one begins.

You do not need exaggerated whitespace to be readable. The better move is predictable spacing that makes Skills, Experience, and Education look like separate zones in both Word and PDF, which is where the phrase unicode resume ats problems becomes useful. Recruiters notice the same clarity the ATS benefits from.

Consistency matters more than the exact decimal setting. A resume that uses the same spacing rule across every section usually parses better than a file that mixes custom line-height values, manual blank lines, and table-driven alignment. One stable rule is easier to trust. I treat stable extraction as the rule and visual density as the tradeoff, not the other way around.

Start the check with the section most likely to break. If the article topic is special characters, inspect the top of Experience, the contact block, and the first link because those areas reveal merge problems first. /ats-checker tells you whether structure is hurting the score, while /ats-preview shows the exact line breaks the parser extracted.

Look for field relationships rather than isolated words. If the title moved away from the date, or the URL wrapped into the next bullet, the setting is still too risky even when every word exists somewhere in the extract. I trust clean adjacency more than raw presence.

A final pass should compare the tested PDF and tested DOCX if you use both. Sometimes the Word file handles standard hyphens, round bullets, and plain punctuation cleanly while the PDF compresses a heading or widens a bullet unexpectedly, so the safest submission is the version whose extract mirrors the visible structure more closely.

The first mistake is compressing the page until sections lose shape. People often shrink special characters to fit one page, but that move can merge bullets, dates, and URLs into lines the parser cannot separate cleanly. The extra space is cheaper than a broken extract.

The second mistake is using manual formatting hacks instead of consistent document settings. Multiple return keys, invisible tables, and custom line values may solve one visual issue in Word and create three parsing issues in PDF. Stable formatting beats clever patches.

The third mistake is checking only the visual file. A PDF can look polished and still convert decorative Unicode bullets, stars, and checkmarks that replace plain text into text that Greenhouse or Taleo reads badly. Always inspect the extracted version before you hit submit.