How to Use Hyphens and Dashes on US Resumes

10 min read

You did not miss a keyword. You pasted a bullet with a long dash character and the parser read everything after it as a new field. The human sees one line about revenue. Workday shows half a sentence in Skills and the rest orphaned below. That's fixable in one editing pass if you know which characters to hunt.

Hyphens join words. En dashes and em dashes are typography for print, not for upload boxes. And that minus sign your template inserted from a symbol menu is a third character that looks identical on screen but fails token matching.

Check your resume for free after you run a punctuation scrub. You are looking for broken lines, not keyword density.

Below: the direct answer on which character to use where, exceptions for phone numbers, before-and-after fixes, and a copy-paste find list. No typography lecture. Just what to change before tonight's application batch.

Job searching already asks you to rewrite bullets for every posting. Punctuation scrub is the low-effort layer that prevents silent parse drops. You are not dumbing the file down. You are choosing characters parsers were built to read.

Why dash type matters more than font choice

Parsers tokenize on punctuation. A hyphen-minus keeps client-facing as one token when the posting uses the same spelling. A long dash character often inserts a hard break. The second half of your bullet becomes noise.

Recruiters skim plain text previews in Greenhouse and Lever. When dates wrap oddly or job titles split across lines, they assume formatting sloppiness before they reach bullet one.

Word and Google Docs auto-correct double hyphens into en or em dash characters. That helps essays. It hurts resume exports. Turn off smart punctuation before your final pass.

Hyphen-minus is ASCII code 45. En dash and em dash live in unicode space your eyes cannot distinguish at small sizes. Minus sign U+2212 is a third lookalike from equation editors. Each can split tokens differently depending on vendor.

Taleo and older iCIMS builds were especially brittle on non-ASCII punctuation. Greenhouse and Lever improved, but plain text previews still show the damage when you paste from a designed PDF.

For spacing rules that pair with punctuation, see the best resume section spacing for readability . Fix section gaps and dash characters in the same editing session.

Edge case: academic CV habits bleed into corporate resumes. CVs tolerate wider typography. US corporate uploads want boring ASCII. Edge case: multilingual files where names include legitimate hyphens. Keep those hyphens; do not let auto-format widen them into dash characters.

How to use hyphens and dashes safely on US resumes

Use the keyboard hyphen for compounds the job posting repeats. Use the word to for date ranges when you want zero ambiguity. Reserve bullets for periods, not decorative breaks.

Compounds and job titles

Before: full time analyst with client facing reports pasted from a template with nonbreaking hyphens.
After: full-time analyst with client-facing reports using ASCII hyphen-minus only.

Before: Senior Developer [long dash character] Java/Python in the title line.
After: Senior Developer: Java/Python or Senior Developer, Java/Python. Colons and commas parse predictably.

Employment dates

Before: March 2019 [en dash character] August 2023 copied from a Canva resume.
After: March 2019 to August 2023 or March 2019-August 2023 with plain hyphen and Month Year labels.

Edge case: contract roles labeled Client Name via Agency. Use commas, not dashes, between entities. Edge case: overlapping part-time roles. Put each employer on its own row with honest Month Year ranges instead of joining two jobs with a slash and a dash.

Bullets that currently use long dashes

Before: Cut ticket backlog 22% [long dash character] rebuilt triage workflow in Zendesk.
After: Cut ticket backlog 22%. Rebuilt triage workflow in Zendesk.

I've opened Workday text exports where every bullet after a long dash landed under Skills. The candidate looked keyword-stuffed in the wrong section because punctuation re-sorted the file.

{`FIND (replace with safe ASCII)
- Long dash inside bullets -> period + space + capital letter
- En dash in dates -> " to " or plain hyphen with Month Year
- Unicode minus U+2212 -> keyboard hyphen-minus
- Nonbreaking hyphen in compounds -> normal hyphen-minus

KEEP
- full-time, part-time, cross-functional, self-starter (posting terms)
- 555-123-4567 phone format
- Req IDs with hyphens when the posting uses them

VERIFY
- Paste into Notepad: no blank squares or odd width characters
- Re-upload preview in portal or run HireFlow parse check`}
              

For Month Year rules that pair with date lines, read resume dates format Month Year vs numeric ATS tips .

Skills lines and certification labels

Postings often hyphenate terms you should mirror exactly. When the req says hands-on, keep the hyphen. When it says machine learning as two words, do not invent a hyphen. Copy the posting spelling into bullets, not only into Skills.

Before: AWS Certified Solutions Architect (Associate) with en dash separators copied from a badge graphic.
After: AWS Certified Solutions Architect, Associate, with commas and ASCII only.

Vendor badges pasted as images bypass text parsers entirely. Type the certification name in plain text beside any logo you keep for human readers.

Export paths that reintroduce bad characters

Google Docs to PDF usually preserves ASCII when smart quotes are off. Canva and slide-deck exports often embed unicode dashes even when the on-screen preview looks normal. Word to PDF on Mac with smart dashes enabled is a common failure mode for otherwise strong candidates.

Print to PDF from the browser preview is unreliable for layout. Prefer Save As PDF from Word with embed fonts disabled when the portal accepts DOCX. When PDF is mandatory, open the PDF in a text extractor or run a parse preview to see what tokens survive.

Bullets across roles and industries

Operations resumes love stacked clauses separated by long breaks. Marketing resumes paste campaign names with special characters from brand guides. Engineering resumes list languages with slashes that are fine, but dashes between title and stack are not.

Before: Grew pipeline 18% [long break] owned Salesforce hygiene and weekly forecast calls.
After: Grew pipeline 18%. Owned Salesforce hygiene and weekly forecast calls.

Healthcare and finance candidates often inherit template language with compliance labels. Keep the label, drop the decorative dash between label and description. Auditors read PDFs; parsers read text exports first.

Remote work compounds often appear as hybrid-remote or fully-remote in postings. Mirror the hyphenation the req uses. Do not invent hybrid remote without the hyphen when the posting hyphenated the term.

Security clearance lines sometimes include slash-separated levels. Slashes are fine on US keyboards. Problems start when clearance labels are joined to dates with long dash characters copied from clearance badge PDFs.

Education blocks tempt en dash ranges for graduation years. Prefer Graduated May 2020 or Class of 2020 without a range character when you only need one year. Ranges belong on employment, not every credential line.

Volunteer sections follow the same rules as paid roles. Month Year to Present with ASCII hyphens only. Volunteers often paste brochure copy with stylized punctuation; strip it before upload.

Characters that quietly break US uploads

Mixing three dash types in one section. Headers use en dash dates, bullets use long breaks, Skills use unicode minus. Exports look fine in PDF; plain text is a mess.

Spaces around hyphens in compounds. full - time reads as two tokens. full-time reads as one.

Using dashes as bullet glyphs. Custom square bullets paste as odd unicode. Stick to standard round bullets from Word outline.

Before: Designed two-column PDF with smart quotes and dash ornaments.
After: Single-column DOCX, smart punctuation off, ASCII scrub, then PDF export for upload if the portal requires PDF.

This will not fix missing required skills. It stops qualified files from shedding half a bullet because of one wrong character.

Recruiters rarely call out punctuation in feedback. They say the file felt messy. Fixing dashes is a silent upgrade that shows up as intact lines in the preview pane next to cleaner competitors.

Build a personal banned-character list from your last parse export. If client-facing split into client on one line and facing in Skills, you found the smoking gun. Fix the source DOCX, not the PDF alone.

Table layouts in Word sometimes insert vertical bar characters that look like pipes but are not ASCII 124. Those bars split columns in ugly ways in text exports. Single column removes the need for decorative separators between title and company.

International candidates exporting from non-US keyboard layouts should switch input locale to US English for the final scrub pass. OS-level autocorrect differs by locale even when the resume language is English.

Headers with pipe separators between title and company fail for the same reason as dash splits when the pipe is a special character. Use a comma or line break instead of decorative separators in the contact block.

Summary sections copied from online profile exports often import long dash characters because the profile editor uses rich text. Retype the summary in plain Word rather than pasting directly from a rich-text profile box.

Scan the file after punctuation cleanup

Upload the scrubbed export to HireFlow's free ATS resume checker with a target posting. Confirm compound terms stayed intact and section order survived export.

Rebuilding from scratch? Build your resume in a single-column layout so the next PDF pass does not reintroduce smart dashes.

When you need a letter that matches the cleaned file, generate a cover letter in plain text so punctuation stays ASCII there too.

Pair punctuation cleanup with a keyword pass only after characters are stable. Running match scores on a file that still splits tokens gives false gaps. Scrub first, score second, apply once.

Keep a version label in the filename after scrub: Lastname-Resume-ASCII.docx. When you revert to an old Canva export by mistake, the label reminds you which file is upload-safe.

Scrub dashes tonight

How to use hyphens and dashes safely on US resumes comes down to ASCII discipline. Compounds on keyboard hyphens, dates as Month Year to Present, bullets without long break characters, phone numbers with plain hyphens.

Schedule a quarterly scrub even when you are not actively applying. Templates reintroduce smart punctuation when collaborators edit your master file. Five minutes in find-and-replace beats a silent parse fail on a role you really wanted.

Teach collaborators the same rules when they help rewrite bullets. A well-meaning friend adding stylish dashes for readability can undo your ASCII pass overnight.

• Turn off smart punctuation in Word or Docs.
• Run the find-and-fix checklist on Experience and Skills.
• Paste into Notepad to spot odd characters.
• Parse-check before the next upload batch.
• Save an ASCII-labeled master copy separate from designed exports.

Open your latest export. Run a free ATS check and confirm full-time still reads as one token. If it splits, walk backward to the DOCX source and replace the character at that spot before you re-export.