Most people either send the same résumé to every job or rebuild it from a blank page each time. Neither works well. The first ignores what each posting is actually asking for; the second burns an hour per application and still leaves you guessing what to include. Tailoring done right is neither — it's a short, repeatable loop you run against the same base résumé every time, and it takes minutes once you know the steps.
Start from the posting, not your résumé
Open the job description before you touch your résumé. Read it for two categories: the must-haves — the requirements that are genuinely load-bearing for the role — and the nice-to-haves, the wish-list items a hiring manager would love but won't block a candidate over. Postings rarely label these explicitly, but the language usually gives it away: "required," "must have," and specific years-of-experience thresholds mark the must-haves; "familiarity with," "a plus," and long laundry lists of tools near the bottom mark the nice-to-haves. Write the must-haves down as a short list. That list is what the rest of the loop maps against — not your résumé's existing structure, not what you personally think is impressive.
This ordering matters more than it sounds like it should. Starting from your résumé and asking "what can I tweak to fit this job" tends to produce small, surface-level edits — a swapped word here, a reordered bullet there — because you're anchored to whatever structure you already have. Starting from the posting and asking "what does this role actually need, and where does my history already show it" produces a different, more accurate result, because you're building the mapping in the direction the reader will actually use it: from requirement to evidence, not from résumé to justification.
Map every requirement to real experience
For each item on that must-have list, look through your actual work history for the bullet, project, or responsibility that already proves it. Most of the time it's there, just phrased differently or buried lower than it should be. Pull it up, note which job it lives under, and move to the next requirement. When a requirement doesn't map to anything in your history, that's a gap — not a prompt to write something that sounds close enough. A gap is information you'll act on in a later step, not a blank to fill in with invented experience.
It helps to do this mapping as a literal list rather than trying to hold it in your head — one line per requirement, with either the matching bullet next to it or the word "gap." Seeing the full list laid out this way does two things at once: it shows you exactly which parts of your existing résumé are actually relevant to this posting (often a smaller fraction than you'd guess), and it turns the vague anxiety of "am I qualified for this" into a short, concrete list you can act on one line at a time.
Rewrite bullets in the posting's language
Once you know which of your existing bullets map to which requirements, rewrite those bullets using the posting's own terms — but only where the accomplishment underneath is genuinely yours. If the posting says "stakeholder management" and your bullet already describes coordinating with three departments on a launch, "stakeholder management" is an honest, more legible way to say the same true thing. Keep the parts that make a bullet strong regardless of phrasing: a concrete action verb and a measurable result. Matching language is a translation, not an invention — the underlying fact doesn't change, only the words a hiring manager's eye catches faster.
Resist the urge to match language on bullets that don't actually support it. If a posting emphasizes "data-driven decision making" and your work involved some light reporting but nothing you'd call rigorous analysis, forcing that exact phrase onto the bullet creates a claim your interview answer won't back up. The rewrite step should only ever tighten the connection between a true accomplishment and the words that describe it — never stretch a true accomplishment to imply something bigger than it was.
Decide what to do with the gaps
Every gap you found earlier needs an explicit decision, not silence. Some gaps are worth closing before you apply — a short course or a weekend project that gets you honestly over the line on something central to the role. Some are better reframed truthfully: you haven't used the exact tool named, but you've done the underlying task with a close substitute, and saying so plainly is more credible than pretending otherwise. And some gaps are best left off the résumé entirely rather than papered over with vague language that invites a follow-up question you can't answer well. For the full decision framework on which path fits which kind of gap, see handling skill gaps honestly.
Check honest coverage before you send
Before you export anything, read the match score and the specific gaps named alongside it — not as a vanity number, but as a checklist. A score that looks high because it's quietly ignoring a requirement you don't meet doesn't help you; it just delays the moment an interviewer finds the same gap live. The useful version of a match score names what's missing as clearly as what's covered, so you can make the same close/reframe/drop decision on each one before you hit send, not after a recruiter calls.
This step is also where it's worth re-reading your rewritten bullets against the posting one more time, specifically checking for anything that reads slightly stronger than what you actually did. It's a quick pass, but it's the last checkpoint before the résumé leaves your hands, and it's much cheaper to soften a line now than to walk it back out loud in an interview.
Export one clean page
The last step is formatting, and it should take no thought at all: one page, single column, standard headings, selectable text — a layout a parser reads correctly and a recruiter reads in seconds, exported as PDF or DOCX depending on what the application asks for. If you're doing this loop for more than one posting in a sitting, the full end-to-end version — from paste to export — is laid out in the minutes-per-posting loop.
Run this loop a handful of times and it stops feeling like six separate steps and starts feeling like one motion: read the posting, map it against what you've already done, phrase the overlap honestly, decide on the gaps, check the coverage, export. The résumé changes every time. The process underneath it doesn't have to.