A resume that gets zero replies is usually not about a lack of experience — it is about wording: vague phrases instead of results, duties instead of achievements, text that never makes it through automated screening. Below are seven Claude prompts that cover the whole cycle — from the resume itself to the message you send a recruiter. All of them in full, nothing trimmed.
Why a specific prompt beats "make it better"
"Improve my resume" gives the model no criterion: it has no way to know what counts as an improvement. The prompts below instead specify a concrete outcome — strong verbs, measurable numbers, a format applicant tracking systems (ATS) can read — plus a boundary ("no exaggeration", "stay honest") so Claude does not start embellishing your experience.
Prompt 1 — a resume that gets through ATS
The criterion: strong action verbs, measurable results, a format applicant tracking systems can parse.
Here is my resume: [paste text].
Rewrite it to maximise interview invites:
strong verbs, measurable results,
ATS-friendly format. No exaggeration.
Prompt 2 — a resume tailored to one specific job
You give it the job posting and your resume — Claude finds the missing keywords and works them in honestly, without distorting your actual experience.
Job posting: [paste]. Resume: [paste].
Find the missing keywords
and work them into the resume honestly,
without distorting my experience.
Prompt 3 — experience bullets built on results, not duties
A recruiter should see impact, not a list of functions. This prompt rewrites bullets in a "result" format with a length cap.
Rewrite these resume bullets: [paste].
Focus on the result, not the task.
Each bullet — no longer than 2 lines.
Prompt 4 — a cover letter with no boilerplate
The goal is a short letter that reads as written by a human for this specific role, not as a one-size-fits-all template.
Write a cover letter
for this job: [paste description].
Short, human, specific —
no boilerplate phrases or cliches.
Prompt 5 — a recruiter message that actually gets replies
The point of the message is not to ask for a favour but to spark interest with specifics: short, to the point, with a clear reason for writing right now.
Job posting: [paste]. Write a short
message to the recruiter on LinkedIn —
one that sparks interest and gets a reply,
rather than asking for a favour.
Prompt 6 — roles that are easy to miss
Based on your experience and skills, Claude can suggest job titles that would never occur to you in a self-directed search — simply because they are called something else.
My experience and skills: [paste].
List 10 roles I am a fit for
but might have missed while
searching by job title.
Prompt 7 — a search strategy instead of scattershot applications
Blasting the same resume everywhere with no strategy usually produces a low response rate. This prompt asks not for a rewrite but for a plan: how many applications to send, how to adapt the resume, and when to follow up.
My experience and target roles: [paste].
Suggest an application strategy: how many
jobs per week, how to adapt the resume,
when and how to follow up.
How to run the prompts in order
They work as one conversation rather than in isolation: first the ATS resume (prompt 1), then tailoring to a specific job (prompt 2), then sharpening the experience bullets (prompt 3) — that is the base you reuse. Prompts 4-5 (cover letter and recruiter message) go per individual job. Prompts 6-7 are for occasional use, so your search does not narrow down to only the roles that came to mind first.
How we do it
The qvib.pro knowledge base has a dedicated section of prompts for career and resume tasks — no invented response-rate statistics, just working formulations with a clear success criterion. The same principle, "a concrete criterion instead of a vague request", is what our engine for generating sites and code is built on.
Related links
- The "Prompts" section of the arsenal: qvib.pro/arsenal/prompts/
- The "Claude skills" section: qvib.pro/arsenal/skills/
- How the qvib engine works: qvib.pro/