Applicant tracking systems can often read selectable text and use it to fill fields such as a name, employment history, or contact details. Results depend on the system, the format, and how the file was made. A résumé can be visually readable and still extract in an awkward order. If the employer shows a preview, check that separately. The simplest goal is to give both the software and the hiring reader a clear version of the same facts.
Understand what people mean by “the ATS reads it”
An applicant tracking system helps an employer manage applications. Parsing is the step where software attempts to convert information from a résumé into data fields. Greenhouse, for example, documents that résumé parsing can populate a candidate profile and that a file can remain attached even if parsing does not succeed. Other hiring workflows may handle a failed parse differently. A warning about parsing tells you something about the file or fields. It does not tell you what the employer will do next.
There is also a difference between extracting text and understanding the relationships between pieces of text. A parser may extract the word “Coordinator,” the name of an employer, and a date, then fail to recognise that those three pieces describe one job. Keeping them close together in a clear reading order makes the relationship easier to see. If you submit through a portal that fills fields, inspect those visible fields even when you checked the file locally.
| Résumé element | What can go wrong | A format to test |
|---|---|---|
| Name and email in a graphic | Text extraction may skip the letters in the image | Write both as selectable text in the main document. |
| Experience layout in two columns | Reading order can mix nearby sections | Use one clear sequence for heading, employer, title, dates, and bullets. |
| A visual skill rating | The length of a bar or number of icons may not extract meaningfully | Name the skill in text and support it with a job or project. |
| A text-based PDF | Text may extract while individual fields are still assigned incorrectly | Check text order and review any portal preview separately. |
Use real text for the information the employer needs
A plain name, phone number, and email are more useful than those details embedded in a background graphic. A photo, illustration, or icon can be visible in the file without its text being selectable. Adobe’s guidance describes how scanned documents may contain images of words and require optical character recognition to make those words searchable or selectable. When you have the original résumé, exporting from it as text can be simpler than using a scan and correcting recognition errors later.

The same principle applies to a skills graph. A bar may show that you consider a skill advanced, but a text extraction may return only the heading or nothing about its level. Name the skill and put a related action in your work history, such as “Built a weekly inventory report from Excel tables and reviewed exceptions with two site leads.” The employer has something specific to evaluate, and you can explain it during an interview.
- Read the file
The application system receives it and may extract selectable text. - Assign the fields
The parser may identify names, dates, titles, and employers. - Review the record
The employer can use the displayed fields or attachment, depending on its process.
Check reading order before changing every part of a layout
Open the actual file you plan to submit. Copy its text into a plain-text editor and check the sequence of the first page. If an Education sidebar appears in the middle of Experience, try a simpler reading order and re-export. If your contact details do not appear, check whether you placed them in a graphic, decorative box, or header. Bring essential text into the main document if needed. Read each employer, title, date range, and bullet together so you can catch a separation that would change the meaning.
Use ordinary section headings and consistent job entries. A restrained two-column layout may extract correctly in one test. If you cannot inspect the output or the important elements interleave, choose a standard layout with one sequence. Keep a formatted copy for settings where you specifically want it, such as direct sharing or a separate portfolio, when accepted. Always use the file type and size requested by the employer.
Worked example of an employer and date getting separated
Imagine a résumé shows two job entries with dates in a thin column on the left. A viewer might extract both dates before it reaches the employers on the right. The output could read “2024–2026, 2021–2024, Operations Coordinator, North Office, Support Assistant, South Office.” A reader can work out the likely pairings from the page, but a text-only process has less context. Move each date to the same line or immediately below its employer and role. Export again and copy the text. You should be able to read each job as a complete entry before you reach the next one. If the portal still pre-fills the fields incorrectly, compare against the original and correct them if you can. This test shows which change helped the exported text order and keeps portal behaviour as a separate check.
Be careful about universal ATS claims
The judgment you can make from a test is limited. If you can select the text, your viewer found selectable text. If it pastes in order, you have a useful check of that export. Neither is a guarantee that every employer’s parser will fill fields the same way. A formatting change also does not establish that your application meets the qualifications. Check your evidence against the posting and fill all required fields that genuinely apply to you.
If a portal offers a preview, compare it with the final résumé. Look especially at the first role, the last role, your education, and contact details. Fix any fields you are allowed to correct before submitting. When the preview is missing, apply using the supported format and your own checks. Save a copy of the exact file you sent so you can provide the same version if a recruiter requests it.
Frequently asked questions
Do ATS systems read PDF or DOCX files better?
Use whichever format the application requests. If it accepts both, test the actual exports. Choose the one with the clearer reading order and preview. Document construction matters, so one clean PDF can be preferable to a poorly structured DOCX in a given situation, and the reverse can also be true.
Are icons and tables always unreadable?
A decorative icon or layout table can coexist with readable text. Problems arise when essential information is conveyed only by a graphic or when reading order separates facts that belong together. Put key text in a clear order and test the file rather than treating every visual element the same way.
Does a failed parse automatically reject an application?
That depends on the employer’s software and process. Some products may still attach the original document when parsing fails. If you can see a warning or editable fields, follow the instructions, correct what you can, and check that you submitted the requested document.
Cover photograph by Roman Denisenko on Unsplash.