How to tailor your resume to a job description

What tailoring is, and what it is not

Tailoring means adjusting the resume you already have so that one specific job is easy to see in it. It is not rewriting your career, and it is not adding whatever the posting asks for.

Most of the work is selection and wording. You decide which of your real experiences go first, which get shorter, and which words describe them. The facts do not change. The emphasis does.

The test for every change is the same: could you tell the story behind this line in an interview, for two minutes, without preparation? If not, the line does not go in. Everything below is a way of applying that test methodically.

Step 1: read the posting for requirements

Read the posting twice. The first time, mark everything that reads like a requirement: tools, years, domain, languages, certifications, and the tasks the role does day to day. The second time, sort those marks into three piles: must-haves, nice-to-haves, and company description you can ignore.

Repeated words matter. If "stock reconciliation" appears three times, the recruiter will search for it and expect to see it. The verbs matter too: coordinate, own, report. They tell you what the role is measured on.

Here is the posting we will use for the rest of this guide. It is fictional, and so is the candidate.

Operations Coordinator at Northline Supply. Coordinate daily order flow between the warehouse, carriers and customer service.
Own the weekly stock reconciliation and report discrepancies to finance.
3+ years in logistics or e-commerce operations.
Hands-on experience with NetSuite (required).
Comfortable with spreadsheets and basic reporting.
German at B2 or above is a plus.

Step 2: write down your evidence before you touch the resume

The candidate is Maya. She has worked two years and eight months as an Order Coordinator at a furniture retailer. Her current resume describes the role in three bullets: "Responsible for processing customer orders and handling shipping issues." "Helped with inventory counts." "Worked with the warehouse and customer service teams."

Before changing a word, she writes down what she actually did, in plain language, with only the details she knows for certain. This is the step most people skip, and it is where all the honest material comes from.

Around 120 orders a day in a normal week. I checked a monthly export from the ERP once, so this is a measured figure, not a guess.
Every Friday I did the stock count with the warehouse lead and posted the differences to the finance team in a shared spreadsheet.
I built the Excel tracker for delayed shipments. Customer service used it to answer where-is-my-order calls.
The ERP was SAP Business One. I used it daily for orders, stock levels and returns. I have never opened NetSuite.
No German. I took one evening course years ago and remember almost nothing.

Step 3: map every requirement to a piece of evidence

Now put the two lists side by side. For each requirement, write down where it is proven and mark it met, partly met, or not met. This takes ten minutes, and it removes the guesswork from everything that follows.

Coordinate daily order flow between warehouse, carriers and customer service. Evidence: around 120 orders a day, two parcel carriers, the customer service team. Met.
Own weekly stock reconciliation and report discrepancies to finance. Evidence: the Friday count with the warehouse lead, differences posted to finance. Met.
3+ years in logistics or e-commerce operations. Evidence: two years and eight months at the retailer. Partly met.
Hands-on experience with NetSuite. Evidence: none. SAP Business One daily, for the same kind of work. Not met.
Comfortable with spreadsheets and basic reporting. Evidence: the delayed-shipments tracker, the weekly finance sheet. Met.
German at B2 or above. Evidence: none. Not met.

What the map tells you

Three met, one partly, two not met. That is a normal result for a role worth applying to. A resume that meets every line usually means the person is overqualified or the posting is vague.

The map also shows where to spend the writing effort. Two requirements are met but currently sit behind weak bullets; those are the lines that will move the resume. The requirements she does not meet are a separate decision, covered further down. Notice what her notes contained: a number with a source, the names of systems she really used, and two plain admissions of what she does not have. All three kinds are useful.

Step 4: rewrite the bullets the evidence supports

Maya rewrites three bullets. Each new line uses the posting's words where they describe the same work, and contains nothing that is not in her notes.

Before: "Responsible for processing customer orders and handling shipping issues." After: "Coordinated daily order flow for around 120 orders a day between the warehouse, two parcel carriers and the customer service team."

Before: "Helped with inventory counts." After: "Ran the weekly stock reconciliation with the warehouse lead and reported discrepancies to finance in a shared spreadsheet."

Before: "Worked with the warehouse and customer service teams." After: "Built an Excel tracker for delayed shipments that customer service used to answer delivery questions."

Three things changed. The verbs now say what she did rather than what she was near: coordinated, ran, built. The posting's own terms appear where they are accurate: daily order flow, stock reconciliation, discrepancies. And every detail traces back to a note. The 120 orders came from an export, the warehouse lead was a real person, the tracker was hers.

Three things did not change. The number did not become 150 because it sounded better. The weekly count did not become "led inventory management". The tracker did not gain a result she never measured, such as "cut call handling time by 30%". The new lines are shorter on adjectives and longer on facts, which is what a recruiter in the field will notice.

What to do with a requirement you do not meet

Two of the six requirements are not met and one is short. There are four honest options. Which one fits depends on how hard the requirement is.

Show the adjacent evidence. Maya cannot claim NetSuite, and she should not add it to a skills list on the theory that all ERPs are alike. She can show what she has, plainly: "SAP Business One, daily use for orders, stock and returns, 2.5 years." A recruiter who needs any ERP experience will read that and move on. A recruiter who needs NetSuite specifically will not, and that is the correct outcome for both of them.

State the real figure. For the three years, she writes her true start and end dates. Two years and eight months is close enough that a human will decide. Stretching the dates is the kind of change a reference call exposes, and it turns a near miss into a lie.

Leave it out. For German, she adds nothing. "Basic German" on a resume invites a question in German at the interview. A plus she does not have is simply absent from the page.

Address it elsewhere, or move on. When the gap is the one requirement the posting marks as required, the cover letter is the place to say so in one sentence and point at the closest thing you have. If that still feels thin, the honest answer may be to skip this posting and spend the hour on one where the map shows more met lines.

The rule behind all four: a requirement you do not meet is a decision about where to apply, not a writing problem to solve with better phrasing.

After you tailor

Read the tailored resume the way a recruiter does, in thirty seconds. Is the role obvious from the top third? Do the first bullets of the latest job match the posting's first requirements? Is the contact information visible? Then read it as the interviewer: pick any line at random and tell its story out loud.

Keep the tailored file under the company's name. The next posting in the same field will reuse most of the mapping, and the notes from step 2 are the start of a personal evidence file that makes every later application faster.

Reorder bullets so the most relevant proof sits at the top of each role.
Mirror the posting's phrasing only where it describes work you actually did.
Add a tool to the skills line only if you have used it, not if you sat next to someone who did.
Shorten unrelated bullets rather than deleting your history. Gaps raise more questions than short lines.

How Verlane does this

Verlane runs the same steps, with the job description pasted into a chat and your resume already stored. The parts that matter for honesty are these.

The match score is a formula, not a model's opinion: keyword coverage against the posting plus a structural check of the resume. It is recalculated after every accepted edit, so you see the same arithmetic before and after.
The posting is read into a list of requirements, and each one is checked against your resume and your stored notes, which Verlane calls Mindbase. A requirement with no evidence becomes a gap, not a sentence.
Hard requirements it cannot find evidence for get a question, up to three per run, with the answers "yes, add it", "partly, in my words", or "no". A "no" is remembered for later postings, and nothing that claims that requirement goes into the result.
Every suggested sentence is checked against your own material before it reaches you. A sentence nothing supports is cut, or reduced to what the evidence actually says. It is not polished into something more convincing.
Edits arrive one at a time, with the before and after side by side. Nothing changes on your resume until you accept that specific line.
A cover letter and application answers come from the same thread and the same evidence, so the three documents cannot contradict each other.

What it would do with Maya

It would show the SAP Business One line, treat NetSuite as a gap, ask about it rather than guess, record her "no", and leave it out of every document. The three rewritten bullets above are the kind of edit it would propose, each with the original beside it. What it would not do is make her a NetSuite user. That is the whole point.