Why Your ATS Isn’t Reading Your Resume Correctly: How to Test and Fix Parsing Errors
Diagnose resume parsing errors in ATS job applications: text layers, column order, missing dates, autofill, PDF versus DOCX, and practical verification tools.
Contents
- What an applicant tracking system actually does
- Three separate stages that people often confuse
- The five-gate diagnosis: what to check first
- Gate 1: Does the job portal accept the file?
- Gate 2: Does the PDF contain real, selectable text?
- Gate 3: Is the extracted text in a meaningful order?
- Gate 4: Can the system interpret the fields?
- Gate 5: Is the resume relevant to the role?
- ATS symptom checker: problem, likely cause, and first repair
- A repeatable test using two versions of your resume
- Prepare an original and a simplified version
- Illustrative example: all the words are there, but their meaning is lost
- Keep a small verification record
- What an ATS-friendly design actually looks like
- Design feature versus safer alternative
- PDF versus DOCX: which should you send in the US or UK?
- Resume versus CV: a US–UK terminology difference
- Multilingual resumes: names, dates, and text direction
- Use job-description keywords without keyword stuffing
- A worked example: fictional data analyst vacancy
- Missing keyword or missing qualification?
- A clear resume structure for people and machines
- A simple plain-text example
- A practical workflow with Horus Valley tools
- Step 1: Build a cleaner draft
- Step 2: Inspect the embedded PDF text
- Step 3: Compare two exports
- Step 4: Verify the application's populated fields
- What does an “ATS match score” really mean?
- An honest self-audit, without a fake acceptance percentage
- How the role and country affect your resume
- Software engineering, analytics, and other technical roles
- Finance, operations, administration, and accounting
- Applications in the United States
- Applications in the United Kingdom
- Academic or research roles
- Mistakes people make after repairing their resume
- A realistic 30-minute first-pass repair plan
- Sources, evidence limits, and what this guide does not claim
- Final takeaway: make the resume legible, truthful, and specific

Your resume can look excellent on screen and still produce a baffling job application: your employer appears in the job-title field, a past position has lost its dates, or the form asks for qualifications that are plainly visible in your PDF. That is a resume-parsing problem, not proof that you are unqualified for the role. Before buying an “ATS-approved” template or adding more keywords, find out whether the problem lies in the file, the extracted text, the interpretation of that text, or the job requirements themselves.
This guide gives you a repeatable way to troubleshoot those different failure points. You will learn how to inspect a PDF, compare two versions of a resume, interpret a job portal's autofilled fields, and make sensible format choices for US and UK applications. It also explains what a generic ATS score cannot tell you. The examples below are instructional illustrations, not claimed test results from Workday, Greenhouse, Lever, or any other proprietary applicant tracking system.
What an applicant tracking system actually does
An applicant tracking system (ATS) helps an employer manage job advertisements, applications, candidate records, hiring workflows, and associated documents. Some systems offer resume parsing: they attempt to extract names, contact information, work history, education, and other details from an uploaded file. Other functionality may include recruiter search, application questions, screening rules, or skills-matching features. These are not the same operation.
Workday's documentation on resume parsing explicitly notes that results can vary with resume formatting and word order. Greenhouse's support article likewise explains why a document may upload yet fail to populate candidate fields. Neither fact means that every employer uses the same scoring algorithm or automatically rejects a resume with an unusual layout.
Three separate stages that people often confuse
| Stage | What the system may do | Sign that something went wrong | What you can check yourself |
|---|---|---|---|
| Text extraction | Read characters from a PDF or DOCX | Missing passages or garbled symbols | Select and copy text, or extract the PDF to TXT |
| Resume parsing | Associate words with contact details, roles, employers, and dates | Dates appear under the wrong employer | Review the job portal's autofilled fields |
| Matching and selection | Apply employer criteria, screening questions, and recruitment decisions | The file parses but the application does not progress | Check eligibility and evidence against the posting |
- Extraction: Can the system read actual characters from the file, rather than merely display the page as an image?
- Parsing: Can it correctly associate those characters with fields such as job title, employer, dates, degree, and skills?
- Evaluation: Does the completed application satisfy the employer's requirements, including work eligibility, experience, qualifications, and answers to screening questions?
A document can pass extraction and fail parsing. It can pass both and still be a poor match for the vacancy. Conversely, a formatting problem does not automatically establish why a recruiter has not contacted you. Fix the stage that is failing, instead of treating every rejection as an ATS design problem.
The five-gate diagnosis: what to check first
Gate 1: Does the job portal accept the file?
Read the employer's upload instructions before changing your design. Check whether it accepts PDF, DOCX, or other formats, whether there is a file-size limit, and whether a separate form must be completed. A file that exceeds a portal limit may not upload at all. A file that uploads successfully may nevertheless be difficult to parse.
A particularly instructive example comes from Greenhouse. Its supported-upload documentation says candidate attachments can be up to 100 MB, but its resume-parsing troubleshooting guidance says the parser cannot parse resumes larger than 2.5 MB. Upload acceptance and successful parsing are distinct limits. That is a Greenhouse-specific example, not a universal maximum for all ATS products.
If your file is unexpectedly large, check for embedded photographs, oversized graphics, or scanned pages before applying aggressive compression. Reducing file size must not turn selectable text into a blurry image. Keep your editable source document so you can export a smaller clean version when necessary.
Gate 2: Does the PDF contain real, selectable text?
Open your PDF, try selecting a job title and a few lines of work history, then copy them into a plain-text editor. If you cannot select the words at all, your PDF may consist of page images or a flattened scan. Some employers' technologies may use OCR, but you should not rely on every workflow to recover an image-only resume correctly.
You can also use Horus Valley's PDF to Text tool to inspect the embedded text of the exact PDF you plan to submit. It works with selectable text rather than providing optical character recognition for scanned images. If the output is empty, that is a prompt to investigate your export; it does not prove that all hiring systems will fail on the file.
Gate 3: Is the extracted text in a meaningful order?
A two-column layout may be readable to a person but extract as fragments: a skill from the sidebar, half a job description, a date from the opposite column, and then the employer's name. This is a different defect from a missing text layer. A parser might encounter all the words yet have trouble pairing them.
Read the extracted text from top to bottom. For each position, make sure the job title, employer, employment dates, and achievements remain together. Check whether your name and contact details appear before the experience section. If the order is inconsistent, create a one-column version and compare the output rather than rewriting the entire resume immediately.
Gate 4: Can the system interpret the fields?
Even orderly text can be ambiguous. The headings “Selected Adventures” or “Where I Made a Difference” may make perfect sense to you but provide fewer cues than Professional Experience, Education, and Skills. A date such as 2021–23 may also be less helpful than a consistent Jan 2021 – Dec 2023 format. Specify job titles and organizations clearly and avoid putting a phone number only inside an icon or image.
Keep essential contact information in the document's body, not solely in a Word header, footer, or floating text box. Greenhouse names those areas among potential causes of parsing problems, and the US Department of Labor's CareerOneStop resume guide recommends standard headings and avoiding heavily formatted layouts.
If the portal shows an autofilled application preview, correct that preview. It is stronger evidence of the particular portal's behavior than a generic online checker, although correcting visible fields does not reveal the employer's entire selection process.
Gate 5: Is the resume relevant to the role?
Once the file and fields are in order, stop blaming the layout for every unsuccessful application. Compare the vacancy with your genuine qualifications. You may be missing a required credential, a specific type of experience, employment authorization, or a portfolio example. There may simply be stronger candidates. None of those issues is resolved by switching from Arial to Calibri or buying an “ATS 100%” template.
ATS symptom checker: problem, likely cause, and first repair
| What you observe | Possible explanation, not a certain diagnosis | First action | What to check next |
|---|---|---|---|
| The PDF displays text but nothing is selectable | Scanned image or flattened export | Export a text-based PDF from the original document | Check extraction again; consider a permitted DOCX alternative |
| All words extract but appear out of sequence | Columns, floating items, or layout order | Move to a single-column design | Inspect each job's employer, title, and dates |
| Your telephone number is missing from autofill | Number inside a graphic, text box, header, or poorly recognized format | Write it as ordinary body text | Edit portal fields manually where permitted |
| Some characters become symbols | Font encoding, export, or extraction issue | Export using a common font and retest | Try an allowed alternative format |
| Dates are attached to the wrong employer | Field boundaries or timeline formatting unclear | Standardize role, organization, and date order | Inspect the portal's populated work-history fields |
| Your resume parses but you receive no interview | Fit, experience, eligibility, competition, or hiring decisions | Review job requirements and honest evidence | Do not assume a hidden formatting rejection |
| A third-party checker returns “42% ATS match” | Proprietary checklist or keyword score | Examine precisely what is being measured | Avoid treating the number as an acceptance probability |
This table is a troubleshooting aid, not the output of a benchmark of specific commercial parsers. Modern systems vary and may successfully read some layouts that older tools struggle with.
A repeatable test using two versions of your resume
You can examine basic extraction problems without paying for an ATS simulator. The goal is to test the integrity and order of the text in your own file; it is not to reproduce an employer's screening algorithm.
Prepare an original and a simplified version
- Save a copy of your existing resume. Do not overwrite the original.
- Create a second document with the same factual content, arranged in one column without decorative sidebars or floating text boxes.
- Export both as text-based PDFs if the source software supports it. Use DOCX when required by the vacancy.
- Extract the text from each PDF using PDF to Text on Horus Valley or a trusted local reader. If your privacy or workplace rules prohibit using a web interface, use appropriate offline software.
- Paste the two outputs into the Horus Valley Text Diff Checker to examine added, missing, and reordered lines. Whitespace and line-break changes can produce apparent differences even when the words are still present.
- Inspect the same five categories in both outputs: contact information, each job title, employer name, date range, and relevant skills.
- In a genuine application where the portal provides a review step, inspect the fields it populated and correct them before submission. Do not submit fake applications just to probe a hiring system.
Illustrative example: all the words are there, but their meaning is lost
Imagine a fictional candidate, Alex Morgan, whose entry should read: Data Analyst — Example Analytics Ltd — March 2022 to August 2025 — SQL, Power BI, Excel. A two-column export might extract: Alex Morgan — SQL — Data Analyst — Power BI — Example Analytics Ltd — Excel — March 2022 to August 2025.
Almost every term remains, but the ordering makes it harder to tell which text describes a role and which belongs in the skills section. In a one-column version, the job and dates stay together, followed by a clearly labeled skills section. This is a constructed demonstration, not a real parser trial. An advanced parser might handle both documents, and a simple text extractor might behave differently from the eventual employer's tool.
Keep a small verification record
| Field to verify | In the original document | In the extracted text | Result |
|---|---|---|---|
| Full name | At the top as text | Complete and readable? | Pass / revise |
| Email and phone | Plain characters | Copied without changes? | Pass / revise |
| Job title and employer | Clearly grouped | Still grouped correctly? | Pass / revise |
| Employment dates | Month and year for each role | Linked to the correct role? | Pass / revise |
| Relevant skills | Listed truthfully in context | Complete and searchable? | Pass / revise |
| Portfolio links | Visible URL or meaningful link text | Destination and label still understandable? | Pass / revise |
Retain the checklist with your application documents. Once all the items pass, focus on the content and vacancy fit rather than endlessly regenerating your PDF.
What an ATS-friendly design actually looks like
An ATS-friendly resume does not have to be ugly. Use consistent spacing, readable type, descriptive headings, short accomplishment bullets, and modest emphasis. Bold job titles can help a human reviewer scan the page. A restrained color accent is not automatically disqualifying; what matters is whether the information survives when visual decoration is ignored.
The University of Minnesota Duluth's ATS guidance recommends standard headings, familiar fonts, and avoiding columns, tables, pictures, and text boxes. Such advice reduces risk; it does not prove that every application system fails on every two-column resume.
Design feature versus safer alternative
| Design element | Why it can cause trouble | Simpler alternative |
|---|---|---|
| Skills in a narrow sidebar | Text may be extracted among experience entries | Separate Skills section below the profile |
| Email icon with no visible address | No literal email address to extract | Print the full email address |
| Circular “90% proficiency” chart | The skill may be represented as graphics, not text | Name the skill and describe its use |
| Floating text boxes | Text order may change or content may disappear | Ordinary document paragraphs |
| Photos or logos inside experience entries | Little benefit to field extraction | Text job titles and employers |
| Unusual decorative font | Export or recognition may be inconsistent | Arial, Calibri, Georgia, or another readable font |
| White text repeating the job advert | Manipulative and unrelated to demonstrable experience | Relevant, accurate achievements in context |
If you are applying for design work, a visual portfolio can demonstrate craft without requiring the resume itself to contain complex page furniture. Follow the employer's submission instructions for any supplementary portfolio or work samples.
PDF versus DOCX: which should you send in the US or UK?
Follow the employer's requested format first. There is no sound universal rule that a PDF always beats DOCX or vice versa. A real-text PDF often preserves appearance across devices, while DOCX is easier to edit and may work better in some workflows. A scanned PDF, on the other hand, is a weak default when a text-based document is possible.
| Situation | Practical choice | Check before submitting |
|---|---|---|
| The posting explicitly requires DOCX | DOCX | Opens correctly; dates and fields are clear |
| The posting explicitly requires PDF | Text-based PDF | Text can be selected and copied |
| Both formats are accepted | The version the portal previews accurately | Compare contact details, dates, and jobs |
| The PDF is a scanned image | Re-export from an editable source | Do not rely on unspecified OCR support |
| The resume mixes languages | Test both the display and extracted order | Verify names, dates, punctuation, and links |
A second Greenhouse distinction illustrates why vendor-specific advice matters. The MyGreenhouse candidate guidance recommends PDF for its candidate experience but also tells applicants to review and correct parsed fields. Other portals may have different preferences. Always prioritize the directions on the actual application page.
Resume versus CV: a US–UK terminology difference
In most US private-sector applications, a resume is a targeted professional summary. In the UK, CV is the usual label for a similar job-application document. In US academia, however, a curriculum vitae can be a substantially longer record of research, publications, teaching, and professional activity. Do not shorten an academic CV to one page solely to satisfy a generic ATS myth; first check the hiring institution's instructions and the role's expectations.
The same principle applies to a UK academic CV, a graduate scheme application, or a public-sector form with prescribed sections. A system's inability to populate one field does not override the employer's stated submission requirements.
Multilingual resumes: names, dates, and text direction
For most US and UK applications, write the document in the language requested in the advert. Candidates with multilingual experience may still need to include non-English employer names, certifications, technical terms, or publications. Mixed writing systems can create directionality or encoding problems when copied from a PDF, particularly when left-to-right English appears alongside right-to-left scripts such as Arabic.
- Keep paragraphs in a consistent language and direction where practical.
- Put employer names and dates on predictable lines rather than distributing them through multiple floating elements.
- Preserve the official spelling of an organization, and include an accurate English rendering only when it clarifies identity.
- Spell out less familiar abbreviations on first use, such as
Enterprise Resource Planning (ERP), if relevant. - Copy one mixed-language line from the exported PDF into plain text and look for reordered digits, brackets, or punctuation.
- When you genuinely need separate Arabic and English applications, maintain separate readable versions rather than an overloaded bilingual layout.
A successful local copy-and-paste test is useful but does not certify how any particular platform handles international scripts. Review the employer's own autofill preview if available.
Use job-description keywords without keyword stuffing
Keywords matter when they describe real skills and experience, but an indiscriminate list of software names is not evidence of competence. Start with the employer's essential criteria and distinguish those from preferred qualifications. Map each genuine skill to a project, responsibility, or result. This gives both software and human readers meaningful context.
A worked example: fictional data analyst vacancy
Suppose a posting asks for SQL, Power BI, reporting automation, stakeholder communication, and experience with data quality. The examples in the final column are sample wording to use only if they accurately describe work you performed.
| Vacancy requirement | What honest evidence looks like | Illustrative accomplishment wording |
|---|---|---|
| SQL | Queries that join, filter, or summarize data | “Built SQL queries for the weekly sales reporting workflow.” |
| Power BI | Dashboards used by a team | “Developed Power BI dashboards for regional performance reviews.” |
| Data quality | Validation, cleaning, or anomaly checks | “Added validation checks to identify duplicate customer records.” |
| Reporting automation | An automated workflow you maintained | “Automated recurring report preparation with documented steps.” |
| Stakeholder communication | Clear collaboration with nontechnical teams | “Explained reporting definitions to sales and operations colleagues.” |
These are hypothetical examples, not achievements attributed to a real candidate. Where you have reliable records, an actual result can strengthen a bullet: “Reduced weekly reporting preparation from two hours to 45 minutes.” Do not copy a quantified claim unless that change occurred and you can substantiate it.
Missing keyword or missing qualification?
Those are different issues. If you have used an alternative business-intelligence tool but not Power BI, explain that experience honestly; do not claim proficiency with Power BI because the advert lists it. The employer might value transferable skills, or may insist on the named software. Likewise, no change in resume formatting can substitute for a required professional license or legal work authorization.
The UC Davis Career Center's resume guidance focuses on writing targeted accomplishments and selecting relevant evidence. That approach is more defensible than trying to inflate a machine-generated percentage by repeating words from the vacancy.
A clear resume structure for people and machines
There is no single mandatory sequence for every profession, but a predictable layout usually makes the document easier to inspect. Experienced applicants often put relevant experience first; recent graduates may place education and substantial projects earlier.
- Name and contact: Full name, professional email, usable phone number, location at an appropriate level of detail, and relevant professional profile or portfolio link.
- Headline and summary: A concise description of your role, experience, and specialization rather than a list of unsupported adjectives.
- Professional experience: Reverse chronological where suitable, with job title, employer, month/year dates, and evidence-based accomplishment bullets.
- Skills: Specific tools, methods, languages, and competencies that you genuinely have and that relate to the job.
- Education and credentials: Institution, qualification, and relevant credentials in a consistent format.
- Selected projects: State the project's purpose, your own contribution, technologies used, and outcomes that can be verified.
A two-page resume can be appropriate for a relevant, substantial career. A one-page document with tiny text and missing evidence is not automatically better. Length alone is not a universal automated hiring threshold.
A simple plain-text example
The following layout is illustrative, not a file submitted to a real ATS:
ALEX MORGAN — DATA ANALYST
London, UK · alex.morgan@example.com · +44 20 0000 0000 · portfolio.example.com
Professional Summary: Data analyst with experience preparing operational reports, checking data quality, and explaining dashboards to business teams.
Professional Experience — Data Analyst, Example Analytics Ltd — Mar 2022 to Aug 2025
- Prepared recurring reports using SQL and spreadsheets.
- Created dashboard views for operational stakeholders.
- Documented validation steps used in monthly data reviews.
Skills: SQL, Power BI, Excel, data validation, reporting.
Education: BSc in a relevant discipline, Example University.
Use real details instead of this fictional identity. The purpose of the example is to keep headings, contact data, and work history as explicit, searchable text.
A practical workflow with Horus Valley tools
Horus Valley offers useful preparation tools, but none should be described as an official ATS emulator or a guarantee of passing a specific employer's system.
Step 1: Build a cleaner draft
Open the Horus Valley CV / Resume Builder. Enter a full name, job title, email address, phone number, summary, experience, education, and skills. The tool provides a preview and a print/save-as-PDF workflow. It can help produce a straightforward draft, but the exported document still needs checking on your device.
Step 2: Inspect the embedded PDF text
Use PDF to Text on the actual final exported file. Read the extracted output in sequence, looking particularly at company names, job dates, and email addresses. The tool's published description specifies browser-local processing and extraction of existing text, not OCR. For confidential resumes, observe any workplace policies and make your own decision about which software you trust with personal details.
Step 3: Compare two exports
Place the output of your initial layout alongside the simplified version in the Text Diff Checker. Look for missing job titles, truncated entries, or rearranged lines. The checker compares text by lines; differences in spacing and wrapping alone are not proof that information was lost.
Step 4: Verify the application's populated fields
Where the hiring portal allows editing, review employment history, qualifications, name, phone, location, and answers to screening questions before you click submit. This portal-specific check is more relevant than a third-party score, although it still cannot reveal every decision factor used by recruiters.
Do not upload multiple fake applications just to experiment with a system. Keep one verified master resume and tailor factual details to real opportunities.
What does an “ATS match score” really mean?
Services that advertise 72%, 85%, or 98% ATS compatibility may be computing a proprietary checklist: term overlap with a job posting, section-label patterns, number of relevant phrases, or other internal rules. Such a result can identify text worth reviewing. It is not a probability of receiving an interview, nor a score that all employers calculate in the same way.
Before relying on a score, ask: Does the tool distinguish must-have skills from preferences? Does it understand whether a skill appears only in a course or in five years of work? Does it separate extraction quality from qualifications? Does it support the applicant's language? Has its score been independently validated against the hiring system you are actually using? If the answers are unclear, treat it as an editorial checklist—not an acceptance forecast.
An honest self-audit, without a fake acceptance percentage
| Audit area | Practical standard | Record your result |
|---|---|---|
| File compatibility | Allowed format and size for this posting | Yes / No |
| Real text layer | Name and experience can be selected and copied | Yes / No |
| Order and grouping | Each role stays with its employer and dates | Yes / No |
| Field clarity | Standard section labels and plain contact details | Yes / No |
| Evidence and fit | Statements support the genuine job requirements | Yes / No / Requirement missing |
| Portal review | Autofilled fields match your original information | Yes / No / Not available |
Do not add up these six answers into an arbitrary hiring percentage. One missing mandatory qualification may outweigh all the formatting improvements you make.
How the role and country affect your resume
Software engineering, analytics, and other technical roles
Name the technologies you actually used and link to demonstrable work when relevant. Show how you applied SQL, Python, cloud tooling, or another requested skill. A decorative “five-star JavaScript” graphic says less than a short project description with a real outcome. Do not imply familiarity with every tool in a long job advert.
Finance, operations, administration, and accounting
Give concrete examples of processes, systems, reports, and responsibilities: month-end reconciliations, purchase orders, ERP workflows, client communication, audit support, or budget reporting. Explain scale or improvements only if you can support the numbers. Use recognized job titles without falsifying historical titles.
Applications in the United States
Follow the specific posting and avoid adding unrelated sensitive personal details. For many mainstream private-sector resumes, a headshot is not needed and can complicate extraction. Where a job requires work authorization or a license, answer the designated application questions accurately rather than trying to conceal a missing requirement in your resume.
Applications in the United Kingdom
The job-application document is usually called a CV. Keep the same emphasis on clarity, relevant achievements, and standard headings, and follow the employer's file format and application questions. UK public-sector applications, graduate schemes, and competency-based hiring processes may require a separate statement or evidence against published criteria; a perfectly parsed CV is not a substitute for those materials.
Academic or research roles
A research CV may legitimately be much longer and include publications, grants, conferences, teaching, professional appointments, and supervision. Use clear section headings and comply with institutional instructions. The short corporate resume template is not universally suitable for academic recruitment.
Mistakes people make after repairing their resume
Editing after the last check: A resume may parse well, but the applicant adds a new sidebar and submits the altered file without retesting. Always inspect the final version, not the one you tested yesterday.
Trusting appearance alone: Being able to see a date in a PDF viewer does not guarantee the underlying characters are extracted in the correct sequence. Verify both the text and the portal's fields.
Copying the entire job advertisement: It does not establish competence and can make the resume tedious to read. Use truthful, context-rich examples instead.
Flattening the resume into an image: Locking the appearance by removing selectable text sacrifices usability and may impair accessible reading and parsing. Export from an editable source whenever possible.
Hiding contact details behind symbols: A phone or envelope pictogram is not a substitute for a readable number or address in body text.
Renaming old jobs to match the advert: Changing a historical title can create inconsistencies with references and records. You can explain equivalent responsibilities without inventing the formal job title.
Ignoring screening questions: Required professional registrations, work eligibility, location constraints, or employer-specific questions may influence the application independently of how successfully the resume is parsed.
A realistic 30-minute first-pass repair plan
This is a suggested time budget for a resume whose factual content is already prepared, not a promise that every document can be repaired in 30 minutes.
- Minutes 0–5: Read the job posting, allowed file format, and non-negotiable criteria.
- Minutes 5–10: Copy or extract the text of your actual submission file. Find missing information or garbled characters.
- Minutes 10–17: Replace problematic columns or floating boxes with normal paragraphs; move contact details into the document body; make dates consistent.
- Minutes 17–24: Compare your truthful experience with the job's essentials. Clarify vague accomplishments and remove irrelevant filler.
- Minutes 24–30: Export the requested format, repeat the text check, and review portal autofill before submitting.
If you discover a major inconsistency in job dates, credentials, or documents, take more time. Accuracy matters more than completing a checklist quickly.
Sources, evidence limits, and what this guide does not claim
The advice above draws on published career guidance and ATS-vendor documentation rather than supposed access to private scoring systems:
- Greenhouse — Unsuccessful resume parse: documented parse failures, formatting issues, and a parser-specific size limit.
- Greenhouse — Supported candidate file formats: permitted upload types and the separate general attachment limit.
- Workday — Resume Parsing: parsing use cases and sensitivity to file order and format.
- University of Minnesota Duluth — ATS Tips: standard sections, clear work history, and low-risk formatting.
- US Department of Labor CareerOneStop — Resume Formatting: readable formatting, standard headings, and common layout pitfalls.
- UC Davis Career Center — Resumes: evidence-based accomplishments and targeting materials to the job.
These references do not establish a single worldwide ATS rejection rate, prove that every table fails, or guarantee that a particular resume format will produce an interview. The two-version exercise in this article checks extraction and document integrity on your side; it is not a scientific benchmark of Workday, Greenhouse, or other systems.
Final takeaway: make the resume legible, truthful, and specific
Start with the employer's accepted file type. Verify that your document contains selectable text, that titles and dates stay together in extraction, and that the application form displays accurate fields. Then invest your effort in matching the real requirements with evidence of work you genuinely performed. The Horus Valley CV Builder, PDF to Text, and Text Diff Checker can support this workflow, but none can tell you whether an employer will hire you. A readable resume improves the quality of your application information; it is not a guarantee of selection.
