A hyphenated name on a resume breaks ATS parsing when tokenizers treat the dash as a field separator—assigning one segment to first name and another to last name, or dropping part of the surname entirely—so you must format the name on one plain-text line and manually verify every application field after autofill.
This is not a rare edge case. Compound surnames, maiden-name combinations, and Hispanic double surnames are common in the US workforce. The U.S. Equal Employment Opportunity Commission has long recognized that hiring systems must not disadvantage applicants based on name characteristics tied to national origin. Yet parser design still lags legal and cultural reality. This guide explains why splits happen, how Workday, Greenhouse, and Taleo behave differently, and the formatting fixes that keep your identity intact.
| What you see after upload | Typical parser cause | Fix |
|---|---|---|
| First name = Lopez, last name = Garcia | Hyphen treated as space between tokens | Manual last-name field = Lopez-Garcia |
| Last name blank or truncated | Name only in Word header/footer | Move full name to resume body top |
| Two last-name fields partially filled | Legacy Taleo multi-field name layout | Repeat full surname in primary last-name box |
| Preferred name wrong, legal name right | Greenhouse optional preferred-name mapping | Set preferred name explicitly after upload |
Key Takeaways
- Never remove the hyphen to please a parser—fix fields manually instead
- Put your full legal name on one line in the resume body
- Verify first, last, and preferred name after every autofill
- Use standard ASCII hyphens, not en dashes or em dashes
- Run copy-paste and PDF search tests before you upload
Why ATS parsers split or drop hyphenated names
Resume parsers are not reading your name the way a human does. They tokenize lines of text into words using rules built for Anglo-style given name plus single-token surname patterns. A hyphen looks like punctuation between two tokens—similar to how parsers mishandle phone numbers with dashes, as covered in our guide on why ATS cannot read phone numbers .
The importer often runs before a human sees your file. Workday maps extracted tokens into structured candidate-profile fields. Greenhouse attaches the PDF but still parses contact blocks for search. Taleo and iCIMS variants used by large enterprises may expose separate first, middle, and last name boxes that autofill independently—each with its own failure mode.
According to SHRM's coverage of AI and hiring technology , employers remain responsible for ensuring automated systems do not produce discriminatory outcomes—even when the root cause is a parsing bug rather than intentional bias. That does not help you in the moment of application, which is why verification steps below matter.
Canva and design-tool resumes often render names as curved text objects. Parsers cannot extract those layers as searchable text—your hyphenated surname disappears even though it looks perfect on screen. Export a text-based PDF from Word or Google Docs for applications, and keep the designed version for networking only.
Common Mistake: assuming a correct PDF preview means correct structured data—recruiters often see parsed fields before they open your attachment.
How Workday, Greenhouse, and Taleo handle hyphenated surnames differently
Workday
Workday's candidate-profile importer runs early in the application flow. It extracts the top lines of your resume and guesses which tokens belong in first versus last name fields. Hyphenated surnames frequently land split across both fields. The importer may also cache the first parse—re-uploading a fixed resume does not always refresh name fields unless you clear them manually. See Workday resume autofill wrong fields for the full autofill verification workflow.
Greenhouse
Greenhouse is more forgiving for keyword search because recruiters often read the attached PDF directly. Parsing still matters for contact exports and CRM sync. Optional preferred-name fields can diverge from legal name if autofill maps only part of your hyphenated surname. Always set preferred name explicitly when you use a shortened professional name.
Taleo and iCIMS
Older Taleo implementations sometimes present multiple surname fields or character limits that truncate Lopez-Garcia to Lopez. iCIMS enterprise clients may run custom field mappings that strip hyphens entirely. Enterprise configurations vary—two banks on Taleo can behave differently on the same resume file.
Quick Check: after upload, screenshot your name fields—if a recruiter disputes identity later, you have proof you submitted the correct legal spelling.
First name / last name field traps on US application forms
Application forms ask for structured identity data even when the resume already contains your name. Common traps:
- Single last-name character limit: truncates compound surnames—paste the full string and watch for silent cutoff.
- Legal vs preferred name split: legal name must match I-9; preferred name is what recruiters greet you with—both need correct spelling.
- Middle name field absorbing surname segment: Maria / Lopez / Garcia instead of Maria / blank / Lopez-Garcia.
- Suffix fields (Jr., III): parsers attach suffix to last name or drop it— use the dedicated suffix box when available.
- Previous employer name mismatch: background checks compare application name to payroll records—consistency beats parser convenience.
Federal and contractor roles through USAJOBS use structured resume builders with separate name components. Mirror your legal hyphenated surname in the last-name box even if the builder suggests splitting at the hyphen.
Pro Tip: if a form offers "other name used" or maiden name, list prior surnames there rather than deleting hyphen segments from your current legal name.
Maiden names, double surnames, and suffix parsing edge cases
Not every compound surname uses a hyphen. Space-separated double surnames (Ana Martinez Rodriguez), maiden-name combinations (Sarah Johnson-Smith), and patronymic patterns all stress the same tokenizers. Parsers often keep only the final token as last name—dropping Martinez from Martinez Rodriguez.
Apostrophe names (D'Angelo, O'Connor) can lose the apostrophe or split at the quote character on legacy systems. Accented characters (José, François) may normalize to unaccented ASCII or render as replacement characters if the PDF embeds non-standard fonts. Unicode normalization is inconsistent across ATS vendors—plain ASCII hyphens and unaccented spellings parse more reliably, but only use them if they match your legal documents or you have legally adopted that spelling.
Generational suffixes (Jr., Sr., III) belong in dedicated suffix fields—not appended to the last-name box with a comma unless the form instructs that format. ADP Recruiting and SuccessFactors instances used by mid-market employers follow similar rules with separate suffix metadata.
Common Mistake: switching between hyphenated and non-hyphenated spellings across applications—background vendors flag inconsistent identity data as a verification delay.
Before/after name formatting fixes that survive parsers
These patterns fix most hyphenated-name parsing failures without altering your legal identity.
Before (header only): Name in Word header on every page; body starts with Summary
After (body line): Elena Ruiz-Mendoza | [email protected] | (555) 987-6543 as first lines of main text
Before (line break): Elena Ruiz-
Mendoza
After (single line): Elena Ruiz-Mendoza on one unbroken line
Before (styled dash): Elena Ruiz–Mendoza with en dash from Word autoformat
After (ASCII hyphen): Elena Ruiz-Mendoza with standard hyphen-minus character
Layout still matters. Two-column templates that place contact info in a sidebar can cause the parser to read your name after job titles. Single-column, top-of-body contact blocks parse most reliably—same rule as Workday resume format guidance for 2026 .
Key Takeaway: one plain-text name line in the body beats a beautifully designed header recruiters never see because parsing failed first.
Copy-paste and search tests for hyphenated names
- Copy-paste test: select all resume text, paste into Notepad or TextEdit plain mode—confirm your full hyphenated name appears on one line near the top.
- PDF search test: open the PDF and Ctrl/Cmd+F your complete surname including the hyphen—if search fails, the text may be an image layer.
- Hyphen character test: paste the name into a hex or character viewer if available, or retype the hyphen manually to eliminate en-dash autoformat.
- Upload dry run: when possible, start an application and stop before submit—verify autofill name fields.
- ATS checker: run formatting diagnostics that flag header-only contact blocks and parsing risk.
Mid-article check: upload your resume to HireFlow's ATS resume checker to catch layout issues that hide your name from extractors—not just keyword gaps.
Quick Check: if copy-paste shows your name after your Skills section, parsers will too—reorder before uploading.
Keep hyphenated names consistent across LinkedIn, payroll, and applications
Recruiters cross-check application data against LinkedIn and prior employment verifications. If your resume says Lopez-Garcia but LinkedIn says Lopez Garcia without the hyphen, screening teams may pause for identity confirmation—not because of bias, but because mismatch signals a data entry error or incomplete profile merge.
Align spelling with your Social Security card, state ID, and most recent W-2. Payroll systems at large employers using ADP or Workday HCM will reproduce whatever spelling HR entered at hire—changing hyphenation later requires HR intervention.
Email addresses that embed only part of a compound surname (elena.ruiz@) are fine, but the display name on applications should still show the full legal surname. Some calendar and scheduling tools strip hyphens when generating interview invites—confirm the invite shows your correct name before the interview.
When an employer uses both a resume upload and a separate HRIS onboarding system, name data may sync twice—once from the ATS import and again from your first-day paperwork. Mismatches between those systems delay badge printing and email account creation. Use identical spelling on the application, resume, and I-9 form even if one system suggests a shortcut.
Pro Tip: add a one-line note in the application comments field only when the form truncated your surname—most enterprise ATS do not show free-text comments to parsers, so this is for human reviewers, not a parsing fix.
Pre-submit checklist for hyphenated-name applications
- Full legal name on one line at top of resume body.
- Standard ASCII hyphen between surname parts.
- Copy-paste test shows name before work history.
- PDF search finds complete hyphenated surname.
- After autofill: first name, last name, suffix, and preferred name verified.
- Spelling matches LinkedIn and government ID.
- Email display name uses correct legal surname.
- Screenshot saved if the portal truncates a field.
Common Mistake: clicking Submit while the last-name field still shows only the segment after the hyphen—fix manually every time.
Before and after (ATS-safe wording)
Key Takeaway: keep the same fact, add the tool name and a number.
| Before | After |
|---|---|
| Responsible for reports and team support. | Built weekly Workday headcount reports that cut manager follow-ups by 30%. |
| Used office software and helped customers. | Processed 40+ Greenhouse tickets/week in Zendesk with 96% CSAT. |
| Improved processes across the department. | Mapped the Taleo requisition workflow and cut time-to-post from 5 days to 2. |
Catch parsing issues before recruiters do
HireFlow's ATS checker flags contact blocks trapped in headers, layout order problems, and other formatting failures that split hyphenated names during autofill.
Run free ATS check →Frequently asked questions
Most US ATS platforms treat the hyphen as a word separator or field delimiter. Parsers assign text before the hyphen to the first-name field and text after to the last-name field—or drop the segment entirely. Workday's candidate-profile importer and Greenhouse's resume parser both rely on pattern rules that predate common double-surname formats.
No. Removing the hyphen misrepresents your legal name and can create mismatches with background checks, payroll, and I-9 verification. Instead, format the resume for parser readability and manually correct application fields after upload. Use the same spelling everywhere—including LinkedIn and prior employer records.
Place your full legal name on one line at the top of the body text: Maria Lopez-Garcia. Do not put your name only in a Word header or footer. Avoid splitting the surname across lines with a manual line break at the hyphen. Keep the hyphen as a standard ASCII character, not an en dash or em dash.
Not consistently. Workday's autofill from resume often maps hyphenated surnames into wrong first or last name fields because the importer guesses token boundaries. You must review every name field after upload—even when the resume preview looks correct on screen.
Space-separated double surnames (Maria Lopez Garcia) can still confuse parsers that assume the final token is the only last name. Put the full surname string in the last-name application field when the form allows, and repeat the complete name on the resume header line.
Yes. Apostrophes (O'Brien), accents (José), periods in suffixes (Jr.), and non-Latin scripts often fail on older Taleo and iCIMS instances. The same manual verification rule applies: never trust autofill for contact and identity fields.
No. All caps does not change how tokenizers split on hyphens. It may reduce readability for recruiters and can cause email systems to reject addresses that were uppercased incorrectly. Use standard title case for your name line.
Copy-paste your resume into a plain text editor and confirm the full name appears on one line. Search your PDF for the complete hyphenated string with Ctrl/Cmd+F. Upload to a test application if possible, then verify first name, last name, and preferred name fields before clicking submit.