How to Use the ATS Resume Checker: Inputs, Results, and Limits
Use the local ATS checker with a sample or your own text, interpret keyword coverage and prioritized fixes, and understand what the report cannot inspect.
Open Resume Kit Team · · 4 min read · Updated
Open Resume Kit's ATS checker reviews pasted text in your browser. This guide explains its inputs and results; it does not repeat the resume parsing background.
The tool uses local rules. It does not connect to an employer's ATS or inspect an original PDF file.
Try the Sample or Transfer Your Draft
Choose Load Sample to populate a fictional resume and job description. Use that sample to understand the interface rather than copying its career details.
For your own application, choose Clear and paste resume text. The builder's ATS Check button can also transfer draft text to the checker. Confirm that you are reviewing the intended version.
Paste the actual job description into the optional second field if you want keyword feedback. Results update as you edit the inputs.
Read Keyword Coverage as Text Overlap
The checker selects terms from the job description and looks for them in the resume text. It is a simple text comparison, not a measure of professional competence or the employer's criteria.
Without a job description, the coverage display asks you to add one. An overall score shown without that input is not evidence of a match to a specific vacancy.
Illustrative example:
Listing: prepare SQL reports for operations. Resume draft: prepared weekly reports.
If SQL appears as missing, ask whether the candidate actually used it. If yes, describe the work more clearly. If no, do not add it to raise the score.
Review Prioritized Fixes One at a Time
The text checklist score uses three equally weighted checks: a contact-email pattern, core headings, and text-formatting signals. Skills and Education are recognized alongside Experience or Projects. A summary is optional. A passed signal does not validate the address, section content, PDF layout, or an employer's parsing result.
Writing suggestions and keyword overlap are separate and do not affect the score. There is no word-count or metrics penalty. Describe an actual contribution or deliverable; use numbers only when verified. A phrase such as "assisted with" may accurately describe your contribution; make it specific without claiming you led the project. Each check includes its rule and a practical example.
Do not treat detected headings as proof the associated content is complete. The rules look for text patterns.
Separate Warnings From Confirmed Faults
The formatting rules flag table-like rows and some decorative symbols or image-placeholder words. Ordinary pipes in contact and date lines are not treated as tables. Even a table warning is a prompt to review reading order, not proof that an exported file cannot be parsed.
Likewise, text resembling a URL does not prove its destination works. The checker cannot determine whether a link remains clickable in the PDF.
For page boundaries, fonts, reading order, and hyperlinks in the saved document, follow the PDF inspection guide.
Edit and Compare the Same Inputs
Make one supported change, then compare the result using the same job description. For example, replace a vague reporting bullet with the actual tool, task, and audience.
Use Copy Report if you want to keep the displayed summary with your application notes. Store it privately because it can contain information from your draft.
Scores from the checker and the builder are calculated differently. The builder score guide explains the separate weighted categories.
Know When to Stop
Finish when you have reviewed the relevant warnings, your claims are accurate, and the original file is readable. A higher number alone is not a reason to add irrelevant skills, unnecessary links, or invented outcomes.
If you need to create the document first, use the worked resume example. No local report predicts an interview or an employer's screening decision.