Parser view
Shows how an applicant tracking system sees your CV, field by field.
“Parser view” opens after the analysis.
This view answers the questions candidates ask most:
- Did the parser read your title and dates correctly?
- Were identity fields such as name, email, phone, location and links found, suspect or missing?
- How does each experience entry look: position, company and date range?
- Were education, skills and languages extracted correctly?
Every missing or suspect field comes with a readable cause, for example "the date range looks split across two columns". Clicking a field highlights its line in the raw text.
How does an ATS read my CV?
The parser view shows how an applicant tracking system can read your CV: the raw text extracted from your file, plus the fields a parser would try to fill from it. It is the quickest way to see what a machine gets, as opposed to what you see on the page.
Upload a PDF, a DOCX or a plain text file. The text is shown exactly as the scorer saw it, and a copy button gives you the raw text. If a job ad is attached, the terms that matched it are marked in the text. Very long text is cut off in the display, not in the analysis.
What fields does the CV parser check?
The CV parser view checks nine profile fields and the dated entries in your experience, and marks each one as found, suspect or missing. A suspect field is present but would not be read cleanly.
Each problem field carries a readable reason, and clicking a field jumps to its source line in the text.
| Part | Fields | Status |
|---|---|---|
| Identity table | Name, email, phone, location, profile, latest title, employer, date range, school | Found, suspect or missing, with the source line |
| Entries table | Title, organisation and date range of each dated entry | A range that ends before it starts is flagged as unusable |
| Sections | Summary, experience, education, skills, languages, certifications | Found or missing |
Example: what does a suspect field look like?
In the parser view, a suspect field is one the checks count as present but the parser could not lift out cleanly, and the view says why. You see the cause next to the field instead of a bare score penalty.
Suppose a job title and its dates sit on two separate lines. The view marks the date range as suspect and explains that it only reads correctly once the lines are joined, so a parser sees two fragments and uses neither. If nothing in the document resembles a field, it is marked missing. If a CV has no readable dates, the entries table says that a parser cannot build an employment history from it.
What does the parser view not do?
The parser view is not a copy of any specific vendor's parser. It shows how this tool's rule-based reader sees your file, which is a readability estimate rather than a guarantee.
If a PDF has pages without a text layer, the analyzer offers OCR. It runs in your browser after a one-time download of the OCR files, and nothing is sent to a server for it. The view reads your text but never rewrites your file.
“Parser view” opens after the analysis.
Last updated