Career and jobs
How to Use Claude for CV Writing
CV writing is a sequence of decisions, not one request for a finished document. Claude can help structure real experience and remove repetition, but the source notes, facts and final approval remain yours.
GPTPrompts.AI Editorial
Hands-on with Claude; every method here is one we use · Last updated September 2026
01 · Reality check
What Claude actually does well here
Good at
- Turning notes into a writing sequence
- Drafting evidence-led wording
- Removing repetition
- Comparing a CV with a role
- Producing change logs
Not the right tool for
- Knowing which claims are true without records
- Guaranteeing interviews or ATS outcomes
- Replacing local advice
- Choosing sensitive disclosures
- Writing credible evidence from a blank prompt
02A · Working notes
Start with a writing brief
Define the reader, opportunity, decision, format, length, tone and evidence priorities. Ask Claude to convert that brief into an outline and clarifying questions before prose. ‘Make me stand out’ is not a useful constraint; ‘make evidence of project delivery easy to verify for this role’ is.
If an application asks for publications, teaching and service, those requirements should shape the outline. If it asks for a one-page industry document, they may need a different treatment. The opportunity sets the structure, not the model's default template.
Turn notes into evidence units
Give Claude one experience at a time: situation, task, action, tools, people involved, constraints and outcome. Ask it to return facts unchanged, missing questions and several bullet options. This separates fact discovery from writing.
Do not solve missing evidence with adjectives. If you remember that a process improved but not the percentage, find the record or use a precise qualitative result. If a team did the work, state your contribution. This produces language you can defend.
Draft the summary from proof
Ask for summary options only after the evidence matrix exists. Require every sentence to point to supplied experience and reject claims of expertise, seniority or results you cannot substantiate. A summary is a signpost, not proof.
Remove it temporarily and ask whether the bullets still support the same story. If they do not, improve the evidence or change the summary. Keep it short enough that it does not bury the work.
Use skills as an index
Compare the target description with tools, methods and knowledge you actually used. Put supported skills in a compact index and demonstrate important ones in the experience section. Do not make the list a keyword wall or claim proficiency from brief exposure.
Ask Claude to narrow broad terms. ‘Data analysis’ might mean spreadsheet reporting, SQL or statistical modelling. Specific wording helps only when it remains true and interviewable.
Edit for voice and meaning
Give Claude samples of your professional writing when voice matters. Ask it to match directness and vocabulary while preserving facts, then return before-and-after text, a change log and a meaning audit.
Watch for team contributions becoming individual leadership, support becoming ownership, exposure becoming expertise and plans becoming outcomes. Ask for concrete verbs and shorter sentences, not a more impressive tone.
Tailor a controlled copy
Keep one master CV and create a named copy for each meaningful application. Ask Claude to propose only evidence-alignment changes, accept them one by one and record the role, date and sections changed.
Compare the tailored copy with the master after each substantial pass. Repeated AI editing can introduce drift in dates, titles and numbers. Never let a generated version replace the verified master without review.
Handle gaps, privacy and disclosure
When the matrix shows a gap, classify it as absent evidence, adjacent experience, transferable skill or a requirement needing clarification. Decide whether to add real evidence, explain it elsewhere, train for it or leave it unclaimed. Do not let Claude turn adjacency into equivalence.
Share only the personal data the task needs, use placeholders during drafting and follow the relevant employer, university or professional policy. Keep a record of how the tool was used and disclose assistance when required.
Turn feedback into decisions
Classify each suggestion as factual correction, missing evidence, clarity, format, local convention or preference. Factual changes need records; preferences are optional. Ask Claude to flag certainty changes such as ‘helped’ becoming ‘led’ or ‘associated with’ becoming ‘caused’.
If a human reviews the CV, use Claude afterward to group comments rather than overrule them. Save the accepted version and stop editing once it passes the checklist.
Run the final three-document check
Compare the CV with the fact bank, target description, application instructions and any cover letter or profile. Check titles, dates, tools, publications, numbers, links and responsibility. Then inspect the exact exported file as selectable text, including reading order and page breaks.
The final human pass is where you catch a detail that could undermine an otherwise strong application. A clean ending and version record are part of good CV writing.
02 · The method
Step by step
- 1
Write the brief
Define the reader, opportunity, format, length and evidence priorities.
- 2
Build evidence units
Supply real notes and identify missing proof before drafting.
- 3
Draft in passes
Create outline, summary, experience and skills sections separately.
- 4
Edit for meaning
Compare versions and keep your own voice.
- 5
Tailor a copy
Change emphasis while protecting the master CV.
- 6
Check and approve
Verify facts, policy, consistency and the exported file.
03 · Use this now
Copy-paste prompt for CV writing
Help me write a truthful CV in stages. Never invent or upgrade a title, date, employer, qualification, publication, tool, metric or achievement. If evidence is missing, write [VERIFY]. Reader and target opportunity: [PASTE]. Format and length: [PASTE]. Source notes: [PASTE]. First return a brief, evidence matrix, outline and questions. After I approve, draft sections separately. Include a change log and meaning audit for every rewrite.
04 · Avoid these
Common mistakes
- Starting with a blank prompt
- Using adjectives instead of evidence
- Allowing rewrites to change facts
- Making skills a keyword dump
- Hiding uncertainty
- Skipping the final file check
05 · Questions
Frequently asked questions
What is the best Claude CV prompt?
Define the reader, opportunity, format, source notes and non-invention rule, then request an outline and evidence matrix before prose.
Can Claude make my CV professional?
It can make it clearer and more specific. Give voice examples and require a meaning audit so polish does not become exaggeration.
How many versions should I make?
Keep one verified master and focused copies for genuinely different roles. Record changes and never replace the master without review.
Is using Claude dishonest?
Policies differ. Keep claims yours, follow instructions and disclose assistance when required.
Related guides
Primary sources
Product menus and plan limits change. The linked vendor documentation is the authority when your screen differs.