Compare Your Resume and a Job Description: A Side-by-Side Method
To compare your resume and a job description, put the posting’s requirements in the left column of a table, write where your resume proves each one in the next column, and mark every row as proven, buried or missing. Proven rows need nothing. Buried rows need to move or be reworded. Missing rows are either a real gap you accept or a thing you did and never wrote down. The whole comparison takes about fifteen minutes with a pen or a spreadsheet, and it tells you exactly which lines of the resume to touch.
Most advice jumps straight to “add keywords”. That skips the useful part. A comparison first tells you what the gap actually is, and the gap is rarely a missing word.
What a resume and job description comparison is for
A posting is a list of things someone wants done. A resume is a list of things you have done. Comparing them means checking, requirement by requirement, whether the second list answers the first.
That is different from the two jobs it is often confused with:
- Finding keywords is a vocabulary exercise. Our ten-minute method for finding keywords in a job description covers it, and it is the first half of this comparison.
- Tailoring is the editing that follows. The guide to tailoring a resume to a job description shows where the edits go.
The comparison sits between them. It decides whether you should apply, what to edit, and what to leave alone. Done before tailoring, it stops you rewriting lines that were already fine.
Step by step: compare a resume and a job description
1. Split the posting into requirements
Copy the posting into a document and break it into one requirement per line. Postings bundle several asks into one sentence (“own onboarding, reporting and renewals”), so unbundle them. You are after things a person could check:
- Tools and systems named in the posting.
- Responsibilities phrased as verbs (“manage a pipeline”, “write release notes”).
- Credentials, years of experience and scale (“team of eight”, “multi-site”).
- The job title itself.
Tag each line must if it sits under “requirements”, appears in the first few bullets, or repeats. Tag it nice if it sits under “preferred”, “bonus” or “familiarity with”.
2. Find the evidence on your resume
For each requirement, find the single line of your resume that best proves it. Quote the line, or write its location (“Acme, bullet 3”). If you cannot point at a line, leave the cell blank.
Be strict about what counts. A skill sitting in a list of twenty tools proves less than a bullet showing you used it. A bullet that does the job without using the posting’s words counts as evidence, but weak evidence, and that is what the next step sorts out.
3. Mark each row
Use three marks and nothing else.
| Mark | What it means | What you do |
|---|---|---|
| Proven | A bullet shows it, in words a recruiter would search for | Nothing |
| Buried | You did it, but the proof is low on the page, vague, or in different words | Move it up or reword the label, keeping the fact |
| Missing | No line on the resume shows it | Ask whether you did it and left it out, or never did it |
The third row is where the honest work is. Missing splits into two cases that look identical on the page. Either you have done the thing and never wrote it down, or you have not done it. The first is a resume edit. The second is a gap, and no wording fixes a gap.
4. Count what you found
Add up the marks for the must rows only. A rough reading works well:
- Nearly all proven or buried: apply, and spend your effort on moving and rewording.
- A few missing must-haves, all things you have done: apply after adding them. This is the common case.
- Several missing must-haves you have not done: the posting is aimed at someone else. Applying costs you an afternoon and is unlikely to go anywhere. A different posting is a better use of the time.
There is no magic ratio. Postings describe an ideal candidate, and hiring managers usually expect to meet people with gaps, so one or two missing must-haves are normal. A missing must-have that is the core of the job, the one the title names, is not.
5. Fix the buried and the missing-but-done rows
Now edit, in this order, because it gets the most value for the least rewriting:
- Move before you reword. Put the bullet that answers the top requirement first within its role.
- Match the label. If the posting says “customer implementation” and you wrote “client onboarding”, use the posting’s phrase or write both once.
- Add what you left out. If a missing must-have is something you did, write the bullet. Say what you did, with a number only if you have a real one.
- Mirror the title. If you held the equivalent role under another name, make the equivalence visible near the top.
Leave the proven rows alone. Changing a bullet that already works is the quickest way to make a resume worse.
A worked example
Take a posting for a customer success manager with these must-haves, and a resume that says “Account Manager, SaaS” at the top. The match table might look like this.
| Requirement | Evidence on the resume | Mark |
|---|---|---|
| Manage a book of 40+ accounts | ”Managed 55 mid-market accounts” | Proven |
| Run quarterly business reviews | ”Presented results to clients each quarter” | Buried |
| Own renewals | Nothing | Missing, but done |
| Use Salesforce | Listed in a skills line, no bullet | Buried |
| Experience with enterprise clients | Nothing | Missing, not done |
Four things follow from the table, and none of them is “add more keywords”:
- The accounts row is fine. Leave it.
- The review row is the same work in different words. Rewrite it as “Ran quarterly business reviews for 55 accounts”.
- Renewals were part of the account manager’s job and never made it onto the page. Write the bullet.
- Salesforce needs a bullet that shows what the candidate did in it, not a place in a list.
- Enterprise is a real gap. Say nothing about it, and expect the interview to ask. The candidate can apply with that gap known, rather than finding out in the screen.
Without the table, most people would have rewritten the whole resume and still left renewals off.
When the manual comparison is enough
Do it by hand if you are sending a handful of applications. A table per posting costs about fifteen minutes, it forces you to read the posting properly, and you end with a clear view of what you would be claiming. For a short, careful search, there is nothing to buy.
It is also the right approach when the posting is unusual. A match table copes with a role that does not look like the standard version of itself.
A scanner is a faster first pass at the same question. Our guide to a free ATS resume checker shows how to check a resume yourself first, and covers what the free scans do and do not tell you. Whatever produces the score, the decisions in step 5 stay yours, because only you know which missing rows are true.
Where the time goes, and where a tool helps
The comparison is the quick part. The slow part is step 5: rewriting six or seven bullets for every posting, and keeping each one true. By the tenth application most people are tired and start to stretch.
That is the part InstaResume is built for. You paste your real experience and the posting, and it writes resume bullets or a cover letter grounded in what you gave it, in the posting’s vocabulary. It does not invent employers, figures or tools you never mentioned. It does not compare or score your resume against the posting, so the match table above stays your job, and so does the decision about which gaps are real.
As of October 2026, the free tool pages give 3 generations a day without an account. A free account adds 5 generations, granted once, which do not refill, plus PDF and DOCX export. Pro is $9 a month for 500 generations a month. Pages such as resume bullet points for customer service take a role, your background and an optional job posting, so you can run one posting through it before deciding whether it is worth anything to you.
A workable routine looks like this:
- Build the match table and mark every row.
- Decide whether the missing must-haves are real gaps. If so, pick a better-fitting posting.
- Write down, in plain notes, the experience behind each buried or missing-but-done row.
- Paste those notes and the posting into a tool page for a draft, or write the bullets yourself.
- Check every line against the table. If a line claims something you cannot defend, cut it.
- Pair it with a cover letter built on the same table, since the rows you could not fit on the resume are often the ones worth a sentence there.
Mistakes that make the comparison useless
- Comparing against the whole posting. Culture paragraphs and company history are not requirements. Skip them.
- Counting a skills list as proof. A name in a list shows you have heard of it. A bullet shows you used it.
- Marking everything buried. If every row is “buried”, you are being kind to yourself. A row is proven only when a bullet would convince a stranger.
- Treating a gap as a wording problem. If you never did it, a new phrase does not change that, and it fails at the first interview question.
- Doing it once. Postings for similar roles differ in two or three requirements. Keep the finished table, and next time only the differing rows need work.
Frequently asked questions
How do I compare my resume to a job description for free?
Use the table above. It needs a document and fifteen minutes. Free scanners offer a quicker score, and the ones we compared are covered in our Jobscan alternative guide, but the table tells you what to change, which a bare percentage does not.
How many missing requirements are too many?
There is no fixed number. Missing nice-to-haves rarely matter. One or two missing must-haves you could grow into are common. A missing must-have that defines the job is a reason to look elsewhere.
Should I copy the job description’s wording into my resume?
Use the posting’s wording for tools, titles and credentials, where an exact match is easiest to find. Describe everything else in your own words, and keep every line something you did.
How often should I redo the comparison?
For every posting you take seriously. Keep the earlier tables, because applications to similar roles share most of their rows.