Career and jobs
How to Use Claude to Create a CV
A CV is a record of evidence, not a creative writing exercise. Claude can organise a messy career history, map it to a role and improve clarity, but it should never fill gaps or inflate responsibility.
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
- Evidence inventories
- Requirement mapping
- Clear bullet alternatives
- Finding repetition and ambiguity
- Final checklists
Not the right tool for
- Inventing evidence
- Predicting ATS outcomes
- Knowing local conventions without instructions
- Replacing a human reviewer
- Deciding what confidential information to disclose
02A · Working notes
Build a verified fact bank
Collect employers, official titles, dates, qualifications, projects, publications, presentations, awards, tools and outcomes in one source document. Keep the wording plain and add a source note beside important numbers. Ask Claude to return an inventory of supplied facts, missing evidence and questions before it drafts. If a later bullet contains a detail that was not in the inventory, trace it to your records or remove it.
Separate your master CV from each application copy. The master is the source of truth; a tailored copy changes emphasis and order, not your history. This prevents a model from deleting a publication, changing a date or turning a short resume into an unsuitable academic dossier.
Read the opportunity before choosing the format
CV and resume can mean different things by country and field. Extract the actual instructions: document type, length, required sections, file format, naming convention and disclosure rules. Ask Claude to list these constraints and identify what the reader needs to decide. Academic and research applications may need publications, teaching and service; an industry application may need a short evidence-led resume.
Do not rely on a generic template. A neat document in the wrong format is still a weak application. Ask for a section order that follows the instructions and keeps the most relevant verified evidence easy to find.
Map requirements to evidence
Paste the complete job, programme or fellowship description and ask for a requirement-to-evidence matrix. Each row should contain the requirement, exact supplied evidence, proposed section and SUPPORTED, PARTIAL, MISSING or UNCLEAR status. This is safer than asking for keywords because it exposes gaps instead of hiding them.
If a requirement is missing, decide whether you have a real example, should explain adjacent experience, need training or should leave it unclaimed. Claude can ask useful recovery questions, but only your records can answer them. Never let an adjacent skill become an equivalent qualification.
Write specific bullets without changing ownership
Give Claude the original note, your action, the object of the work, context, people involved and verified result. Ask for options that preserve actor, scale, time period and certainty. ‘Coordinated’ is not automatically ‘led’; ‘contributed to’ is not ‘delivered’; exposure is not expertise. Use [ADD VERIFIED RESULT] rather than a plausible number.
Request a meaning audit between the original and rewrite. Keep the version you can explain in an interview, and keep the original note beside it. A credible bullet makes the action and evidence visible without turning team work into an individual claim.
Use readable structure and check the export
A simple single-column document with conventional headings and selectable text is a sensible default unless the application says otherwise. Avoid graphics, rating bars, dense columns and essential information in images. Ask Claude to review the text, but inspect the actual PDF or document after export.
Copy the exported text into a plain editor, check reading order, page breaks, dates and contact details, and open it in another viewer. This cannot guarantee an employer's parser, but it catches broken text and layout before submission.
Protect personal and confidential information
A CV contains personal data and may contain employer or client information. Remove unnecessary addresses, identity numbers, private contact details and confidential project names before uploading. Use placeholders while drafting and use an account approved for the material. Anthropic's document and style guidance is the authority for current product behaviour, but account controls still matter.
Keep the fact bank, opportunity, tailored file, change notes and submitted version together. Record which version you sent and when, then delete temporary uploads when appropriate.
Use feedback as a checklist, not a prediction
Ask Claude to review unclear evidence, repetition, unsupported claims, inconsistent dates and phrases that sound inflated. Require section references and concrete fixes. Do not treat an ATS score or match percentage as a hiring prediction. Run a fact pass against the source, a fit pass against the opportunity and a reader pass asking whether a busy reviewer can understand the evidence quickly.
If another person reviews the CV, ask them to separate factual corrections from preferences. You decide which changes to accept. The final document should sound like a precise version of you, not like generic model output.
Run a final claim audit
Compare the CV, cover letter, application form and profile against the same fact bank. Check titles, dates, employers, locations, tools, publication names, numbers and level of responsibility. Different wording is fine; contradictory facts are not.
Finish without Claude: read the CV aloud, open the exact file you will send, confirm links, filename and recipient, and remove any statement you cannot support. If an achievement matters enough to include, it matters enough to verify.
02 · The method
Step by step
- 1
Create the fact bank
Collect real roles, dates, qualifications, projects and verified outcomes.
- 2
Extract the rules
Read the actual opportunity and confirm type, length, sections and format.
- 3
Build the matrix
Map each requirement to supplied evidence and label gaps.
- 4
Draft and tailor
Rewrite specific evidence while preserving ownership and dates.
- 5
Audit the file
Inspect the exported document and compare it with your source.
- 6
Approve
A human confirms accuracy, privacy and appropriate disclosure.
03 · Use this now
Copy-paste prompt for a truthful CV
Act as a careful CV editor. Use only the facts I supply. Never invent or upgrade a title, date, qualification, publication, employer, tool, metric or result. Target opportunity and rules: [PASTE]. Source fact bank: [PASTE]. First return a requirement-to-evidence matrix with SUPPORTED, PARTIAL, MISSING or UNCLEAR labels, a section order and questions for missing proof. Only after I approve that, draft the sections. Mark uncertain details [VERIFY] and include a change log for every rewrite.
04 · Avoid these
Common mistakes
- Changing responsibility through polished wording
- Copying unsupported keywords
- Using the wrong CV format
- Uploading unnecessary personal data
- Treating an ATS score as a prediction
- Skipping export checks
05 · Questions
Frequently asked questions
Can Claude write my CV from scratch?
It can draft from a detailed fact bank, but a blank prompt encourages generic claims and omissions. Verify every line.
Can Claude make a CV ATS-friendly?
It can help with readable headings and truthful terms, but cannot guarantee a particular parser or ranking.
How do I stop invented metrics?
Tell it never to create numbers and to use a placeholder until you provide a verifiable result.
Should I upload my CV?
Remove unnecessary personal or confidential details and check the current account and file-handling guidance first.
Related guides
Primary sources
Product menus and plan limits change. The linked vendor documentation is the authority when your screen differs.