How to tailor your resume to a job description

A posting is a list of what one team needs this quarter. Two jobs with the same title can ask for different things: one backend role wants Kafka and Kubernetes, the next wants Django and Postgres. A recruiter reading fifty applications, and the applicant tracking system sorting them before that, both look for the posting's own words in your file. When the skill is in your past work but not on the page, it does not count.

Tailoring closes that gap. It does not mean writing a new resume for every job. You keep one complete master resume with everything you have done, and for each posting you make a copy that says the same true things in the posting's terms, with the work it cares about easy to find.

Most postings split what they ask for into two lists, whatever their headings say: what the candidate must have and what would be a plus. Read them apart, because they deserve different treatment.

• Required skills sit under headings such as Requirements, What you bring or Minimum qualifications. A screen will often filter on these.
• Preferred skills sit under Nice to have, Bonus points or Preferred qualifications. They break ties between people who meet the requirements.
• Years and degrees (five years of Python, a degree in computer science or equivalent) are facts about you. You cannot tailor them, only show the ones you have clearly.
• The job's own title, as the posting writes it, matters for the headline at the top of your resume.

Write the skills down by their short names: PostgreSQL, Terraform, stakeholder management. Skip the filler around them (“a passion for”, “strong understanding of”). Then mark which ones your resume already names, word for word or as an obvious synonym, and which it does not. The missing ones are your work list. Our guide to resume keywords goes into how to pick them out.

A skill listed only in a block at the bottom carries little weight: anyone can type a word into a skills section. A skill inside a line of experience says where you used it and what came of it. So for each missing skill, look for the line whose work already involved it.

1. A line already describes the work. You built the event pipeline, and it ran on Kafka, but the line says “message queue”. Name the tool: “Built the order event pipeline on Kafka, cutting checkout latency by 40%”. If the line names a similar tool the posting does not care about, swap it for the one it does, as long as both are true.
2. No line fits, and the skill is required. If you really have the skill, open a new line under the role where you used it most, and write it as a strong statement of what you did with it. A line under the wrong role reads as padding.
3. No line fits, and the skill is only preferred. Leave it out. A preferred skill is not worth a claim your experience does not support. A programming language you do use is the one easy exception: it can go into the line closest to it.

Add every skill you placed to the skills section too, under its group (languages, frameworks, cloud, tools), so both the reader who skims the list and the one who reads the lines find it. Marking the technology names in bold inside the lines makes them easy to scan, and lets you drop a separate “Tech stack” line under each role, which saves space.

Everything that can be checked against a reference, a background check or your LinkedIn profile stays exactly as it happened:

• employers, job titles and seniority
• dates and places of work
• schools, degrees, certifications and licenses
• security clearances and work authorization
• the years of experience you actually have

The one place the posting's title belongs is the headline at the top of the resume. “Senior Data Engineer” as your headline, when that is the job you are applying for, tells the reader what you are aiming at. Your past roles keep their own titles underneath.

Figures are a matter of degree. Scale and impact numbers (requests a day, users served, percentage gained) belong to your work, and a light edit should keep them as they are. A heavier rewrite can sharpen one, but only to something you can explain in an interview.

There are roughly four depths of tailoring, and each has its place.

Deeper is not always better. The further a rewrite goes, the more carefully you have to read it, because every sentence is something you may be asked about.

A tailored resume only helps if the tracking system can read it. Use one column, standard section headings (Experience, Education, Skills), dates with months, and no tables, text boxes, icons or images. Save it as a PDF with a real text layer, on US Letter for jobs in the US and Canada and A4 elsewhere. Our guide to how an ATS parses a resume covers why each of these matters.

Name the file Resume.pdf, or your name followed by “resume”. A file called “Resume_Acme_Backend_v3.pdf” tells the employer you keep versions for each company, which is true for everyone and helps no one.

One page is a good target for a few years of experience, but do not cut true lines to get there. Tighten the spacing and the margins first; two full pages beat one page that drops the work the posting asked about.

Before a tailored resume goes, read it once as the person who will interview you:

• Can you talk for two minutes about every skill you added, in the line where you added it?
• Does any line now claim a tool, a scale or a result that belongs to a teammate, not you?
• Did a required skill end up only in the skills list, with no line showing it?
• Is the headline the posting's title, and every past role still its own?

A match score is a quick way to see whether the edit moved the resume toward the posting. Compare the score before and after; if it barely moved, the skills you added were probably not the ones the posting weighs. Our guide to the resume match score explains what such a score can and cannot tell you.

Jobapplier follows the steps above for you. When a posting comes into our catalogue, a language model trained on job postings (JobBERT) reads its required and preferred skills, so they are ready before you open the job. Press Tailor and the skills your master resume misses go into the lines whose work fits them, or, for a required skill with no fitting line, into a new line under the role that fits it best. A preferred skill with no fitting line is left out, except a programming language, which goes into its closest line.

You choose how far it goes. Off, the default, runs no AI rewrite at all: only the missing skills are placed. Light, Balanced and Aggressive go further, as in the table above. No level adds or changes an employer, a job title, a seniority, a date, a place of work, a school, a degree, a certification, a license, a clearance or a work authorization, and a section you wrote yourself is locked until you reset it.

The result opens beside its match before and after, and you can edit any line before you download it. Every file is a one-column PDF named Resume.pdf. See resume tailoring for the details and what each plan includes.