How to tailor a resume to a job description, step by step

Tailoring a resume means reorganising and rewording your real experience so the parts most relevant to one specific posting are the easiest to find, in the vocabulary that posting uses. It takes about thirty minutes per job once you have a system.

Why a generic resume underperforms

A resume written for “any engineering job” has to hedge: it leads with whatever you think is most impressive in general, uses your previous employer’s vocabulary, and buries the one project that happens to match this posting on page two. A reviewer, human or automated, is looking for evidence of this role’s requirements and has limited time to find it.

Step 1: Extract the posting’s concrete requirements

Copy the posting into a document and strip it to its nouns: tools, methods, domains, certifications, named responsibilities, and stated years of experience. Ignore the culture paragraph. You will usually be left with ten to twenty items. Mark the ones the posting repeats or lists first as likely primary.

Step 2: Map each requirement to your evidence

Against each item, write the strongest real example you have, drawing on more than your current resume: older resumes, project notes, reviews. Mark each item as matched, partially matched, or missing. This map is the whole basis for the tailored resume; everything else is editing. Tailoring without inventing experience covers how to handle the partial and missing items honestly.

Step 3: Reorder

• Lead the summary with the two or three matched requirements the posting treats as primary.
• Within each job, move the bullets that map to this posting’s requirements to the top.
• If a relevant project sits inside an otherwise unrelated job, give it its own bullet or a short project line.
• Trim bullets that map to nothing in this posting. They are not wrong; they are noise for this reader.

Step 4: Reword into the posting’s vocabulary

Where your evidence and the posting describe the same thing in different words, use the posting’s words. This is the step most people mean by “keywords,” and it matters for two readers at once: a recruiter scanning for terms from the requisition, and any applicant tracking system search or filter an employer has configured. Keep the fact unchanged; change only the label.

Step 5: Check readability for software and for people

Applicant tracking systems extract text from your file into structured fields. Standard section headings, a single column, real text rather than text in images, and consistent date formats all help that extraction. They also help a person reading quickly. See how to pass an ATS for the formatting detail, and how ATS keyword matching works for what these systems do and do not do with the words.

Step 6: Read it as the hiring manager

Give it two minutes. Can you find evidence for the primary requirements without hunting? Does every specific claim have a story behind it you could tell in an interview? If yes, send it. If a claim makes you uneasy, it is probably a rephrase that drifted into an exaggeration; pull it back.

Doing this per job without starting over

The expensive part is step 2, and it is expensive because the evidence is scattered. Once your evidence is collected in one place, the map for a new posting is a comparison, not an archaeology dig. That is the workflow FilterProof is built around: evidence on a private Memory Board, a pasted job description, a match that shows the matched, partial and missing requirements, and a resume and cover letter generated only from the matched evidence. You still do step 6.

Frequently asked questions