Kyrolane

Resumes

Resume Parsing Explained

How applicant tracking systems extract fields from your file—and why columns, headers, and images make qualified people look like empty records.

Kyrolane Career Team4 min read

Recruiters do not open your PDF first. In most companies the first "reader" is a parser: software that copies your file into fields in Greenhouse, Workday, Lever, iCIMS, Taleo. Ranking, recruiter search, and the preview pane all run on that copy.

If the copy is wrong, nothing downstream can save you. This page is the systems explainer. ATS Resume Format is the fix-it checklist. Both belong to the Ultimate ATS Resume Guide.

What parsing is trying to fill

A typical extractor is hunting for:

  • Identity and contact (name, email, phone, URL)
  • Section boundaries (Experience vs Education vs Skills)
  • Role lines (title, employer, location, start, end)
  • Body text under each role
  • A skills list
  • Education and credentials

It is not scoring your leadership. It is not "rejecting" a font. It is filling a form. Empty form, empty candidate.

That is why format failures do not look like failures. There is no error toast. There is a plausible-looking profile with a blank skills field, and every search against that field misses you.

How the machine actually reads

Rough pipeline:

  1. Text extraction. PDF/DOCX → a stream of characters. Scanned pages need OCR; many pipelines skip or cheap out.
  2. Reading order. Tokens are ordered as the file encoded them, not as your eyes read a sidebar.
  3. Section mapping. Headings that match known labels (Experience, Education, Skills) become buckets. "My Journey" often becomes leftover text.
  4. Field assembly. Repeated patterns (Title, Company, Dates) train the guess for the next role. Inconsistent date formats break the guess.
  5. Skills harvest. Lists, commas, and known skill dictionaries. Icons and bars harvest nothing.
What an ATS parser actually does

Two-column layouts die at step 3. The stream becomes Senior Engineer React Acme TypeScript 2021–Present led migration... and the skills field stays empty because those words landed in Experience.

Headers and footers die at step 1. Plenty of extractors never look there. Your email never enters the record.

What good extraction looks like

You do not need vendor software to approximate it.

Paste test. Select all in the PDF, paste into a plain-text editor. Check:

  • Name and email first, not missing
  • Experience in chronological blocks, not spliced with a sidebar
  • Dates glued to the right jobs
  • Skills as words, not □□□□

If you cannot reconstruct the resume from paste, neither can Workday.

Form test. When a portal auto-fills application fields from the upload, read them. Wrong titles and missing jobs are parse errors you can still correct in the form—and a signal to fix the file.

Human preview. Some ATS preview panes show the parsed record, not your design. If a recruiter comments that your resume "looks sparse," ask whether they are looking at parse vs PDF.

Parse check — before you tailor wording

  • Text is selectable in the PDF
  • Paste order matches visual order
  • Contact is in the body
  • Headings are Experience, Education, Skills (or close cousins)
  • Dates use one pattern
  • Skills appear as words in paste
  • Portal auto-fill matches the file; you correct mismatches

Common questions

What is resume parsing?
Parsing is the step where software turns your PDF or DOCX into structured fields—contact, work history, education, skills—so the ATS can search, filter, and display you. It is not the same as ranking or a knockout question.
Does a parse error mean I am automatically rejected?
Usually no knockout. Worse: you are stored incorrectly. A recruiter search for your actual title never finds you. The preview looks thin. Humans skip it. You experience this as silence.
Why do two-column resumes parse badly?
Most extractors read top-to-bottom in document order, not visual columns. A skills sidebar gets interleaved into job descriptions, or dropped. The recruiter sees word salad or an empty skills field.
Can parsers read scanned PDFs?
Only if OCR is good, and many ATS pipelines are not trying hard. If you cannot select the text with a cursor, assume the parser cannot either. Export from Word or Google Docs.
Do I need to fill the ATS forms if parsing is perfect?
Yes. Portal fields are a second, often required, structured record. Parsing fills a resume profile; application forms are what some workflows actually search. Paste carefully; do not type from memory and drift from the file.
How does Kyrolane parse a resume?
We extract the same kinds of fields an ATS would—contact, sections, dates, skills—and show you what would be missing or jumbled. Suggested fixes stay in your control. Details stay on the format guide's two-reader test.

Put this into practice

Use Kyrolane to run the workflow described above—free to start, no credit card required.