Get Started
Chapter 28 min read

Applications That Do Not Read Like Everyone Else's

Cover letters are now trivially generated, which is exactly why generic ones fail harder than they used to. What specificity looks like and how to produce it quickly.

Every recruiter reading applications this year is reading a lot of fluent, well-structured, entirely interchangeable cover letters. Fluency has stopped being a signal — it is now the baseline, available to everyone in eight seconds.

What remains a signal is evidence that you looked at this particular organisation and thought about this particular problem.

The structure that still works

  1. One sentence on why this organisation, specific enough that it could not be sent to a competitor
  2. One paragraph on the most relevant thing you have actually done, with a result
  3. One paragraph connecting that to something they need — from the posting, their product, or a change they have announced
  4. One line on what you want and your availability

Four short paragraphs. Anything longer is read diagonally, and the parts you worked hardest on are the parts skipped.

Using AI without landing in the generic pile

The trick is to make it work on your material rather than produce material. Give it the raw facts and let it structure them; do not give it the job title and let it invent enthusiasm.

A brief that produces something specific

Write a four-paragraph cover letter using ONLY the facts below.
Invent nothing. If something important is missing, list what
you need instead of filling the gap.

Job: [paste the posting]

About the company that I actually noticed:
[one real thing — a product change, a market they entered,
something in their docs or their blog]

My most relevant work:
[what you did, what changed, the number]

Why I want this specifically:
[your real reason, in your own words, even if clumsy]

Tone: direct and plain. No "I am thrilled", no "passionate",
no "I believe I would be a great fit". Under 250 words.

Research that takes ten minutes and shows

  • Read the company's own blog or changelog, not the press coverage. One line about something they shipped beats three about their mission
  • Look at who you would work with and what they have written or built publicly
  • Read the posting twice — the requirement listed first is usually the one that matters most
  • Note what is missing from the posting. A gap you can fill is a stronger angle than a requirement you meet
  • Check whether they have grown, been acquired, or changed direction recently. It explains why the role exists

Volume is not the strategy it appears to be

It is now possible to send fifty applications in an evening, and the temptation is obvious. It is also the approach with the worst results — high volume applications are the ones that read as templates, and referrals and specific applications convert several times better than cold volume in every recruiter account of the last two years.

Ten thought-through applications beat fifty generated ones. That is not a moral point; it is arithmetic on response rates.

The follow-up nobody sends

A short note a week after applying — three sentences, referencing one specific thing about the role, no pressure — is unusual enough to be remembered. Use AI to make it brief and non-needy, not to make it longer.

What to take from this chapter

  • Fluent writing is now the baseline; specificity is the remaining signal
  • Four short paragraphs: why them, what you did, how it connects, what you want
  • If it could be sent to a competitor unchanged, it will be read as a template
  • Feed the model real facts and let it structure them — never let it invent enthusiasm or achievements
  • Ten researched applications beat fifty generated ones on response rate

Try it

Take a role you actually want. Spend ten minutes on their blog or changelog and write one true sentence about something they built. That sentence is your opening line, and almost nobody else applying will have one.