Who runs this site
Resumes.tools (resumes.tools) is operated by Anderson Gomes Ferreira. contato@resumes.tools
How it works
Files are read in your browser. A PDF is read with PDF.js, the open-source PDF reader from Mozilla; a Word file (.docx) is unzipped and its XML is read directly. Nothing is uploaded.
Keywords come from the job description: skill names from a built-in list, repeated phrases of two or three words, and repeated single terms, with common words and hiring boilerplate left out. A keyword counts as found when the same word stems appear in your resume (managed, manage and managing match).
Coverage is the share of the job’s keywords found in your resume, with skill names and terms from the requirements weighing more. It measures overlap of words, not fit for the job.
Layout checks look for things that parsers often read out of order: tables, text boxes, several columns, contact details only in the page header or footer, icon fonts, and PDFs with no text layer.
Writing checks look at section headings, date formats, how each bullet starts, whether it has a number, its length, and first-person words.
Where the data and rules come from
- Mozilla PDF.js — Library used to read the text of PDF files in the browser
- ECMA-376 Office Open XML — Format of .docx files: paragraphs, tables, text boxes, sections and columns
- U.S. OPM: Agency guidance on the two-page limit on resume length — Two-page limit for federal resumes on USAJOBS
How we keep the content up to date
The checks are rules written in code and covered by tests. The page-limit source is opened again when the guidance changes.
What this site is not
Every employer configures its own applicant tracking system, and none publishes how it ranks candidates. The checks point at common causes of misreading and at weak writing; they do not predict whether a resume will be shortlisted or a person hired.
Get in touch
Found a mistake, have a question or a suggestion? See the channels on the contact.
This page was last reviewed: