Check your resume before you apply

Checks that a real name, email address, phone number, location, and profile link exist in the text layer and sit where a parser looks for them. Details trapped in a page header, a footer, or an image are invisible to the parser even though you can see them perfectly.

Reads your opening paragraph and judges whether it says what you bring to a specific kind of role. A generic career objective scores low, a summary written around the work you actually do scores high, and no summary at all scores nothing.

Looks for the tools, technologies, and skills of your field, presented under a heading a parser recognizes as skills. Abilities mentioned only inside a sentence buried in your experience are much easier for a parser to miss.

Checks that each role carries a job title, an employer, and dates in a consistent format, and that the bullets underneath describe what you did and what changed because of it. This section carries the most weight in the overall score.

Checks for a clearly labelled education section with your qualification, the institution, and a graduation year. A missing year is one of the most common reasons this section scores below what the candidate expects.

One column, top to bottom. A parser flattens the page into a single stream of text, so a two-column layout can interleave your job titles with your skills list and produce nonsense.

Work Experience, Education, and Skills, spelled the ordinary way. A heading like My Journey or What I Bring reads well to a person and matches nothing a parser is looking for.

Your name, email, phone number, and links belong in the first lines of the document itself, not in the page header region that many parsers never extract.

Your content has to be real text. A resume exported as an image, or scanned from paper, has no text layer at all, which is the single most common reason a resume scores near zero.

One date format throughout, and the same title, employer, dates ordering in every entry. Consistency is what lets a parser work out where one role ends and the next begins.

The checker scores five defined areas and combines them into a single number, so you can see both the headline and where it came from.

Every judgement comes from the document you submit. Nothing is inferred from a profile, a job title, or an industry average.

Issues are ordered by impact and tied to a specific edit, so the report ends with something to do rather than a list of observations.

Different employers run different ATS platforms and different hiring processes. This score identifies the structural faults that break parsing in general, and it cannot simulate any one vendor's parser.