7 Ways to Test Your Resume for ATS Parsing (Workday, Greenhouse, Lever)

I see it all the time. A job seeker with perfect skills and experience applies to dozens of roles and gets nothing but silence. They blame the market, or their background. But nine times out of ten, the problem is simpler. Their resume got mangled by the Applicant Tracking System before a human ever saw it.

You might think a clean PDF is enough. It’s not. These systems, like Workday and Greenhouse, parse your document, pulling data into rigid fields. If your formatting confuses the parser, your "Expert in Python" becomes "Expert in" and "Python" lands in a random notes section. Your five years of experience vanish. You’re out of the running before the race starts.

The good news? You can test for this. You don’t need to guess. Here’s a practical framework to validate your resume against the quirks of major ATS platforms.

Key Takeaways

• The biggest ATS risk isn't keyword stuffing, it's formatting that breaks the parser. Simple, single-column resumes with standard headings parse best.
• You can simulate an ATS parsing test for free using basic tools like text pasting, PDF-to-Word conversion, and a careful review of job application previews.
• Workday, Greenhouse, and Lever each have unique quirks. Knowing them lets you proactively format your resume to survive the upload.
• Your testing isn't a one-time job. You need a repeatable workflow to check every new resume version and application.

Why ATS Parsing Fails (It’s Not What You Think)

People obsess over keywords. That matters, but it's secondary. The primary gate is parsing. If the ATS can't correctly read your job titles, companies, and dates, no amount of keyword optimization will help.

Think of the parser as a very literal, somewhat clumsy robot. It looks for patterns. A line with dates in it? Probably a job entry. A bolded phrase at the start of a line? Could be a section header. When you use complex layouts, tables, text boxes, or fancy icons, the robot gets lost. It starts putting your address in the "Skills" field or merging two jobs into one.

I reviewed a resume last month that used a two-column layout with a sidebar for skills. In the ATS preview, all those skills were appended to the end of the professional summary, making it a jumbled, unreadable block. The candidate’s core strengths were completely hidden.

Your Pre-Test Checklist: The Foundation

Before you even start testing, get your resume into a parsing-friendly state. This solves 80% of problems.

1. Use a Single-Column Format. This is non-negotiable. Sidebars, multiple columns, and complex grids confuse parsers. Stick to a top-to-bottom flow.
2. Choose Standard, Clear Section Headings. Use "Work Experience," "Education," "Skills," "Projects." Avoid cute titles like "My Journey" or "Where I've Been."
3. Ditch Tables and Text Boxes. Use them for visual layout, and the parser will choke. Use tabs, spaces, or simple line breaks to align dates if you must, but a left-aligned date on the same line as the job title is safest.
4. Stick to Common Fonts. Use Arial, Calibri, Georgia, Helvetica, or Times New Roman. Uncommon fonts may default to something else, breaking spacing.
5. Save as a .docx File for Upload. While PDFs are often accepted, a Word document (.docx) is the native format most parsers are built to handle. Have a clean PDF for direct emails, but use the .docx for ATS portals.

A tool like Career Dog is built for this. Its templates are designed to be ATS-friendly from the start, giving you a clean, professional single-column format without you having to worry about the underlying code. You can focus on content, not debugging layout.

The 7-Point ATS Parsing Validation Framework

This is your action plan. You don't need expensive software. You need methodical scrutiny.

Test 1: The "Plain Text Paste" Stress Test

This is the quickest, most revealing check. Open Notepad (Windows) or TextEdit (Mac, in plain text mode). Copy your entire resume and paste it in.

What you're looking for:

• Is the logical order of information preserved? Do your jobs still appear in reverse-chronological order?
• Do your section headers stand out (e.g., are they on their own line)?
• Has any text become garbled or merged? Special characters (bullets, arrows, icons) often turn into question marks or boxes.

Action: If the pasted text is a mess, your formatting is too complex. Simplify.

Test 2: The PDF-to-Word Conversion Check

If you have a PDF resume (maybe from a designer), open it in Adobe Acrobat or use a free online converter to turn it into a Word document. Now, open that converted .docx file.

What you're looking for:

• Has the conversion created text boxes or images of text? (Click on text. If it selects as a whole block or image, it's bad.)
• Are lines and spacing wildly different?
• This simulates what an ATS parser does when it receives your PDF. If the conversion is poor, the parsing will be worse.

Test 3: The Workday Simulation

Workday is ubiquitous in large enterprises. It's also notoriously rigid. It expects a very clean, predictable structure.

Quirks to know:

• It heavily relies on dates to identify work entries. Ensure each job has clear start and end months/years.
• It can struggle with hyphenated company names or titles with multiple slashes.
• The "summary" or "profile" section at the top can sometimes get truncated if it's too long.

Simulation Test: When you apply on a Workday portal, pay close attention to the preview screen after you upload your resume. Workday will show you how it parsed your data into its fields ("Resume Details"). Go field by field. Is your current title in the "Most Recent Job Title" field? Are all your past employers listed correctly? This is your golden ticket to see Workday's own parser in action. If it's wrong here, it's wrong for the recruiter.

Test 4: The Greenhouse Simulation

Greenhouse is popular with tech and mid-size companies. It's generally a better parser than Workday, but it has its own habits.

Quirks to know:

• It's good at pulling skills from a dedicated "Skills" section. List them clearly.
• It can sometimes pull the company name and job title from the same line if not formatted perfectly.

Simulation Test: Similar to Workday, Greenhouse often provides a parsed preview. Look for a "Review and Submit" step. Check how it categorized your experience. Also, Greenhouse allows some companies to add custom questions. While not a parsing test, a clean application here is a good sign your format is sound.

Test 5: The Lever & Other System Check

Lever, Ashby, and similar modern ATS are often more forgiving. They still parse, but they might handle slightly more complex layouts.

General Rule: The principles for Workday and Greenhouse will keep you safe here. Focus on clean data separation: one company/role/date set per clearly separated block.

Test 6: The "Keyword Readiness" Scan

Once you're confident the structure is parsed, then think about keywords.

• Open the job description and the pasted plain text version of your resume side-by-side.
• Identify 5-8 hard skills and core tools from the description (e.g., "Project Management," "SQL," "Agile Scrum").
• Can you find each one clearly in your plain text resume? If a keyword is buried in a table or text box that didn't survive the paste test, the ATS won't see it either.

Test 7: The Human Readability Finale

Pass the final, parsed-through-an-ATS version to a friend. Give them the plain text file from Test 1. Ask them to tell you:

• What your most recent job is.
• What your top three skills are.
• How many years of experience you have.

If they can answer instantly, you've won. The ATS and the human recruiter (who often skims a parsed view) will get it too.

Building Your Testing Workflow

Don't do this once. Build it into your process.

1. Create a Master Resume File. This is your perfectly formatted, ATS-optimized .docx. This is your source of truth.
2. Customize for a Job. From your master, tailor content for a specific role.
3. Run the Gauntlet. Before hitting "submit," do the Plain Text Paste (Test 1) and a quick visual scan for any new formatting you introduced.
4. Learn from Previews. Every time you apply and see an ATS preview (Workday, Greenhouse), study it. Note what worked and what didn't. Adjust your master file accordingly.

Common Red Flags and Quick Fixes

• Problem: Dates are missing or parsed into the job description. Fix: Put dates on the same line as the job title and company, right-aligned. Format: Month YYYY - Month YYYY.
• Problem: Skills section is merged into another paragraph. Fix: Put "Skills" on its own line. List skills with bullet points or pipe separators (e.g., Python | SQL | Data Analysis | A/B Testing).
• Problem: Company name and job title are combined into one field. Fix: Use a clear line break or put the title on the line directly below the company name, bolded.
• Problem: Your name and contact info are split up. Fix: Keep it all at the very top, on 1-3 simple lines. No icons for phone or email.

What to Do When You Can't Test a Specific System

You won't always know if a company uses Lever or iCIMS. That's okay. By adhering to the foundation and running your own pre-flight tests, you create a resume that is system-agnostic. It's built to survive. The goal isn't to pass a specific test for every single ATS, but to create a document so clean and standard that any reasonable parser will handle it well.

The Bottom Line

Treat your resume like a data transfer, not just a document. Your goal is to transmit your career data from your screen into the ATS database with 100% fidelity. The fanciest design in the world is worthless if it drops half the data along the way.

Start with the plain text paste test today. It takes two minutes and will tell you more than any online scanner. Simplify relentlessly. Use the application previews as free, real-world parsing reports. Your response rate isn't a mystery. It's often a formatting issue you have the power to fix.

Build your resume with ATS as the first audience, not the last. A platform like Career Dog enforces this mindset, providing templates where the parsing is already considered. Then, you can apply this validation framework with confidence, knowing your foundation is solid. Stop guessing and start testing.