11 min read
You've exported a resume that looks fine on your laptop. Workday's preview shows random symbols where bullets should be, your phone number split across two fields, and a skills table that reads like one long sentence. That's not a typo on your part, and you're not alone. The parser misread layout, fonts, or a PDF layer, and garbled text is what recruiters see unless you fix the source file.
Check your resume for free on the same export before you blame keyword density. US corporate reqs on Workday build a candidate profile on upload. When tables, headers, or image-only PDFs scramble characters, your contact block and best bullet can disappear before a human opens the attachment.
Below you'll see the bar a parse-safe file must clear, before/after pairs for the garbled text failures I see most on Workday uploads, what broken previews share, and a copy-paste header block you can use tonight. Job searching's draining. This page is about stopping qualified files from turning into nonsense in the parser.
If you've been tweaking keywords while your experience still sits inside a Word table, flip the order. Layout fixes come before tailoring. You can't keyword-stuff your way out of a file where Workday reads • instead of a bullet and maps your email into the wrong field.
Quick Wins
- Move phone and email out of Word headers into the body under your name.
- Replace skills tables with employer bullets or one vertical list.
- Export text-based PDF from Word, not a scan or design-only export.
- Swap custom bullets for hyphens, then paste into Notepad once to read order.
The bar a Workday-safe resume must clear before upload
Workday is not a PDF viewer. It extracts text into profile fields recruiters scan in list view. Losing fonts and colors is normal. Random symbols, scrambled dates, and contact soup are not.
The standard your file is judged against: a plain-text paste reads in human skim order: name and contact, summary if you use one, Experience with Month Year dates, Education, then Skills. Each employer line stays attached to its title and bullets. No • strings, no phone digits in the name field.
A composite operations coordinator whose two-column template puts Skills on the left often sees tool names parse as the first "employer." The real job title drops four rows down with garbled bullet characters between lines. Same person, same career. Different screen because layout drove parse order.
US Workday portals sometimes show a preview step after upload. I've passed on candidates when the parsed profile showed nonsense contact text even though the PDF attachment looked polished. The attachment does not always get opened first.
Read how resume file type impacts screening for the wider format story. This teardown is the garbled character layer: tables, headers, and PDF exports that break on Workday upload.
Naming Workday is allowed. Claiming how it ranks candidates is not. Stick to what you can observe: preview text, field mapping, and plain-text export order. Fix those and you stop losing screens to symbols nobody can read.
Multi-page files add risk. Page-two headers with your name and phone restart parse loops. Section breaks between Experience and Education can insert blank rows that read as gaps. Keep one continuous flow when you can. If you need page two, don't repeat contact blocks at the top.
Edge case: you're returning after a gap and used a functional-style skills block up front. Workday still reads top to bottom. Put a dated contract or consulting line before the skills list so parsers attach tools to a real employer, not a floating grid.
Before/after fixes for Workday parsing errors and garbled text
Each pair shows a layout choice, what Workday tends to do with it, and the export fix. Swap in your employers and bullets. Illustrative job titles only.
Pair 1: Finance analyst with experience in a Word table
Before: Three-column table with employer, title, and dates in separate cells. Merged rows for promotions.
After: Single column. Jan 2021 to Mar 2024 · Senior Financial Analyst · RetailCo on one line, then bullets below with standard hyphens.
Tables flatten into one run-on line or reorder cells left-to-right by row. Dates can show 2024 to 2021 beside the wrong company. Kill the grid, not the metrics.
Pair 2: Contact block trapped in header/footer
Before: Phone, email, and LinkedIn URL in a Word header on every page. Name centered in the body.
After: Name on line one, city and phone on line two, email on line three, all in the body. No header or footer content.
Headers parse early. Workday may map digits into a name field while your summary lands under Education. Recruiters see garbled contact text before bullet one.
Pair 3: Software engineer PDF from a design export
Before: Canva or similar export with icon bullets, colored sidebar, and github.com/handle in a footer. Preview shows • and blank squares.
After: 11-point Calibri single column from Word. github.com/handle on line three under email. AWS and Kubernetes inside bullets under the employer that ran production traffic.
Design PDFs often embed fonts the parser cannot map. Custom glyphs become garbage characters. Export from Word after you flatten layout.
Pair 4: Nurse resume with certification table
Before: Bordered table for ACLS, PALS, and BLS above Experience. Unit types in a second table beside hospital roles.
After: RN license and ACLS on line two under name. Each hospital role lists unit type and patient ratio in bullet one with Month Year dates.
Before: Med-surg, telemetry, 6:1 ratio; managed acute care patients.
After: Staff RN, Med-Surg/Telemetry, 32-bed unit, 6:1 ratio; precepted 4 orientees and maintained fall-rate below unit average in FY24 at County General.
Pair 5: Customer support rep with two-column template
Before: Left rail lists Zendesk, Salesforce, and CSAT metrics. Right column holds employers without tools in bullets.
After: One column. Zendesk and Salesforce named inside bullet one under the employer with Month Year dates and ticket volume in the same line.
Side rails parse first. Workday may show Zendesk as your opening "job" while your current title drops below garbled symbols. Flatten, then name tools in context.
Pair 6: Marketing manager with skills in a text box
Before: Gray shaded text box beside the name with HubSpot, GA4, and SQL in a three-column mini-table.
After: Skills as normal body text after Experience, or one line per role: Stack: HubSpot, GA4, SQL, Looker.
Floating objects parse last or drop entirely. A strong skills box may never reach the profile field recruiters skim, or it may flatten into unreadable character runs.
Pair 7: Scanned PDF resume
Before: Photo scan of a printed resume saved as PDF. OCR guesses characters on employer names and dates.
After: Retype into a single-column Word doc with selectable text. Export PDF using Save As PDF from Word, not a phone camera app.
Scanned files are the fastest path to blank pages or nonsense strings in Workday. If you cannot highlight text in the PDF, the parser cannot read it reliably either.
Pair 8: Project coordinator with wingding bullets
Before: Custom bullet font, logo watermark, dates in the left margin outside the main text flow.
After: Standard round bullets or hyphens. Month Year dates at the start of each employer line. No watermark, one column.
Before: Coordinated vendor onboarding; tracked milestones in Smartsheet.
After: Jun 2022 to Present · Project Coordinator · LogisticsCo · Coordinated vendor onboarding across 14 sites; cut milestone slippage by holding weekly Smartsheet reviews with procurement through Q1 2025.
Copy-paste Workday-safe header block
Paste this at the top of a blank Word doc and replace bracketed lines:
[Full Name]
[City, ST] · [Phone] · [[email protected]]
[Optional one-line summary with title level and scope]
Professional Experience
[Month Year] to [Month Year or Present] · [Employer] · [Title]
- [Bullet with verb, scope, tool, and outcome]
Export PDF from this file only. Open the Workday preview if the portal offers one. If characters still garble on PDF, try DOCX upload from the same source.
See DOCX export settings that improve US ATS parsing when you need export clicks that keep text selectable for Workday.
What garbled Workday previews still share
Trusting the PDF because it looks fine on your screen. Recruiters may never open it. The parsed profile already shows nonsense symbols where your bullets were.
Repeating contact info in header, footer, and body. Duplicates fight for the same fields. Pick one body block and delete the rest.
Using design templates with invisible tables. Many online resume builders hide grid lines. Workday still reads the grid and garbles row order.
Uploading a scan of a printed resume. OCR guesses characters. Employer names and dates are the first casualties.
Skipping the preview because you're applying on mobile. Wait until you can open the desktop preview once. Garbled uploads are harder to fix after submit on some reqs.
Stuffing keywords into a sidebar after a failed upload. More text in the wrong column makes parse order worse, not better. Flatten first, then tailor bullets.
Assuming every US company configures Workday the same way. Preview steps vary. Plain-text export order is the constant you control tonight.
Leaving section headers creative or cute. My Journey and Where I've Been don't map to Experience and Education in most parsers. Standard labels are boring on purpose.
Applying fixes only to page one. A clean first page with a two-column page two still scrambles the full profile. Scroll the entire doc before export.
Verify parse text before you hit submit
Run the export through the free ATS checker with the job description pasted in. You're confirming employer-title pairing and whether skills landed in Experience, not chasing a perfect score.
Then build your resume in a single-column layout if you need a clean base file before you tailor for the posting. Parse order first. Keywords second.
Stop garbled text tonight
Workday parsing errors that produce garbled text usually trace back to tables, header contact blocks, and PDF exports the parser cannot read as plain text. Flatten to one column, move contact into the body, kill floating boxes, and read a Notepad paste once before upload.
Pick the next Workday req on your list. Apply the copy-paste header block. Run a free ATS check on the same file. Open the preview if the portal shows one. Upload when employer lines stay paired with the right titles and bullets show real words, not symbol soup.
This won't turn a design portfolio into a parser-friendly file without edits. It does stop qualified candidates from losing screens because Workday turned a skills table into their fake first job while • characters replaced the bullet that proved impact.
When the portal asks for a cover letter after upload, generate a cover letter from the corrected resume text so the note matches the employer order you fixed in Word.
Read more
Frequently asked questions
Those symbols usually mean the parser misread a special character or font glyph from a PDF or Word export. Custom wingding bullets, smart quotes, and emoji icons often become nonsense text in the Workday preview. Replace decorative bullets with a standard hyphen or round bullet in 11-point Calibri or Arial, then re-export as a text-based PDF from Word.
Tables are a common trigger, not a guaranteed failure. Workday often flattens grid cells into one run-on line or reads columns out of order. A finance analyst whose dates sat in a left column may see 2020 to 2018 beside the wrong employer. Skills tables can parse as a fake first job. Flatten tables into single-column employer blocks with Month Year dates on the same line as the title.
Upload whichever format the portal accepts, then open the preview if Workday shows one. A text-based PDF exported from a single-column Word file usually parses cleanly. Scanned PDFs and Canva-style design exports often produce blank or garbled text. If the preview still scrambles employers on PDF, try DOCX from the same flattened source. Never assume the attachment you see is what the recruiter reads first.
Yes. Phone, email, and city lines in a Word header often parse before body text. Workday may stuff digits into a name field or drop your email entirely while your summary shifts below Education. Move all contact details into the body under your name on line one. Delete repeated headers and footers on pages two and three.
No. A parse-safe file does not change fit. It stops a qualified resume from dying because Workday turned your strongest bullet into random symbols or attached metrics to the wrong employer. Fix layout and export order first, then tailor keywords to the posting.