How to Tailor a Resume to a Job Description

Everybody knows they should tailor their resume. Almost nobody does it, and the reason is a misunderstanding: people think tailoring means writing a new resume for every job. Framed that way, it's obviously not worth it — you'd spend two hours per application, and you have forty applications to send.

So here's the reframe. A recruiter's first pass over your resume takes somewhere around six seconds, and in those six seconds they are scanning the top third of page one for evidence that you are plausibly the person in the job description. Tailoring is the act of making sure the right evidence is in that space. It is a sorting operation, not a writing operation. And sorting is fast.

Why does everything start with a master resume?

You cannot select from a set you haven't built. The master resume is a private document — three, four, six pages, it doesn't matter, nobody will ever see it — that contains every role, every project, every tool, every number you have ever been able to claim.

Under each role, write six to ten bullets rather than the three you'd actually send. Include the small stuff. Include the internal tool nobody's heard of. Include the thing you did once for a quarter that turned out to matter. It'll feel bloated and self-indulgent, which is exactly right: this is a warehouse, not a shop window.

How do you read a job description properly?

Job descriptions are badly written, and part of the skill is knowing what to ignore. There's a structure hiding in almost all of them:

Read it once and write down the three things this job is really about. Not fifteen keywords — three things. If you can't name them, you don't understand the role well enough to tailor for it, and no amount of keyword matching will save you.

What are the four edits that do all the work?

1. Rewrite the summary — this is 80% of the value

Your summary is the only part of the resume guaranteed to be read. Two lines, and they should read as though written for this job specifically, because they were.

Experienced software engineer with a passion for building great products
and a track record of delivering high-quality solutions.

Backend engineer, 6 years, focused on payments and high-throughput APIs.
Built the ledger service behind ~40k transactions/week and cut checkout
failures by a third. Comfortable owning PCI-scoped systems end to end.

2. Re-order the bullets inside each role

Don't rewrite them — re-order them. Whichever of your true bullets speaks most directly to those three things you identified goes first. People read the first bullet of each role and skim the rest, so bullet one is prime real estate and it should change between applications.

3. Re-order the skills

Your skills list is scanned, not read. The first four or five entries are the ones that register. Put the role's core stack at the front, and drop the entries that are irrelevant to this job — a long list dilutes the ones that count.

4. Match the vocabulary

If the job says customer success and you wrote client servicing, use theirs. If they say observability and you wrote monitoring, use theirs. This is not keyword stuffing; it's speaking the same language as the person reading. You are describing the same real work — just in the words they'll recognise.

Tailoring is not making yourself look like a different person. It's making sure the person you already are is legible in six seconds.

What should you never change?

• Job titles. Adjusting a title to match the posting is the most common resume lie, and it is checked during reference and background checks. If your official title was misleading, keep it and clarify in the bullet.
• Dates. Ever.
• Facts, numbers, scope, or team size. Emphasis is legitimate. Invention is not, and it collapses in the interview.