The Plain-Text Test: How to See What ATS Robots Actually Read from Your Resume

You spent hours on that resume. The layout is clean, the typography is sharp, and the color accents make your name pop. You feel confident sending it out. But what if I told you that to the first and most critical reader—an Applicant Tracking System—your masterpiece might look like digital alphabet soup?

It's a harsh truth, but a necessary one. These systems don't see beauty. They read code and extract text, often clumsily. A misplaced text box, a fancy header, or even the wrong file format can scramble your information. The result? A qualified candidate gets filtered out before a human ever glances at their carefully chosen font.

So how do you know if your resume will survive the journey from your inbox to the recruiter's desk? There's a simple, free, and incredibly revealing test you can run in under two minutes. I call it the Plain-Text Export Diagnostic. It shows you exactly what the ATS parsing engine sees.

Let's get into it.

Key Takeaways

• The Plain-Text Export Diagnostic is a crucial compatibility check anyone can perform for free.
• It reveals hidden formatting errors like jumbled sections, lost contact info, and garbled bullet points.
• Fixing these parsing issues often requires simplifying your design and sticking to ATS-friendly resume builders.
• Regularly testing your resume this way is as important as proofreading it for typos.

Why Your Gorgeous Resume Might Be a Digital Mess

First, a quick reality check. Most mid-to-large companies use some form of ATS to manage the flood of applications. One survey from a major job site found that over 90% of Fortune 500 companies rely on them. Their primary job is to sort, rank, and filter.

To do that, the software must first parse, or "read," your document. It tries to identify chunks of text and assign them to categories: name, phone, skills, job titles, companies, dates. It's not a perfect science. Complex formatting, graphics, and unconventional layouts act like obstacles on its reading path.

Think of it like this: you're handing a beautifully handwritten, calligraphic letter to someone who only reads standard typewritten text. They'll struggle. They might miss words written in the margins or misread ornate letters. The ATS is that literal-minded reader.

Your goal isn't to "beat" the system with keyword stuffing. It's to make your information so clear and accessible that the system can understand it effortlessly. That's where the diagnostic comes in.

Step-by-Step: How to Run the Plain-Text Diagnostic

This isn't complicated. You don't need special software. Here's how to do it with the resume file you plan to send out, whether it's a .docx or a PDF.

1. Open Your Resume File Open your resume in whatever program you used to create it (Microsoft Word, Google Docs, Apple Pages, a design tool like Canva or Illustrator).

2. "Save As" or Export to Plain Text (.txt) This is the key step. You're converting your formatted document into the most basic, no-frills text format possible.

• In Microsoft Word: Go to File > Save As. Choose the location, and in the "Save as type" dropdown, select "Plain Text (*.txt)". Click Save. A file conversion dialog may pop up; just click OK.
• In Google Docs: Go to File > Download > Plain Text (.txt).
• In Apple Pages: Go to File > Export To > Plain Text....
• For PDFs: Open the PDF in Adobe Acrobat Reader. Go to File > Save As Other > Text (Plain). If you don't have Acrobat, you can copy-paste all text into a basic text editor like Notepad (Windows) or TextEdit (in Plain Text mode on Mac).

3. Open and Analyze the .txt File Now, open that newly created .txt file. Use a simple text editor like Notepad (Windows) or TextEdit (set to Plain Text mode on Mac). Do not open it in Word or another rich-text editor, as it might try to reformat things. You want to see the raw, stripped-down output.

4. Critically Review What You See This is the diagnostic moment. You are now looking at a rough approximation of what the ATS extracted. Scrutinize it.

The Red Flags: What to Look For in Your Plain-Text Output

When you open that .txt file, don't panic if it looks ugly. Plain text is supposed to be plain. You're not judging aesthetics; you're checking for data integrity and logical flow. Here are the critical problems to spot.

1. Contact Information Chaos

This is the most common and damaging failure. Your name, phone, email, and LinkedIn URL must be immediately clear at the top.

• The Problem: In your .txt file, your contact info is scattered, repeated, or buried under other text. Maybe your city and state are on a different line than your name, or your email appears halfway down the page.
• Why It Matters: If the ATS can't cleanly identify "John Smith" and "john.smith@email.com" as belonging to the same person and being contact info, your entire profile can be corrupted or rejected from the start.

2. Section Header Confusion

Your clear headings like "Professional Experience," "Skills," and "Education" should be obvious.

• The Problem: The headers are missing entirely, mashed into the first line of a paragraph, or replaced with gibberish symbols (like "···" or "??"). This often happens with custom graphic headers or special bullet characters.
• Why It Matters: The ATS uses these headers to map your data. No clear "Skills" header means the software might not properly catalog your keywords. No "Experience" header could lead it to miss your job history altogether.

3. Bullet Point Breakdown

Your achievement bullets are the heart of your resume. They need to stay intact.

• The Problem: Bullets turn into random characters (like "•" or "÷"), or they disappear, causing all your sentences to run together into a giant, hard-to-read paragraph.
• Why It Matters: This destroys readability for both the system and the human recruiter who might see the parsed version. It also makes it impossible for the ATS to distinguish between separate achievements.

4. Text Box and Column Catastrophe

You used a sidebar for your skills or a text box for a quote? Beware.

• The Problem: The text from boxes and columns often gets dumped at the very top or very bottom of the .txt file, completely out of sequence. Your "Technical Skills" section might appear above your name.
• Why It Matters: Context is lost. Your Python and SQL skills, now listed before your name, are no longer associated with the "Skills" section. The ATS's mapping is thrown off.

5. Date Disarray

Dates are crucial for tracking your career timeline.

• The Problem: "June 2023 - Present" might become "June2023Present" or "06/2023-now".
• Why It Matters: Inconsistent date parsing can make it seem like you have employment gaps or can confuse the system's timeline analysis.

A Real-World Before-and-After Example

Let's make this concrete. Imagine a graphic designer's original resume snippet:

Original Formatted Resume (Looks Great):

JANE DOE Designer | jane.doe@portfolio.com | (555) 123-4567

PROFESSIONAL EXPERIENCE Senior Visual Designer | BrightMinds Co. | Jan 2021 – Present • Led a 4-person design team to overhaul the company's main SaaS dashboard, improving user engagement by 40%. • Created a scalable design system in Figma that reduced prototype development time by 25%.

Now, let's see a bad plain-text export (what a poor ATS parse might see):

JANE DOE
Designer
jane.doe@portfolio.com
(555) 123-4567

??PROFESSIONAL EXPERIENCE??
Senior Visual Designer BrightMinds Co. Jan 2021 – Present
• Led a 4-person design team to overhaul the company's main SaaS dashboard, improving user engagement by 40%. • Created a scalable design system in Figma that reduced prototype development time by 25%.

What's wrong here?

1. The header has weird symbols (??).
2. The bullet points are odd characters (•).
3. More critically, the two bullet points have run together into one block of text.

A good, clean plain-text export should look like this:

JANE DOE
Designer
jane.doe@portfolio.com
(555) 123-4567

PROFESSIONAL EXPERIENCE

Senior Visual Designer, BrightMinds Co., Jan 2021 - Present
* Led a 4-person design team to overhaul the company's main SaaS dashboard, improving user engagement by 40%.
* Created a scalable design system in Figma that reduced prototype development time by 25%.

This version is simple, clear, and perfectly readable. Every piece of information is on its own logical line. The bullets are simple asterisks (*). This is what you're aiming for.

How to Fix the Problems You Find

Once you've diagnosed the issues, it's time to repair your resume. Here are the most effective fixes.

1. Simplify Your Formatting

• Use Standard Headers: Stick to common, simple section titles: "Work Experience," "Skills," "Education," "Projects."
• Use Basic Bullets: The humble hyphen (-) or asterisk (*) is your safest bet. Avoid custom icon fonts or graphic bullets.
• Avoid Text Boxes, Sidebars, and Columns Entirely. Use a single-column, top-to-bottom flow. This is the most ATS-friendly structure.
• Keep Tables Simple: If you use a table for skills, test it. Often, table text gets extracted out of order. A simple list is usually safer.

2. Choose the Right File Format

• .docx (Microsoft Word) is generally the most reliably parsed format by ATS systems. It's the safe default.
• PDFs can be fine, but only if they are "text-based" and not "image-based." If your PDF is a scan or saved as an image, the ATS cannot read it at all. When saving as a PDF, ensure you select the option that "preserves document formatting and embeds fonts." A tool like career.dog will always generate text-based, ATS-friendly PDFs.
• Never submit .pages, .odt, or image files (.jpg, .png).

3. Use an ATS-Optimized Resume Builder This is the simplest path to peace of mind. A good resume builder is designed with ATS parsing as a core requirement, not an afterthought. For instance, career.dog creates resumes using clean, semantic HTML under the hood that exports to perfectly parsed text. The templates are built to be attractive to humans but simple and logical for machines. You get the visual appeal without the compatibility gamble.

4. Manual Cleanup in a Text Editor For a quick fix, you can copy the cleaned-up text from your diagnostic .txt file and paste it into the "Notes" or "Paste Resume" field many job applications have. This ensures the raw text they parse is exactly what you intend. But this is a workaround, not a solution for your primary document.

When Should You Run This Test?

Make it a habit.

• Before sending any important application.
• Every time you make a significant update to your resume's content or layout.
• If you're using a new template or design tool for the first time.

Think of it as the final proofread for the most important reader of all.

The Bottom Line for Designers and Creatives

I know this advice can feel stifling. As a creative professional, your visual sense is part of your skillset. You want your resume to reflect that. The compromise isn't to abandon design entirely; it's to prioritize clarity and compatibility.

Use a clean, elegant template with plenty of white space. Let your content—your achievements, skills, and projects—be the star. Use a subtle color for headings if you must, but always ensure the text has high contrast. Your portfolio, personal website, and LinkedIn profile are the perfect places to unleash your full visual creativity.

Your resume has one core job: to get you an interview. The plain-text diagnostic is your way of ensuring it can do that job in the digital age. It takes two minutes. It costs nothing. And it might just be the reason your next application lands in the "yes" pile, not the digital void.

So go ahead. Save that beautiful resume as a .txt file right now. See what the robot sees. Then, make it crystal clear.