Tailored Cover Letter Writer for Claude
Paste a job posting and your experience; get a one-page cover letter that mirrors the role's language, proves three requirements with specific evidence, and sounds like a person, not a template.
Fill in the variables
Prompt
<role>
You are a career coach and former hiring manager who has read thousands of cover letters. You know that the ones that get interviews do three things: name the specific role, prove the top requirements with evidence, and sound like a human who wants this job rather than any job.
</role>
<context>
Job posting (full text):
{{job_posting}}
My background (resume bullets, projects, numbers — raw notes are fine):
{{my_background}}
Why I want this role or company (one or two honest sentences):
{{motivation}}
Tone: {{tone}}
</context>
<constraints>
- Maximum 320 words, four paragraphs, no bullet lists.
- Never open with "I am writing to apply for" or "I am excited to". Open with a sentence about the company's problem or the role's purpose.
- Every claim about me must map to something in my background. Do not invent experience, numbers or tools I did not mention. If the posting requires something I lack, do not mention it or address it in one honest clause.
- Mirror 3–5 key phrases from the posting naturally (the hiring manager pattern-matches on them), but never copy a full sentence.
- No adjectives about myself ("passionate", "results-driven", "detail-oriented"). Show it with a result instead.
- Plain language. No "leverage", "synergy", "utilize".
</constraints>
<goals>
- Make the reader think "this person understood the job" within the first two sentences.
- Prove the three most important requirements with one concrete example each.
- End with a specific, low-pressure next step.
</goals>
<instructions>
1. Read the posting and list, silently, the three requirements the employer cares about most (usually the first three bullets or the ones repeated).
2. For each, pick the single strongest piece of evidence from my background. Prefer numbers and outcomes over responsibilities.
3. Write the letter: paragraph 1 names the role and the company's need; paragraph 2 and 3 prove the requirements with evidence; paragraph 4 states why this company specifically, then the next step.
4. After the letter, add a short "Evidence map" showing requirement → the sentence that proves it, so I can check nothing is invented.
</instructions>
<output_format>
The letter first, as plain text with a greeting line ("Dear Hiring Manager," unless a name appears in the posting) and a sign-off with my name placeholder. Then the evidence map as three lines. Nothing else.
</output_format>
Example input
Job posting: "Customer Support Lead — Lumen (B2B SaaS, 40 people). You will own our support function: a team of 3, Intercom and Zendesk, a 2-hour first-response SLA. Requirements: 3+ years in SaaS support, experience managing or mentoring agents, strong written English, comfortable building help-center content, data-driven (CSAT, response times). Nice to have: experience with product feedback loops. We're a remote-first team that ships weekly." My background: 4 years at a project-management SaaS (Teamline). Started as support agent, became senior agent after 1 year, then "support lead" for a team of 2 from 2024. Cut median first response from 5h to 1.5h by introducing macros + a triage rota. Wrote ~60 help-center articles; ticket deflection went up about 20% after the help center relaunch. Ran a monthly "voice of customer" doc that product used for roadmap. Tools: Intercom, Zendesk, Notion, Metabase. CSAT 94% last year. Motivation: Lumen's changelog shows they ship every week; I like support teams that sit close to product, and a 40-person company means my work would actually show. Tone: direct and warm
Example output generated with Claude Sonnet 4.6 from the example input above
Dear Hiring Manager,
A two-hour first-response SLA with a team of three only holds if the queue is triaged before anyone touches a ticket. At Teamline I built exactly that: a triage rota and a macro library that brought our median first response from five hours to ninety minutes, and kept it there while ticket volume grew.
You are looking for someone who can lead agents, not just answer tickets. I have led a team of two since 2024 after moving up from agent to senior agent, and the part of the job I care most about is the feedback loop you mention as a nice-to-have. Every month I compile a voice-of-customer document from support conversations; our product team has used it to decide roadmap items, and I would want to do the same with Lumen's weekly releases.
Help-center content is where I have had the clearest measurable impact. I wrote about sixty articles for our relaunch, and ticket deflection rose roughly twenty percent in the quarter after it went live. Our CSAT finished last year at 94 percent. I work in Intercom and Zendesk daily and pull my own numbers from Metabase, so response times and CSAT would be on a dashboard, not in a slide once a quarter.
I want this role specifically because Lumen ships weekly and is small enough that a support lead sits next to the people building the product. If it would help, I can share the triage rota template and a sample voice-of-customer report before we talk.
Best regards,
[Your name]
Evidence map:
- Manage/mentor agents → "led a team of two since 2024 after moving up from agent to senior agent"
- Data-driven, SLA → "median first response from five hours to ninety minutes", "CSAT finished last year at 94 percent"
- Help-center content → "about sixty articles… deflection rose roughly twenty percent"
Why this works & how to customize
Why it works: hiring managers skim for two signals, "did they read the posting" and "can they prove it". The prompt forces the model to pick the top three requirements and attach one piece of evidence to each, then shows you the mapping so you can catch anything invented. Banning the standard opener and self-adjectives removes the template smell that gets letters discarded in the first five seconds.
How to customize: for a career change, add a line in motivation explaining the pivot in one sentence and the model will address it once, without apology. For creative roles, set the tone to "conversational, a little dry" and allow 380 words. If the posting names a person, the greeting adapts automatically. Keep your background notes honest and specific; the letter is only as strong as the numbers you give it.
How to customize: for a career change, add a line in motivation explaining the pivot in one sentence and the model will address it once, without apology. For creative roles, set the tone to "conversational, a little dry" and allow 380 words. If the posting names a person, the greeting adapts automatically. Keep your background notes honest and specific; the letter is only as strong as the numbers you give it.
Comments (0)
Sign in to comment.
No comments yet.