Sending the same resume to every job feels efficient. It is not. A generic resume answers a question nobody asked: here is everything I have ever done, in no particular order, and it is up to you to work out whether any of it fits this role. The recruiter will not do that work. They have a pile of applications and a posting in front of them, and the resume that makes the fit obvious wins the read.
Tailoring is the work of making the fit obvious. It does not mean inventing experience, copying the posting word for word, or rewriting your career for every application. It means reading the posting properly, finding the real evidence in your history that answers it, and moving that evidence to where the reader can see it. Think of it like a fitting, not a disguise: the same person, the same record, cut to sit right for this particular job.
The short version: read the posting in three passes, build a small evidence map from requirements to real examples, rewrite only the four places that carry the argument (title, summary, skills, bullets), leave everything else alone, and save the version you sent. The rest of this article walks through each step, with a worked example.
Read the posting in three passes
Most people read a posting once, skim for keywords, and start editing. That is how resumes end up stuffed with terms the writer does not understand and missing the actual job. Read it three times instead, each with a different question in mind.
- Pass one: what would this person actually do? Ignore the requirements list for a moment. What does a normal week look like in this role? What decisions would they own, and who would use the result? This pass separates the real job from the boilerplate. A posting that says "fast-paced environment" and "self-starter" is telling you almost nothing; the paragraph about owning the weekly release notes is telling you the job.
- Pass two: what must they already be able to do? Now read the requirements. Mark the hard requirements (must have, required, essential) separately from the nice-to-haves (preferred, bonus, a plus). Note the tools, methods, and credentials by name, and the level the role expects. This is the list your resume has to answer.
- Pass three: what words does this employer use? Read it once more for language. Does it say "customers" or "clients"? "Stakeholders" or "partners"? "Onboarding" or "implementation"? The same work described in the employer's own words is easier for a human to recognise and easier for a parser to find. You are not copying sentences. You are learning the employer's vocabulary so your real experience can be described in it.
Three passes takes about ten minutes, and it is the highest-value ten minutes in the whole application. Everything after this is execution.
Build an evidence map before you touch the resume
Do not open your resume yet. Take the requirements from pass two and, for each one, write down the real evidence from your history that answers it. A simple table works: requirement, evidence, where it goes on the page. The discipline of the table is what keeps the tailoring honest. If a requirement has no evidence, the table shows a gap, and a gap is a decision you make deliberately, not a claim you smuggle in.
| Posting asks for | Your real evidence | What to do |
|---|---|---|
| Weekly reporting to stakeholders | Wrote the weekly status update for a team of six for a year | Lead bullet in the most recent role; name it in the summary |
| Scheduling and coordination | Kept the shared project calendar and chased late updates | Second bullet; use the posting's word "coordination" |
| Budget ownership | No budget responsibility in any role | Leave it off. Do not dress up tracking expenses as owning a budget |
| A named tool you have never used | No experience with it | Leave it off, or learn it. Never list a tool you cannot discuss |
Notice what the map does. It stops you from copying every phrase in the posting, because the phrases with no evidence have nowhere to go. It also stops you from burying your best proof: the reporting example was sitting in the middle of a job description nobody would have read carefully, and now it is the lead bullet. If you use a tool to tailor, this map is still the thing to check afterwards: the guide on tailoring to a posting covers the same evidence-first order in step form.
Rewrite only four places
Here is the part that saves the method from eating your evening. You do not rewrite the whole resume. You rewrite four places, and you leave the rest alone.
- The title line. Match the posting's title when it is true. If you are applying for a Project Coordinator role and your last title was Project Coordinator, say so. If your last title was different but the work matches, use the posting's title only if it is an honest description of what you did, and keep your real title in the role itself. Never claim a title you did not hold.
- The summary. Two or three lines, rewritten per posting: who you are, the two or three pieces of evidence that matter most for this role, and the outcome. The summary is the reader's first impression, and it is where tailoring pays off fastest. The summary formula still applies; only the evidence changes.
- The skills section. Reorder it so the posting's required skills come first, in the posting's exact wording, and cut anything the posting did not ask for. How to list skills on a resume covers the full filter: hard skills in the list, soft skills proven in bullets, nothing you cannot defend.
- The strongest bullets. Rewrite three to five bullets in your most recent roles so the evidence from your map is visible and phrased in the posting's language. Reorder bullets inside each role so the most relevant one comes first. You are not inventing new achievements; you are giving the relevant ones the top slot and the clearest wording. The bullet formula — action, work, number, impact — still applies.
Everything else stays as it is: dates, employers, education, and the roles that are less relevant to this posting. In fact, for the less relevant roles, do the opposite of rewriting: trim them. One line each is plenty. The reader's attention is finite, and every line spent on an old, unrelated role is a line not spent on the evidence that matters.
Use the posting's words where they are true
This is the fine line in all tailoring, and it is worth stating plainly. Using the employer's words for experience you genuinely have is not stuffing and not dishonesty. If the posting says "stakeholder reporting" and you wrote weekly reports for stakeholders, call it stakeholder reporting. The human reader recognises it instantly, and the parser matches the literal text. If the posting says "stakeholder reporting" and you never reported to a stakeholder, writing the phrase is a lie that an interview question will expose in seconds.
The test is simple: could you answer a follow-up question about every phrase you added? If yes, keep it. If your honest answer would start with "well, sort of", take it out. Keyword matching without stuffing goes deeper on where this line sits, and handling skill gaps honestly covers what to do with the requirements you cannot meet yet: name the gap, show adjacent experience truthfully, or leave it off. A resume with one honest gap beats a resume with one invented skill every time, because the gap is a conversation and the invented skill is a trap.
Once the draft is done, check it the way the system will: run the finished file through the ATS checker and confirm the skills and terms you care about are actually extracted. If they are not, the formatting is hiding them — a table, a text box, or an image — and now you know what to fix before you send it.
A worked example
Fictional applicant, real method. Priya coordinated support for a small software team: she ran the weekly stand-up, kept the shared calendar, wrote release notes, and answered customer questions. She is applying for a Project Coordinator posting that asks for scheduling and coordination, stakeholder reporting, and a tool she has never used.
Before: the generic version
Summary: "Organised and motivated professional with strong communication skills seeking a challenging role."
Bullet: "Responsible for various coordination tasks and team communication."
Every word is true and none of it helps. A recruiter reading this learns nothing about what Priya did, and the parser finds no overlap with the posting.
After: tailored to the posting
Summary: "Coordinator with two years keeping a six-person software team on schedule: weekly stakeholder updates, shared project calendar, and release notes that cut repeat support questions."
Bullet: "Coordinated scheduling for a team of six: ran the weekly stand-up, kept the shared project calendar, and chased late updates so milestones stayed on track."
Bullet: "Wrote the weekly stakeholder report and the release notes, cutting repeat support questions after each release from about twenty to about five."
The tool she has never used is nowhere on the page. The scheduling and reporting evidence is in the posting's words, with numbers she can defend. Nothing was invented; the same history is simply presented so this employer can see it.
Save the version you sent
Two files, always. Keep one base resume: the full, factual record of your roles, dates, education, and achievements, with nothing tailored away. Then save one tailored copy per application, named after the role and the company, and send exactly that file. When the interviewer asks about a line on the resume in front of them, you want the same file open, not your base version with different wording. If a tailored version drifts from the base — a date changed, a title polished past honesty — the base is the record that catches it. Review the tailored copy against the base before you send it, and ask of every change: is this still true?
One more habit worth keeping: track which version went where. A short note — company, role, date, file name — saves you from opening an interview with the wrong resume in front of you.
The quick checklist
Before you send a tailored resume, run through this list:
- You read the posting in three passes: the work, the requirements, the language.
- Every requirement has either real evidence on the page or an honest, deliberate gap.
- The title, summary, skills, and three to five bullets carry the argument; the rest is untouched.
- Every phrase borrowed from the posting describes experience you can defend in one sentence.
- Less relevant roles are trimmed, not rewritten.
- Nothing on the page is a skill, tool, or title you do not actually have.
- The ATS checker extracts the skills and terms you care about.
- You saved the exact version you sent, and the base resume still matches it on dates and employers.
If the answer to all eight is yes, the resume is tailored: it tells this employer, in their own words, why your real history fits this specific job.
The bottom line
Tailoring a resume to a job description is not a trick and not a rewrite. It is the discipline of reading the posting properly, matching each requirement to evidence you actually have, and putting that evidence where the reader can see it. Do it once slowly, and the method gets faster every time: the evidence map gets easier, the four places get familiar, and the honest version of your history starts writing itself. The generic resume asks the reader to do your work for you. The tailored one does the work for them, and that is why it gets read.