Paste the resume you're about to send, then set it against a real employer's posting, the Labor Department's national profile of the job, or both, and see which requirements your resume states outright. Not implies. Not gestures at across three bullet points. States. Screening software doesn't read between the lines, and neither does a recruiter on applicant number 212.
One warning about pasting a posting. You'll be copying the whole page, so the tool will pick up some material that has nothing to do with the job: benefit plans, PTO policy, the 401(k) match, the paragraph about the company's culture. It filters out what it can recognize, but not everything. After you run the comparison, look through the requirement list and delete anything that isn't really a duty or a qualification. Nobody gets screened out for lacking dental coverage.
1The job
Pick one of O*NET's 923 occupations and the tool can compare your resume against the full national profile: the core tasks people in the job report doing and the software employers ask for most. You can run it with a posting, or with no posting at all.
2Paste what you have
What they asked for
The full employer posting, headings and all, copied from the company's own career page if you can. Leave it blank to compare against the O*NET profile alone.
What you're sending
The resume text, exactly as you'd submit it. Plain text from your document is fine.
3The comparison
The basics
Screening software often filters on these before a person reads anything.
Requirement by requirement
The tool marks what it can find. You know things it doesn't, so change the status or importance where it guessed wrong, and delete anything that isn't really a requirement. Tap a column heading to sort.
| Actions |
|---|
4Things to consider
The posting is what the employer says. The resume is what you say. This puts them next to each other. It doesn't grade you.
How to read this
The tool matches words, not competence. A "found" means the term appears on your resume, not that you're good at it, and a "missing" may only mean you described the work in your old company's dialect. That second case is the fixable one, and more common than people think.
One posting is one hiring manager's wish list, often written by committee and padded with items nobody will check. The tool can't tell you whether the job is real, whether an internal candidate already has it, or how a particular screening system weighs keywords. Importance is a guess from the posting's headings and wording ("required," "preferred," "a plus"); correct it where you know better.
O*NET tasks are written in government prose and matched by shared words, which is crude. A task marked "not on resume" often means you described the same work in your own terms. Read those rows as questions, not verdicts: have you done this, and would a stranger reading your resume know it?
There's no score here on purpose. A match percentage would look precise and mean very little. What's useful is the list: which of their words you're missing, and whether you can honestly add them.