Resume Special Characters ATS: Which Unicode Symbols Break Parsing

Resume parsers tokenize characters before they classify skills, dates, or headings. A unicode glyph that looks harmless in Word can split into multiple bytes during PDF extraction and change the searchable text. The practitioner rule is to trust the extracted output, not the visual preview.

Workday usually normalizes common punctuation to ASCII, so a plain-text PDF often survives with minimal damage. Taleo and older parser chains can turn an em dash into mojibake such as `â€"` while iCIMS behavior changes with the parser vendor a company enabled. The safe operating rule is to remove any symbol that changes after extraction.

The first failures usually come from long punctuation. An em dash, curly apostrophe, or curly double quote may render beautifully but arrive as broken bytes in downstream extraction, which is why em dash resume ats and curly quotes resume ats complaints cluster around older enterprise systems. The practical fix is to replace them with a standard hyphen and straight quotes before export.

Decorative bullets, arrows, check marks, and degree symbols create a different problem because they often replace actual words or separators. A special characters cv parser can either drop them entirely or fuse them into adjacent text, which makes a skills list or certification line harder to search. The safe fallback is plain round bullets, commas, and words such as `to` or `through` instead of symbols.

Greenhouse handles unicode well when the upload is a text-based PDF or DOCX created in Word. That strength disappears when the PDF is image-heavy or the font layer is broken, because Greenhouse still depends on clean text extraction before it can index content. The rule is to separate platform capability from document quality.

iCIMS is the least predictable because implementations vary across healthcare, retail, and government environments. One employer may normalize accented characters cleanly, while another strips the same line or moves the symbol into the wrong field. The decision rule is to assume inconsistency until your own extract proves otherwise.

The safest character set is plain ASCII punctuation with real words carrying the meaning. Use hyphens instead of long dashes, straight quotes instead of smart quotes, and standard bullets instead of diamonds or check marks. That rule keeps the parsed text stable across Workday, Taleo, Greenhouse, and iCIMS.

Run the final file through ProfileOps ATS Checker after every export because the same resume can behave differently as DOCX and PDF. If the tool shows corrupted symbols, replace them at the source rather than hoping the recruiter sees the intended formatting. Testing the exact submission file is the only defensible rule.

The most common mistake is treating every unicode character as equally safe because the PDF opens correctly. Parsing engines do not fail on appearance; they fail on encoding, font mapping, and reading order. The operating principle is to remove risk where it adds no search value.

The second mistake is fixing decorative icons while leaving smart punctuation everywhere else. That leaves the resume vulnerable to resume special characters ats failures in section lines, degree notations, and skill lists that recruiters search directly. The cleaner rule is to standardize the entire file, then validate once.