How to adapt one résumé to many jobs without rewriting it every time

The standard advice is to tailor your résumé to every job. The standard reality is that nobody does it, because rewriting a two-page document forty times is not a thing a human will sustain — and the version people do sustain, changing three keywords in the skills list, is not tailoring.

There is a middle path that works and costs about ninety seconds per application. It requires setting up properly once.

Step 1: write one master document you are not going to send

Your master résumé is longer than what you send. It contains, for each role you have held:

• Every project or workstream you owned, as its own bullet.
• Every number you can honestly attach to something: scale, volume, latency, revenue, team size, time saved, error rate.
• The technologies actually used, with the depth of your involvement.
• Anything that shows scope: what you decided, what you owned, who you worked with.

This is a private document. It might be four pages. It is a bank of material, and the point is that you never again have to remember what you did in 2023 while filling in a form at 11pm.

Step 2: define role families, not roles

Look at the jobs you are actually applying to. Almost everyone's search collapses into two or three clusters. For example:

• Product-facing frontend at small companies.
• Platform / infrastructure at mid-size companies.
• Full-stack generalist at very early-stage companies.

Or, in a different field:

• Performance marketing, in-house.
• Growth / lifecycle, in-house.
• Agency-side campaign management.

You build one sendable résumé per family — two or three documents, not forty. Each is a selection from the master, ordered for that family's priorities. The platform version leads with reliability, scale and systems; the product version leads with shipped features, users and collaboration with design.

If your families are so different that no résumé serves them (a data scientist also applying to engineering management), that is a real signal about your search rather than a formatting problem — and the answer is still separate documents, just more distinct ones.

Step 3: know which four things to change per job

Within a family, per-application tailoring is these four, and nothing else:

1. The headline / title line

The line under your name. Make it match the language of the posting: "Senior Frontend Engineer" if that is the title, not "Software Craftsman" or "Technologist". This is the single highest-leverage edit, because it is the first thing read, and because it decides whether a recruiter has to do translation work.

Never claim a title you have not held at the employer level — that belongs in the experience section, which is verified. The headline is a statement of what you are applying as.

2. The top two or three bullets of your most recent role

Reorder so that the bullets closest to the posting's core responsibility come first. Nothing else about the role changes. This is a reordering, not a rewrite, and it is why the master document exists.

3. The skills line

Include the technologies the posting names that you actually have, in the order the posting cares about them. Drop the ones irrelevant to this family. Do not add anything you would not want to be asked about for twenty minutes.

4. The summary sentence, if you have one

One or two lines at the top. Worth having if you are making a transition that needs explaining (changing domain, relocating, coming back from a break); worth cutting otherwise, because it usually says nothing.

What to leave alone

• Older roles. Nobody is reading your 2019 job that closely. Editing them per application is pure cost.
• Education, certifications, dates. Fixed facts.
• Formatting. One clean, single-column, parseable layout, everywhere. Fiddling with it per job introduces parsing risk for zero gain.
• Length. Two pages if you have more than about five years of experience, one if you have less. This does not change per job either.

Mirroring language without keyword stuffing

Postings are written by people, sometimes badly. Using their vocabulary helps because it removes translation work for the reader and because recruiters search the database using their own words.

The line between mirroring and stuffing:

• Mirroring: they say "observability", you have built dashboards and alerting, so your bullet says "observability" instead of "monitoring".
• Stuffing: they say "Kubernetes", you have never run it, so it appears in your skills list anyway.

The first is translation. The second is a technical screen you will fail, having spent three interview stages getting there.

A useful check: could you talk for two minutes about every term on your résumé? If not, cut it.

Where cover letters and open questions fit

This is the part that should be genuinely per-job — and it is cheap, because it is short. Two to four sentences that could only be about this company: something specific about the product, why the problem matters to you, and the one thing in your background that maps directly.

Effort spent here beats effort spent rewriting the résumé, by a wide margin. It is also the part most people skip, which is precisely why it works.

Making this survive contact with a real search

The system only holds if the per-application cost stays under a couple of minutes. Practically:

• Keep the master document and the two or three sendable versions in one place, with obvious file names.
• Name exported files consistently: Firstname-Lastname-Frontend.pdf.
• Keep a note of which version you sent to whom. When they call you three weeks later, you want to know which document is in front of them.
• Revisit the family versions every few weeks based on what is getting replies — not after every rejection.

The uncomfortable summary

Per-job résumé rewriting is mostly a ritual. It feels like effort, and effort feels like it should matter. What actually matters is applying to jobs you fit, getting the top third of the page right for that family of jobs, and writing two specific sentences where the employer asked a question.

Do those, and one résumé — in two or three versions — will carry an entire search.