How to tailor a resume to a job description in 15 minutes

Tailoring is editing, not rewriting: the summary, the order of your bullets, and the words you use for work you already did. The six-step version, and what not to do.

Last reviewed

Tailoring is fifteen minutes of editing, not a rewrite. You change the summary, the order of your bullets, and the words you use for things you already did. You do not invent experience, and you do not start a new document for every application.

Done properly it is the highest-return thing in a job search, because the alternative — the same PDF sent 200 times — is competing on volume against people who are also sending 200.

The fifteen-minute version

  1. Read the posting twice and mark the nouns. Tools, systems, methods, certifications, domains. Nouns are what get matched and searched; adjectives (“dynamic”, “passionate”) are filler in both directions.
  2. Split them into three piles: things you have done and already say, things you have done and did not say, and things you have not done. The middle pile is the whole job.
  3. Use the posting’s word for it. If you wrote “automated tests” and the posting says “test automation (Selenium)”, and you used Selenium, say Selenium. This is not keyword stuffing — it is answering in the language the question was asked.
  4. Reorder, do not rewrite. Within each role, move the two most relevant bullets to the top. A reader’s attention drops off sharply after the first bullet of each job.
  5. Rewrite the summary, and only the summary. Three lines naming the role you are applying for, the years you have, and the two things from the posting you are strongest on.
  6. Leave the third pile alone. Missing two of eight requirements is normal and expected. Missing six means the posting is not for you today, and that is information worth having before you spend the fifteen minutes.

What not to do

  • Do not paste the job description into your skills section. Both readers catch it: a human sees a skills block that matches the ad word for word, and any decent matcher sees a candidate whose vocabulary appeared from nowhere.
  • Do not change your job titles to match theirs. Titles are verified. If your title was “Systems Analyst” and they want “Data Analyst”, keep the title and let the bullets make the case — or put their phrasing in brackets after yours if it is genuinely the same job.
  • Do not maintain thirty resume files. Keep one master with everything you have ever done, and generate the trimmed, reordered version per application. Thirty files means you will eventually send the wrong one.
  • Do not tailor before you know the posting is real. Reposted-for-months listings and pipeline-building ads are a large share of what is online. Tailor for the ones you would take.

Does tailoring actually change what the ATS does?

Partly, and less mystically than it is usually sold. Recruiters search their applicant database for terms — that is where matching your vocabulary to theirs pays, because a search for “Selenium” does not find a resume that says “automated tests”. Some systems also rank against the posting, and those rankings are decision support for a human, not a gate that fires by itself.

The bigger effect is on the person. A resume whose first six lines are about the job being filled gets read further than one whose first six lines are about something else.

How many jobs is this worth doing for?

Fewer than you are applying to now. Fifteen tailored applications a week beats a hundred untailored ones, and it is the same number of hours. If you are getting no replies at all, the fix is usually not more volume — this is the checklist for that.

Where this site fits

GetFinalCV has a JD matcher: paste the job description beside your resume and it shows the gap — which terms from the posting your document already supports, which ones it does not, and where they would go. The match is free and runs without a model.

The second half, rewriting bullets to fit, is a separate button, and it proposes a diff you accept or reject per change rather than replacing your document. Nothing is rewritten because you looked at the gap table.

Read next