Tailoring, honest keywords and the memorable line

The previous lesson made each line stronger on its own. This one aims the whole page at a particular job and a particular reader.

Three tools do that. Tailoring reorders and rewords your master resume for one application. Keyword work makes sure you are found, without tricks that lose you the human read. And the memorable line gives the people who read you a sentence to repeat when they pass you on.

Tailoring to a job description

Tailoring is the highest-return thirty minutes you can spend on any single application, and it has a procedure.

The procedure

Step 1 — Read it twice. The first read tells you what the job is. The second, with a pen, tells you what it prioritises. Requirements listed first, and repeated in different words, are the ones that matter.

Step 2 — Extract the top five. Not fifteen. Job descriptions are usually written as wish-lists; five is roughly how many actually drive the screen.

Step 3 — Mark yourself against each. Strong, partial, or absent. Be honest — this is a planning document, not a claim.

Step 4 — Reorder. Move bullets so your strong matches sit in the top third of page one. Within a role, bullets do not have to be chronological, so order them by relevance to this job.

Step 5 — Reword to match vocabulary. If the job description says "observability" and your resume says "monitoring and alerting", use their word — provided it is honest. Different words for the same thing cost you both search matches and reader recognition.

Step 6 — Cut. Tailoring adds emphasis, and something has to leave. The bullets about work irrelevant to this role are the ones to shorten or drop.

Step 7 — Re-check. Length, and the six-second test from Section 9.

What tailoring is not

It is not rewriting your resume from scratch for every application — that is unsustainable and you will stop doing it after six applications.

It is a reordering and rewording pass on a master resume, and it should take about thirty minutes once you have done it a few times.

The gaps you find

Step 3 will show you requirements you do not meet. That is useful in two ways: it tells you whether to apply at all, and it tells you what to prepare to discuss if you do.

A role where you are strong on four of five is worth applying to. One where you are strong on one is usually not, however appealing it looks.

Keywords, honestly

Step 5 of tailoring is a form of keyword work. Keyword advice is where a lot of resume guidance goes wrong. Here is the version that works and does not embarrass you.

The legitimate version

Recruiters search the applicant database by technology name (see What an ATS actually does). If you have five years of Go experience and the word "Go" never appears, you will not surface in that search.

So the goal is: the technologies you genuinely know should appear, in the places they belong.

Where they belong:

1. Inside the bullet describing work you did with them. Strongest — it is evidence, not a claim.
2. In the skills section. Confirms and makes you findable.
3. In your job title or context line, where genuinely applicable.

What not to do

The vocabulary-matching version

The genuinely useful form of keyword work is not adding technologies — it is using the industry's word for what you did.

Same work, but the second column matches how recruiters search and how engineers describe their own field.

Where breadth belongs

If you want to be findable for a long tail of technologies, put them on LinkedIn. It is searchable, it has no length limit, and nobody screens you out for a long skills list there.

Keep the resume tight and defensible. Let the profile carry the breadth. LinkedIn alignment covers this split.

The one memorable line

Keywords get you found. What gets you remembered is different: every strong resume has a line that a reader repeats to someone else. It is worth finding yours deliberately.

Why it matters

Debriefs are conversations. When a recruiter forwards you to a hiring manager, or an interviewer mentions you to a colleague, they compress you into a sentence.

If you have supplied that sentence, it is the one they use. If you have not, they will improvise one, and improvised summaries are generic: "backend engineer, five years, seems fine."

What makes a line memorable

Three properties:

1. Specific. A number, a named system, or an unusual situation.
2. Consequential. Something changed that mattered.
3. Compact. One sentence a person can repeat from memory.

Examples:

• Took the checkout service from 3 payment incidents a month to zero over two quarters.

• First engineer on the platform team; it is now nine people and owns deploys for the whole company.

• Cut the nightly ETL from 6 hours to 40 minutes, which is why the reporting product could move to same-day data.

• Found and fixed a race condition that had been silently double-charging ~40 customers a month for two years.

None of these are exotic achievements. They are ordinary engineering work described so the consequence is unmistakable.

Finding yours

You almost certainly already have it — it is usually the story you tell friends about your job.

Ask yourself:

• What is the thing I did that I am actually proud of?
• What would have gone worse if I had not been there?
• What did I fix that had been broken for a long time?
• What did I start that still exists?

Take the answer, apply the impact-first structure, and put it in the top third of page one.