10 min read
A professional resume template ATS safe for Greenhouse is boring on purpose: one column, real text for contact info, Experience labeled exactly, and no icon font where your phone number should be. Pretty layout is not the bar. Parse order is. When hidden Word tables and decorative columns scramble field order, your last job title can land under Skills and dates detach from employers.
Check your resume for free on the PDF or DOCX you'll upload. If the checker shows jobs out of order or missing employers, the template is the problem, not your keywords. Below you'll get three failure causes, before/after layout fixes, how to tell which break is yours, and a copy-paste skeleton that's ugly and readable.
You've probably been told to pick a polished template so you look professional. That's fine for a human reading a printout. Most corporate uploads go through a parser first. You won't fix a scrambled timeline by choosing a darker header color.
Don't trust the thumbnail. Export the file, upload it to a checker, and read what the machine extracted. If Experience is empty while the PDF looks full, start stripping design layers tonight. You'll know you're done when employer names appear in the same order as your PDF without manual fixes in the portal preview.
Quick Wins
- Single column for Experience, Education, and Skills.
- Contact lines as plain text, not icon glyphs.
- Section labels: Experience, Education, Skills (not My Journey).
- Month Year dates on the same line as employer, not in a sidebar.
The symptom: professional template, scrambled Greenhouse fields
I've opened candidate PDFs in Greenhouse where the design was sharp and the parsed profile was nonsense. Job three appeared before job one. Skills repeated in the middle of a bullet. Phone number merged with a section header. That is what a professional resume template that is not ATS safe looks like inside the ATS, even when the human PDF is fine.
ATS safe does not mean plain text only. It means the parser can find employer, title, location, dates, and bullets in reading order without hitting layout traps. Design-heavy templates hide structure in tables, text boxes, and floating shapes. Parsers read character stream order, not what your eyes see.
Edge case: creative industry roles that ask for a designed PDF. Send the designed file only when requested; keep a single-column export for ATS portals. Edge case: federal resumes with rigid format rules. Follow the required template even if it uses tables; those forms are built for specific parsers.
And if a recruiter tells you the file looked fine on their screen, that does not mean the ATS import matched. Hiring managers see the attachment. Greenhouse stores a parsed record used for search and knock-out questions. Both views need to be right; start with the parse view when uploads fail silently.
Read DOCX export settings that improve US ATS parsing when Word exports look fine locally but shift in the upload preview.
Professional resume template ATS safe: three causes and fixes
Work through causes in order. Fix cause one before you blame keywords. Each pair below is a layout diagnosis, not a design contest.
Cause 1: Hidden tables and text boxes
Before: Two-column Canva layout with Experience in a bordered text box and Skills in a left rail table cell. PDF looks balanced. Greenhouse reads the left rail first and lists Photoshop between two job titles.
After: Single-column DOCX. Header block, Summary, Experience with Month Year lines, Skills last. No text boxes. Section breaks only.
Before failed reading order. After passes because jobs stay contiguous.
How to tell: select all in Word and turn on table gridlines. If Experience lives inside a cell, rebuild outside the table. Copy plain text into a new blank document with Heading 2 for section titles.
Save versions as lastname-role-ats.docx and lastname-role-print.pdf so you never upload the wrong export under deadline pressure. Name files with company, role, and your name so recruiters find the right attachment in a crowded downloads folder.
Cause 2: Icon fonts for contact lines
Before: Phone and email shown as envelope and handset icons from a icon font. Human sees symbols. Parser stores Unicode private-use characters or blanks.
After: Plain lines: name, city and state, phone, email, LinkedIn URL spelled out. 11-point Calibri. No glyphs.
Before broke contact fields. After gives strings parsers map to phone and email slots.
Cause 3: Sidebar skills and date columns
Before: Dates in a narrow right column, duties in the center, skills in a colored left sidebar. Timeline sorts by column scrape, not by job.
After: Each job as four lines: Title | Employer | City | Month Year to Month Year, then bullets underneath. Skills section after Experience.
Before detached dates from titles. After keeps each role as one parse block.
Edge case: infographic skill bars. Replace with a comma list or two-column skill table only if you accept parser risk. Edge case: header/footer contact info. Some parsers skip headers; keep contact in body line one.
Cause 4: Marketplace template metadata and locked layers
Before: Premium Word template from a marketplace with locked background shapes, sample text in hidden layers, and instructions to stay inside text boxes. You replaced sample copy but left the boxes. Greenhouse reads box order, not visual order.
After: New blank document. Paste content only. Apply Heading 2 to section titles. Use paragraph spacing for margins. No background shape layer.
Before kept invisible scaffolding. After ships only text the parser can walk sequentially.
How to tell which cause is yours
Upload to a checker. If contact is blank, suspect icons or headers. If jobs are shuffled, suspect tables or sidebars. If Skills injected mid-experience, suspect left-rail layout. If everything is empty, suspect image-only PDF export from a design tool.
Quick field-order test. Search the parsed text for your most recent employer. If it appears below Skills or inside a bullet, your template is reading sideways. Date test. If end dates show without employers, dates are in a separate column or table cell. Character test. If phone shows as squares or odd symbols, replace icon fonts with digits.
Edge case: Mac Pages export to PDF. Re-open in Word or export DOCX through a plain template before ATS upload. Edge case: resume built in design software and saved as PDF. Text may be vector outlines with no selectable characters. Rebuild in Word if select-all returns nothing.
Copy-paste ATS-safe template skeleton
Copy-paste into a blank Word doc:
[Full Name]
[City, ST] | [phone] | [email] | [linkedin.com/in/handle]
SUMMARY
[Two lines, plain text]
EXPERIENCE
[Job Title] | [Employer] | [City] | [Month Year] to [Month Year or Present]
• [Bullet with verb, metric, year]
• [Bullet]
EDUCATION
[Degree] | [School] | [Month Year]
SKILLS
[Tool], [Tool], [Method] (comma-separated, one block)
Compare against the universal US resume template when you need section order for Workday specifically.
What breaks in the parser on professional templates
JPEG skills section. Exporting resume pages as images makes text invisible to ATS. Use text PDF or DOCX.
Creative section names. My Path and Expertise Map do not map to Experience and Skills in Taleo.
Bullet symbols as graphics. Custom dash icons become missing bullets. Use standard round bullets or hyphens.
Multiple font families per line. Title in display font, employer in script. Parser may split mid-line.
Nested tables for spacing. Empty table rows used as margins reorder content in Lever. Use paragraph spacing instead.
Text boxes for summary. Summary trapped in a shape often parses last or never.
Wrong export path. Print to PDF from browser preview is not the same as Save As PDF from Word. Export from the source doc.
Edge case: academic CV templates with publications first. Corporate ATS expects Experience near the top; reorder for industry apps. Edge case: infographic one-pager. Keep a text resume sibling for uploads.
Color and shading traps. Dark background blocks behind white text sometimes fail OCR on older parsers. Light background, dark text, standard margins.
Hyperlinks only. Email as a hyperlink without visible text string can parse empty. Show the address as text and link it.
Section order drift. Certifications before Experience on a marketplace template pushes jobs down page two in the parse preview. Put Experience on page one for corporate reqs.
When structure is fixed, tune wording with your job match score on the same export. Parser order and keyword match are separate fixes. Do layout first.
This won't fix weak bullets or missing keywords. It stops a qualified file from looking empty because the template hid structure from Greenhouse.
Test the export you'll upload
Run the same file the portal accepts, then run a free ATS check with a target posting pasted in. Template fixes show up as restored employer order and intact contact lines before keyword score moves.
Starting clean? Build your resume in a single-column layout so you are not undoing hidden tables from a marketplace template.
Strip design, keep structure
A professional resume template ATS safe for corporate uploads is single column, plain contact text, standard section labels, and Month Year dates beside employers. Hidden tables and icon fonts in polished layouts scramble Greenhouse field order more often than font choice does.
Open your template source tonight. Reveal tables. Replace icons with typed phone and email. Move Skills below Experience. Export DOCX, run the checker, compare parse order to the PDF. Save the boring version as your default upload file and keep the designed PDF for humans who ask for it.
Run the same test on mobile export paths. Some phone PDF apps flatten layers into images. If select-all fails on your phone export, rebuild on desktop Word before you apply. This will not fix applying without relevant experience. It stops empty parsed profiles when the human view looked hireable.
Need a short letter for the same application? Generate a cover letter after the resume export parses cleanly so recruiters see the same titles in both files.
Read more
Frequently asked questions
Many are not when they rely on text boxes, icon fonts for contact lines, or decorative columns. The PDF looks polished to you. Greenhouse may read the left column first, merge phone and job title, or drop Skills entirely. Export a plain DOCX from a single-column Word base when the employer uses an ATS upload. Use design-heavy layouts only when the employer asks for a portfolio PDF or states they read files manually.
Rarely for corporate ATS. A narrow sidebar for contact details sometimes parses if the main column holds Experience in plain paragraphs. Most parsers read left to right across the full page width, so sidebar skills land between job bullets. If you must use two columns, put every date and employer in the wide column only. Run a parse check on the exact export before you trust it.
Word DOCX with built-in Heading styles and no nested tables is the safer default for Workday and Greenhouse. Google Docs exports can add extra spacing codes that shift bullet order. Either works if the structure is single column, standard section labels, and Month Year dates on their own lines. The template brand matters less than whether tables and icons are hidden under the design.
Arial, Calibri, Cambria, Georgia, Helvetica, and Times New Roman at 10.5 to 12 point body text. Avoid icon fonts that draw envelopes and phones as single glyphs. Avoid custom script fonts for section headers. Parsers map plain characters to fields. Icons become blank squares or garbage strings that break contact parsing.