Every few weeks someone posts a resume in r/EngineeringResumes that looks great and gets no callbacks. The usual advice is "quantify your impact". Sometimes the real answer is more boring: the tracking system never read the document properly.
Here is what happens to your PDF after you click Apply, and how to see it yourself.
Step 1: text extraction
The parser does not look at your resume. It extracts a character stream from the file, in whatever order the PDF stores it. For a single-column document written in a word processor that order matches reading order. For anything with columns, text boxes, tables or icons it often does not.
Common failure modes I see in developer resumes:
- Two-column layout where the skills column is interleaved line by line with the experience column.
- Dates right-aligned with a tab stop, which some parsers read as a separate paragraph.
- Section headings rendered as icons (a wrench for Skills, a graduation cap for Education). The icon is an image; the parser sees no heading.
- Skills as a bar chart. "Python ██████░░" extracts as "Python" and a row of box characters.
- Contact details in the page header. Some parsers skip headers and footers entirely.
Step 2: section and field detection
From the character stream the parser guesses sections and then fields: job title, employer, start date, end date. It uses heading names and patterns. "Experience", "Work Experience", "Professional Experience" all work. "Where I made a dent" does not. Company on one line, title on the next, dates on a third is fine. Title and company on the same line separated by a pipe is usually fine. Dates in a separate column are the classic breaker.
Step 3: matching
Only now does keyword and skills matching happen, against the text the parser managed to structure. If your Kubernetes experience lives in a paragraph the parser assigned to the wrong job, it is still there for a human reader but may score as missing for the filter.
How to check your own file
Two options.
The manual one: open your PDF, press Ctrl+A, paste into a plain text editor. Read it top to bottom. If the order is wrong for you, it is wrong for the parser.
The faster one: upload the file to an ATS checker that shows the extracted text. I run one at OwlApply: ATS resume checker. It is free, needs no account, and returns the ATS score, the plain text a tracking system pulls from your file, and a list of what breaks parsing. Files are deleted after 24 hours. Content rewrite suggestions are part of the paid plan, but the parsing view, which is the part this post is about, is not.
What good looks like
If you want reference points, the 20 software engineer resume examples on the same site all pass the three steps above and cover full-stack, front-end, back-end, mobile, DevOps, QA, cloud and a few more. Each opens in the editor for free.
Disclosure: I am the founder of OwlApply (2024). The three-step description applies to every tracking system I have looked at, not just to our checker, so the Ctrl+A test is worth doing even if you never open our site.
