How to Tailor Your Resume to a Job Description, Step by Step
Tailoring means changing which of your real experience is visible, and what you call it. Read the posting for its priorities, mirror the words it uses, and move the bullets that match to the top of each role. Nothing invented.
Most people tailor by swapping the company name in a summary line, which is why the exercise feels pointless. Real tailoring changes the order and vocabulary of the document so the first third of the page is about the advertised job. The process below takes about twenty minutes per application.
Read the posting for its actual priorities
A posting is not a neutral list. Someone had to justify this hire, and the reasons that justified it surface first and repeat. Three things carry the most signal:
- Order. The first two or three responsibilities are usually what the role exists for. Items eight through twelve are often boilerplate carried over from an older req.
- Repetition. Anything appearing in more than one section — the blurb about the team, then responsibilities, then requirements — is what they are worried about. That is your headline.
- The day-to-day section. When a posting describes "a typical week" or the first 90 days, that paragraph is more accurate than the requirements list. Requirements lists get copied. Day-to-day paragraphs get written.
Separate must-haves from nice-to-haves too; postings usually mark this ("required" versus "bonus"). A gap in the bonus list costs almost nothing. A gap in the required list needs a plan, not a lie.
Paste the posting into a plain document and mark it up. Highlight every tool named, every noun for an outcome the role owns (retention, uptime, cycle time, pipeline), and every responsibility that repeats. You now have five to eight items. That short list is the brief for this version of your resume.
Map their words onto work you have already done
The most common tailoring failure is not a missing skill. It is a skill you have, filed under a different name. Screening software and busy readers both scan for the posting's own terminology, so work described in your private vocabulary can pass unnoticed even when it is a direct match.
Build a map before you edit anything. Left column, their term. Right column, what you actually did. If the right column is genuinely empty, leave it empty — that is a gap, not a renaming opportunity.
| What the posting calls it | What you have been calling it | What you actually did |
|---|---|---|
| Stakeholder management | "Talked to other teams" | Ran a weekly priorities call with sales and engineering |
| Voice of the customer | "Told the PM what people complained about" | Summarised recurring ticket themes in a monthly write-up |
| Knowledge base ownership | "Wrote help articles" | Wrote and maintained the public help centre |
| Cross-functional triage | "Flagged bugs to the devs" | Ran a standing bug review with two engineers |
| SLA adherence | "Replied quickly" | Held first-response time inside the team's stated target |
That right-hand column is the honesty anchor. Every renamed line must trace to something you can describe out loud for a minute. Our guide to resume keywords covers which terms are worth mirroring exactly and which are safe to paraphrase.
Reorder before you rewrite
Reordering is free and does more than most rewriting. Chronology governs the order of your roles. Relevance governs the order of bullets inside each role. Those are different rules, and people apply the first one to both.
For each role, move the bullet that best matches your short list to the top — including roles from six years ago. Someone scanning the first line of every role should see the through-line to this job.
Then cut. A resume is a pitch, not an archive. A bullet with nothing to do with this posting, and no job to explain, gets compressed to half a line or dropped.
Chronology decides the order of your jobs. Relevance decides the order of your bullets. Most resumes get the second one wrong by default.
Rewrite to mirror the posting, not to inflate
- Adopt their noun. If the posting says "onboarding", write onboarding, not "getting new customers set up". Keep your own phrasing only where theirs would be inaccurate.
- Match the verb to the responsibility level. "Supported", "ran" and "owned" describe three different jobs. Pick the one that is true; our guide to resume action verbs covers choosing without overclaiming.
- Attach the outcome that posting cares about. The same project can end in a time figure, a quality figure or a scale figure. Use the one they talk about, with a number you can stand behind.
Keep the layout plain while you do this. Tailored wording inside a two-column template can still be mangled on the way into a screening system, which is the subject of our guide on building an ATS-friendly resume.
One bullet, three postings
Here is the underlying reality, unchanged in all three versions. At a mid-sized software company, this person ran the shared support inbox, wrote and maintained the help centre, produced a monthly summary of what customers reported, and held a weekly bug review with two engineers. The figures below are that person's own; use yours.
Handled customer support tickets, wrote help articles, and reported common issues to the engineering team.
Accurate, and invisible. It leads with the least distinctive fact, uses no term any of these three postings uses, and buries the two things that made the job interesting.
Posting A — Customer Support Specialist
It repeats "response times", names a helpdesk tool, and wants someone who can work a high-volume queue without dropping quality.
Owned a shared support queue of roughly 60 tickets a day, holding first-response time inside the team's four-hour target while maintaining the macro library the rest of the team replied from.
Posting B — Knowledge base and technical writing
This one barely mentions tickets. It repeats "documentation", "content maintenance" and "reduce repeat contacts".
Wrote and maintained the public help centre, rewriting articles each release cycle and prioritising new ones from the support queue's most repeated questions.
Posting C — Product Operations Analyst
This one repeats "voice of the customer", "cross-functional" and "surface themes to product". Ticket handling is context, not the job.
Turned support volume into a monthly voice-of-the-customer summary for product, and ran a standing triage with two engineers that moved the top recurring issues into the sprint backlog.
Same job, same person, same week of work. Nothing was added. What changed is which facts appear, which vocabulary carries them, and what each version treats as the headline.
Check what is still missing
Read the finished version against your marked-up posting and note which priority items still have no line anywhere on the page. Two or more missing means either you have relevant experience you have not surfaced, or this is a stretch application. Both are worth knowing before you send. SwiftCover runs that comparison and lists the posting terms your documents do not cover.
Where tailoring ends and fabricating begins
The line is cleaner than people assume. Tailoring changes presentation. Fabricating changes facts.
| Tailoring | Fabricating |
|---|---|
| Reordering bullets by relevance | Moving dates to cover a gap |
| Renaming work using the posting's terms | Claiming a title you did not hold |
| Dropping bullets that do not apply | Dropping a job to hide being fired |
| Choosing which real metric to show | Estimating a metric you never measured |
| Listing a tool you used lightly, described that way | Listing a tool you have only read about |
| Taking credit for your part of a team result | Taking credit for the whole team result |
Two tests settle almost every borderline case. Could the person who managed you read this line and recognise it? And would the line survive the follow-up "tell me about that"? If you would have to invent detail on the spot, it is already a liability.
Never worth it
Do not paste keywords in white text or a tiny font at the bottom of the page, and do not pad a skills list with tools you cannot discuss. Hidden text is fully visible to the software reading the file. Padded skills fail in the first technical conversation. Neither buys anything an honestly mirrored bullet does not.
Being short one required item is not a reason to fake it. Say what you do have, in the cover letter rather than the resume: the adjacent tool you used, the same problem solved another way, how quickly you have picked up comparable things before.
The repeatable twenty-minute pass
Keep one master resume holding everything you have ever done, longer than two pages and never sent anywhere. Each application is a cut of it.
- Read the posting twice. Mark repeated responsibilities, named tools, outcome nouns.
- Write the short list: five to eight priorities, in the posting's own words.
- Fill the terms map: their word, your word, what you actually did.
- Reorder bullets inside every role so the most relevant one leads.
- Rewrite the top bullet of your two most recent roles to mirror their vocabulary.
- Retarget the summary line, if you use one, to the advertised role.
- Cut whatever no longer earns its space and get the page count back.
- Read the short list once more and mark what is still uncovered.
- Every claim traces to something you could describe for a minute out loud
- The posting's top two priorities appear in the first third of page one
- No bullet exists only because it was there last time
- Titles, employers and dates are untouched from your master copy
When you are sending several applications a week, the mechanical parts — the short list, a first-draft rewrite, the coverage check — are what is worth automating. SwiftCover on the web produces a tailored resume and matching cover letter from a posting in about thirty seconds, all of it editable, because the judgement calls in the terms map are still yours.