You upload your resume and the application fills in your details. Your email is correct. Your latest employer is missing. The dates from your previous job now appear beside your current one.
Before rewriting your experience, check where the information went wrong. The file may contain the right words while the application puts them in the wrong fields.
This guide gives you a way to inspect that handoff. It cannot tell you why an employer rejected an application, and it does not predict whether you will get an interview.
Start with the fields that are wrong
Keep the uploaded file and note the error: missing employer, merged jobs, wrong dates, or absent contact details.
There are four useful checkpoints:
- The exported document: can you see and select the information?
- The copied text: does it remain readable in a sensible order?
- The application fields: did the portal assign it to the right place?
- The completed application: are the entries accurate before submission?
Passing one check does not establish the next. A PDF can look correct and copy badly. Text can copy correctly and still be assigned to the wrong field.
Greenhouse documents cases where resume information cannot be imported automatically, including partial imports. Its guidance also identifies formatting issues such as columns and contact details in headers or text boxes. That is evidence about Greenhouse's behavior; it is not a rule for every recruitment system. Source: Greenhouse's parsing troubleshooting guide.
Check the file you actually uploaded
Open the exported PDF or DOCX, rather than only checking the editor you used to make it. Exports can change line breaks and spacing.
Try selecting your name, email, current job title, and one complete experience bullet. If you cannot select text in a PDF, it may be an image-based document. If possible, return to the original editable file and export a version that preserves text. Avoid relying on a screenshot of your resume.
If you only have a scan, OCR may help recover the text, but proofread it. Pay particular attention to email addresses, dates, and technical names. A recovered document still needs checking.
Next, copy the resume into a plain-text editor. Look for these specific problems:
- A sidebar interrupts an experience bullet.
- Dates appear together, separated from their jobs.
- The email disappears or is split across lines.
- Letters in a heading are separated by spaces.
- Words such as “verified” or “workflow” lose letters when pasted. Search for those full words in the PDF, too.
This is a quick inspection of text extraction. It does not reproduce the employer's parser. Use it to spot obvious damage, then check the actual portal whenever it provides a preview.
Repair the symptom you found
| What you observe | First change to try | What to check next |
|---|---|---|
| You cannot select the PDF's text | Export again from an editable source with text preserved | Can you select and copy the contact block and experience? |
| Sidebar text interrupts job descriptions | Create a single-column version | Does each job stay together in copied text? |
| Phone or email in a header/footer disappears | Move contact details into the first few lines of the document body, as ordinary text | Do they survive copying and populate the form? |
| Words containing fi, fl, or ff paste with missing letters or boxes | Try another font or disable optional ligatures, then re-export | Can you search for and paste the complete words? |
| Text looks sharp but cannot be selected after an outlined-text export | Export from the editable source with text preserved rather than converted to shapes | Can you select, search for, and copy full words? |
| Dates attach to the wrong job | Place employer, title, and dates together in a consistent sequence | Does each date range stay with its employer? |
| Copied text looks correct but the form is wrong | Correct editable fields manually; try another accepted format if practical | Is the completed form accurate? |
Header/footer placement and broken letters are different problems. Keep contact details in the body; do not assume a PDF extractor preserves the word processor's header structure. Ligatures combine letters into a glyph, which can complicate text extraction. A text-copy failure does not identify its cause by itself. Source: pypdf extraction documentation.
Change one suspect feature at a time when practical, then repeat the check.
Follow the employer's file instructions. If PDF and DOCX are both accepted, compare exports; neither works best everywhere.
A worked example: the date that moved
The following example is fictional. It illustrates a diagnosis, not a test we ran against an ATS.
In the original two-column resume, a narrow left column holds dates. The right column holds employers and bullets. Visually, the dates line up with the right jobs.
After copying into plain text, the sequence looks like this:
Feb 2024–Present
Jul 2021–Jan 2024
Current employer
Backend Engineer
Built an internal reporting API.
Previous employer
Software Engineer
Maintained a customer support integration.The words survived, but their relationships became unclear. Try a simpler layout; this does not prove how an ATS interprets the file.
In a revised single-column version, each job becomes a complete block:
Current employer
Backend Engineer | Feb 2024–Present
Built an internal reporting API.
Previous employer
Software Engineer | Jul 2021–Jan 2024
Maintained a customer support integration.Re-export, repeat the copy check, and inspect the portal's fields if you can upload again before submitting.
Do not alter your actual employment dates or official title to make an import look cleaner. Correct the presentation and the application fields.
Use this checklist before you submit
Check the final exported file and the completed application side by side:
- My name and contact details are present and accurate.
- Each employer, job title, and date range belongs to the same role.
- Experience bullets remain readable in the copied text.
- Education entries have not been mixed with employment.
- I followed the portal's file-type and size requirements.
- I corrected any inaccurate editable fields before submission.
If all relevant fields are accurate, stop changing the file for this application.
If the portal hides imported information, you can check the file and copied text but cannot verify hidden field assignment.
Questions that usually come next
Does a parsing error mean automatic rejection?
A parsing error alone does not establish the employer's decision. Greenhouse describes an unsuccessful import where the resume remains attached and candidate details need manual entry. An employer's subsequent screening process is a separate question. Source: Greenhouse.
Should I remove every graphic?
Keep essential information in ordinary text and link to a visual portfolio separately. A plain version is a practical fallback if imports fail.
Will a higher resume-checker score fix this?
A score does not show that the employer's application fields are correct. Check the failure you can observe. Resume-to-JD alignment is a separate task: once the document is readable, review whether it shows truthful, relevant evidence for the role.
For that next step, see our guide to mapping resume keywords to evidence and guide to defensible engineering bullets.
