jobbee.io

How to tailor your resume to a job description, without inventing anything

To tailor your resume to a job description, list the posting's must-have requirements, find real evidence for each one in your work history, and move that evidence into the top third of your resume in words the posting would recognize. Change the order, the emphasis and the wording, never the facts: employers, titles and dates stay as they are, and every line still describes something you did.

Most guides on this stop at "mirror the keywords." That's the easy half. The useful half is finding the evidence: the project you cut for space, the result you never wrote down, the tool you used in a role two jobs back. This guide is the full procedure: six steps, a before-and-after example, and what to do when the evidence isn't there. If you're still deciding whether a posting needs tailoring at all, read our guide on when to tailor first.

§ 01

Before you start

Before you start: keep a full record of your work

You can only tailor from what you can find. Before your first posting, write down everything you've done in one place: every project, what you owned, what changed because of it, and any number you can prove. Include the work that never made it onto your resume. Every tailored version of your resume starts from that record.

A project is any substantial piece of work, in your job or outside it: a feature you took from requirements to production, a migration, a launch, a deal, a campaign, and personal, academic and open-source projects too. If it took weeks of your work and ended up as one bullet on your resume, it deserves its own entry in your record.

You'll draw on this record in step 3.

§ 02

The six steps

The six steps: from the posting's must-haves to the top of your resume

You need the posting, your full record, and the resume you'd normally send.

  • 1Pull the must-haves out of the postingCopy the requirements the posting marks as required, lists first, or repeats. Keep the nice-to-haves in a second list. Rewrite each must-have as a short phrase: "SQL", "owned a product launch", "managed a team of 5+". The result is usually a short list.
  • 2Find the posting's words for each oneNote the exact term the posting uses ("stakeholder management", "Kubernetes", "pipeline generation"). You'll use those words only where your experience genuinely matches them.
  • 3Find your evidence for each must-haveGo to your full record, not your current resume. For each must-have, write the strongest real example: what you did, where, and what changed. Mark each one found (you have it), related (you've done something close), or none (you have nothing for it).
  • 4Move the evidence to the top thirdThat's the part a reader sees first: your summary, your skills line and the first bullets under your most recent roles. Lead the summary with the two or three must-haves this posting cares most about. Put the posting's key skills first in your skills line. Under each recent role, move the bullet that proves a must-have to the top.
  • 5Rewrite each bullet to show what changedEach bullet says what you owned, what you did and what changed because of it. Use the posting's term where it's accurate. A duty like "Responsible for reporting" tells the reader nothing. A result shows them you can do what they need.
  • 6Check every line against the recordFor each edited line, ask: could I explain this in an interview, with the details? If not, cut it. Employers, titles and dates never change. Then reread the top third against the must-have list: every found item should be visible there.

§ 03

Worked example

Worked example: one posting, before and after

One hypothetical posting: Product Marketing Manager at a B2B software company. Its four must-haves: launched products end to end, customer research and win-loss, sales enablement, and messaging and positioning.

Must-havePosting's wordsEvidence in their recordStatus
Launches"owned go-to-market launches"Led the launch of a reporting add-on in their current role: launch page, sales briefing, announcement emailFound, but buried in bullet 4
Research"win-loss analysis"Ran 12 customer interviews after a lost-deal streak; findings went into the next quarter's roadmap reviewFound, but only in their notes
Enablement"sales enablement"Wrote the battlecards and objection notes the sales team used against their main competitorFound, but worded as "created documentation"
Positioning"messaging and positioning"Rewrote the pricing-page copy one time, small scopeRelated

Before, the top of their current resume:

Marketing Manager, 2022–present

  • Responsible for content calendar and blog
  • Created documentation for sales team
  • Supported website updates
  • Managed launch of reporting add-on

After, the same role with the same title and dates:

Marketing Manager, 2022–present

  • Owned the go-to-market launch of a reporting add-on: launch page, sales briefing and the announcement email
  • Ran win-loss analysis: 12 customer interviews after a run of lost deals; findings went into the next quarter's roadmap review
  • Built the sales enablement kit (battlecards and objection notes) the sales team used against our main competitor
  • Rewrote the pricing-page copy
  • Ran the content calendar and blog

What changed: the launch moved from bullet 4 to bullet 1. The customer interviews came out of their notes. "Created documentation" became "sales enablement kit", the posting's term, because that is what the work was. The pricing-page rewrite stays a short, plain line because it was a small piece of work. What stayed the same: the title, the employer and the dates. Nothing was added that didn't happen. (This example is hypothetical, written for teaching. It isn't a real person's resume, because we don't publish those without permission.)

§ 04

Gaps

When the evidence isn't there

Step 3 marks each must-have found, related, or none. Here's what to do when it isn't found.

  • Related, not foundDescribe what you actually did, plainly, in your own words. Let the reader decide how close it is. Don't relabel it with the posting's term.
  • NoneLeave it off. Anything on your resume can come up in the interview, and a claim you can't back up will show there.
  • Most must-haves have no evidenceIt's a stretch application. Decide whether to send it anyway, or spend the time on a posting where you have the experience and only need to bring it to the top.

Before you send a tailored version, check it with the six questions in our guide on tailoring vs keyword stuffing.

§ 05

Mistakes

Mistakes that undo the work

  • Pasting the posting's keyword list into a skills section with nothing behind it.
  • Changing a job title to match the posting. Titles stay what they were.
  • Tailoring only the summary and leaving the bullets generic.
  • Tailoring from your current resume instead of your full record: the best evidence is often the part you cut.
  • Keeping one "tailored" version per job title. Two postings with the same title can ask for different must-haves (see an example).

§ 06

Jobbee

Where Jobbee fits

Jobbee (jobbee.io) is our product, so read this section as the maker's description. Jobbee follows the same rule for every posting it tailors for: it checks the posting's requirements against the history you've given it.

  • It reads the posting's requirementsIt counts how many of them your history covers, shown as a score like "Requirements covered: 4/6", and names each gap in plain words. See how a match shows its work.
  • It tailors one resume for that postingFrom your real history, leading with the work that posting asks for.
  • Every line traces back to your historyIf something is missing, it is reported, not filled in. It won't invent experience or alter employers, titles or dates. One known gap: when your files say nothing about a few preferences, such as visa status, Jobbee can still assume an answer. In the next release, it will ask you a question instead.
  • It finds the roles, or takes one by linkIt finds matching roles against the target roles, locations, and seniority you set, or takes a specific posting by its link. If a posting you bring is out of reach, Jobbee tells you up front instead of tailoring for it, and shows how many of its must-haves your profile covers.
  • You review it, and you submitEach tailored resume arrives in your inbox with the job link.
  • A worked example on real filesThis guide’s example is hypothetical. Our open-source examples repository holds real Jobbee runs. Each one puts a fictional person’s workspace next to a real job posting and the resume Jobbee wrote for it, with notes on what to compare. Open-source examples on GitHub.

§ 07

Questions

Questions people ask

How do I match my resume to the job requirements?
List the posting's must-haves, find real evidence for each one in your work, and put that evidence in the top third of your resume in the posting's words where they fit. A requirement without evidence stays off.
Should I copy the exact wording from the job description?
Use the posting's term where your experience genuinely matches it, so the reader recognizes it at a glance. Don't copy phrases you can't back up with something you did.
Which parts of my resume should I change for each job?
Start with the top third: the summary, the skills line and the first bullets of your recent roles. Change only as much as it takes for your evidence to show there. Sometimes that's reordering two bullets; sometimes it's swapping in a project you'd cut. The facts never change.
What should I do if I don't meet every requirement?
Show what you do have, plainly, and leave the rest off. Postings often list more than any one candidate has. What hurts you is a must-have you do have but left buried, or one you claimed and can't explain.
Do I need a different resume for every application?
Only when the must-haves differ. Run the check in our guide on when to tailor: if every must-have already shows at the top, send it as it is.

Written by the Jobbee team, October 2026.

Start free — 3 tailored resumes a day Free tier, no credit card.