Claude Prompts for an ATS-Friendly Resume
28 copy-paste prompts for parsing a job description, rewriting bullets you can defend, locking a plain-text section order, cutting skills fluff, quantifying real impact, and handing the approved resume to a cover letter.
Last updated September 26, 2026
What this page is for
Applicant tracking systems store the text of your file and help a recruiter search it. A useful Claude session does two jobs: it maps the posting's language onto experience you really have, and it keeps the file in an order a parser and a person can both follow. It does not invent a career to raise a match score.
The prompts below assume you paste your own material. They use labeled blocks, a pattern that fits Claude well when two long documents must stay distinct. If Projects is available on your plan, keep the master resume there and open a new conversation for each posting. Still paste the posting every time. A stored resume is not a stored job.
For the surrounding workflow, use How to Use Claude to Create an ATS-Friendly Resume. For Projects, model choice, and loading a long career history, use How to Use Claude for Resume Writing. This page stays on the prompts.
Which prompt to run
| Job | Paste | Claude must not |
|---|---|---|
| Parse the posting | Full job description and current resume | Add a skill so the table looks complete |
| Rewrite a bullet | One bullet, role context, one target phrase | Change who did the work or the size of the result |
| Fix section order | The whole resume as plain text | Invent a two-column or icon layout |
| Clean skills | Skills block plus evidence from bullets | Repeat the posting as a keyword list |
| Quantify impact | A fact bank of numbers you can defend | Guess a percentage |
| Cover letter | The resume you will actually submit | Introduce a claim that is not on that resume |
A short Claude workflow
Run the parse prompt first and save the match table. Rewrite only the bullets that map to a must-have you can support. Then ask for the plain-text assembly. Read it out loud. If a line sounds like a job you did not do, reject it even if the wording is smoother.
Build the fact bank before you ask for numbers. Include team size, time period, tools, budget you controlled, volume, and any result you could show a hiring manager. When the bank is empty, the prompt should leave a blank. A blank is a better resume line than a confident fiction.
After export, open the file outside Claude. Select all, copy, and paste into a plain text editor. If the experience section arrives scrambled, the layout is still too complex. Go back to one column. The US-focused comparison of screening tools is on AI for beating the ATS. Broader prompt collections live on AI resume prompts and resume prompts.
28 copy-paste Claude prompts
Replace every bracket. Delete a block you cannot fill. If Claude returns a metric you do not recognise, treat that line as unusable.
Parse the job description
Start here. Claude should extract the employer's language before it rewrites anything. Label the posting and the resume so the two sources stay separate.
<job_description> [paste the full posting, including requirements and nice-to-haves] </job_description> <resume> [paste your current resume as plain text] </resume> Extract requirements. For each, return: requirement, exact phrase from the posting, resume evidence (quote or MISSING), status EXACT or INFERRED or MISSING, and the best section (summary, bullet, or skills). Do not add skills, tools, degrees, dates, or metrics that are not in the resume.
<job_description> [paste] </job_description> List the 12 phrases a recruiter would search for, in the posting's own words. Split them into must-have and nice-to-have. Flag acronyms and spell out the full form next to each acronym when the posting uses one. Do not rewrite my resume yet.
Here is a job description and my resume: <job_description> [paste] </job_description> <resume> [paste] </resume> Build a match table with columns: posting requirement, my evidence, gap, honest next step. Next step may be "add a bullet I already did", "leave it off", or "ask me for a fact". Do not fill gaps with plausible experience.
Read only the job description below. Return three short lists: tools named, outcomes the employer cares about, and words that describe how the team works. Quote the posting. Then list five questions I should answer from my own history before any rewrite. <job_description> [paste] </job_description>
Rewrite bullets for an ATS without adding fiction
One bullet at a time is easier to check than a full-page rewrite. Ask for options, a word limit, and a change log.
<original_bullet> [paste one bullet] </original_bullet> <role_context> [title, company, dates, what you actually owned] </role_context> <target_phrase> [one requirement from the posting] </target_phrase> Rewrite the bullet in 22 words or fewer. Lead with a concrete verb. Keep the actor, scope, and result truthful. If the target phrase is not supported, say LEAVE OFF and explain why. Return the rewrite and a one-line change log.
Turn these duty lines into achievement bullets. Use only facts in the notes. If a number is missing, write NEEDS METRIC instead of inventing one. <duties> [paste] </duties> <fact_bank> [metrics, tools, team size, dates, and outcomes I can defend] </fact_bank> Give two versions of each bullet: one with a metric from the fact bank, and one that stays qualitative because no metric exists.
Compare my original bullet with this rewrite. List every change to actor, action, scale, time period, tool, and certainty. Recommend KEEP, EDIT, or REJECT. Do not write a third version. <original> [paste] </original> <rewrite> [paste] </rewrite>
Rewrite this bullet so a parser and a recruiter both see the tool the posting named. Use the tool name once, in the posting's spelling, only if my notes show I used it. Otherwise keep my real tool and do not force a synonym. <bullet> [paste] </bullet> <posting_tool> [tool name] </posting_tool> <my_notes> [paste] </my_notes>
Section order and a parser-safe layout
Ask for one column and standard headings. Decorative layouts belong in a design tool after the text is approved, and only if the employer accepts them.
Reassemble my resume as plain text in this order: contact line, target title, summary (3 lines), Experience, Education, Skills. One column. Dates on the same line as each role. Headings must be exactly Experience, Education, and Skills. Do not use tables, text boxes, icons, or columns. <resume> [paste] </resume> <target_title> [title from the posting] </target_title> Keep every employer, title, and date unchanged. Mark any heading you had to rename.
I am a student or recent graduate. Propose a one-column order that puts Education before Experience, then Projects, then Skills. Keep the headings as plain words. Flag lines that are activities with no evidence. <resume> [paste] </resume> <target_role> [role] </target_role>
Audit this plain-text resume for parser risk. Check: contact details stuck in a header, tables, columns, images, icons used as skill ratings, headers that say "Professional Journey" instead of Experience, dates in inconsistent formats, and text that would be read out of order. Return location, risk, and a plain-text fix. Do not redesign it. <resume> [paste] </resume>
The employer asks for [DOCX or PDF, paste the instruction]. Give me a submission checklist: heading names, file type, whether the text must stay selectable, what to remove from the header and footer, and what I should verify after export. Do not claim a specific vendor will score the file.
Skills versus fluff
A skills block should be terms you can discuss in an interview. Claude should separate evidence from adjectives.
<skills_block> [paste] </skills_block> <job_description> [paste] </job_description> <evidence> [bullets or notes that show where I used each skill] </evidence> Split skills into: keep (exact posting term plus evidence), rephrase (I did the work under a different name; show both names once), and remove (adjective, soft claim, or tool I cannot defend). Do not add a skill to raise a match.
Rewrite my summary in 45 words. Use two exact phrases from the posting that my experience supports. Cut "results-driven", "passionate", "dynamic", and "team player" unless you replace them with a fact. If you cannot support two phrases, use one and say what is missing. <summary> [paste] </summary> <supported_phrases> [paste from the match table] </supported_phrases>
Look at this skills list and mark fluff. Fluff includes proficiency bars, "expert" with no scope, repeated synonyms, and tools listed only because the posting named them. <skills> [paste] </skills> Return a cleaned list grouped as Tools, Methods, and Domain knowledge. Cap it at 12 items. Each item needs a six-word evidence note from my resume or NEEDS EVIDENCE.
The posting says "[soft skill, for example stakeholder management]". Find whether my bullets already show it. If yes, quote the bullet and suggest a tighter verb. If no, write OMIT. Do not add a soft-skill line with no story. <resume> [paste] </resume>
Quantify impact from notes you can defend
Numbers help when they are yours. The prompt should interview you for a missing figure instead of guessing one.
Here is a bullet with no number and my raw notes. Ask me at most three questions that would produce a real metric (scale, time, money, quality, or volume). Then draft the bullet only with numbers that appear in the notes. Leave a blank like [METRIC] where I still need to look something up. <bullet> [paste] </bullet> <notes> [paste] </notes>
Convert these notes into one bullet with this pattern: verb, what changed, for whom, over what period, with the number from the notes. If the notes only support a range or an estimate, label it as approximate and keep my wording. <notes> [paste] </notes>
I managed people, but I do not have a revenue number. Using only these facts, write two bullets that quantify scope (team size, cadence, budget I can confirm) without implying I owned company revenue. <facts> [paste] </facts>
Review every number in this resume. For each, say whether the source is in my fact bank, whether the time period is clear, and whether the claim could be read as bigger than the work. Flag any number that appeared in a previous AI draft but not in the fact bank. <resume> [paste] </resume> <fact_bank> [paste] </fact_bank>
Hand off an approved resume to a cover letter
Write the letter only after the resume facts are locked. The letter should point at two or three bullets, not repeat the whole document.
<approved_resume> [paste the resume you are actually submitting] </approved_resume> <job_description> [paste] </job_description> <company_note> [one true detail: a product, a team, a public goal, or "none"] </company_note> Draft a 220 to 260 word cover letter. Open with the role and one supported connection. Use two resume facts with the same numbers. Close with a specific next step. Do not add experience, awards, or enthusiasm that is not in the resume. Mark any sentence that needs a fact I did not provide.
Turn this approved resume into a 90-word application answer for "Why this role?". Use one posting phrase and one resume proof. No greeting, no sign-off. <resume> [paste] </resume> <role> [title and company] </role>
List the claims in this cover letter that are not on the approved resume. Quote the letter sentence and the missing resume support. Recommend cut or add-to-resume-only-if-true. <letter> [paste] </letter> <resume> [paste] </resume>
I am not sending a cover letter. Write a 40-word note I can paste into an application text box, using only the summary and one metric from the resume. If the box is optional, say whether the note adds anything a recruiter cannot already see.
Gaps, career changes, and a final audit
Use a skeptical pass before you export. Claude should surface risk. You decide what stays.
My history has [a gap, a contract stretch, a career change, or a title that does not match the posting]. Here are the true dates and what I did: <facts> [paste] </facts> Suggest a plain-text way to show the dates without a false title. Give two wording options and the interview question each might raise. Do not hide months by changing dates.
You are a recruiter screening for [role]. Read the resume and the posting. List five suspicions, each with the line that caused it and a factual fix if my notes support one. Do not award a score. <resume> [paste] </resume> <job_description> [paste] </job_description>
Final audit. Compare the resume to the posting and the fact bank. Return: exact keywords present, keywords correctly omitted, bullets whose meaning changed, dates that conflict, headings that are nonstandard, and claims with no fact-bank source. End with a submit or revise recommendation and the single edit that matters most. <resume> [paste] </resume> <job_description> [paste] </job_description> <fact_bank> [paste] </fact_bank>
Prepare interview backup for the three strongest bullets. For each, list the situation, my action, the evidence I should be ready to show, and a detail I should not exaggerate. Use only the resume and notes. <resume> [paste] </resume> <notes> [paste] </notes>
Tips that keep the resume yours
- Wrap the posting and the resume in labeled blocks so Claude does not merge them into one story.
- Rewrite one bullet, check the change log, then continue. A full-page rewrite hides meaning changes.
- Use the posting's spelling for a tool you actually used, once. Leave off tools you only recognise.
- Put NEEDS METRIC or [METRIC] in the draft instead of accepting an invented percentage.
- Keep a master fact bank outside the chat: titles, dates, tools, and numbers you can defend.
- Export to the file type the application requests, then copy the text out of the file and read it in order.
- Standard headings (Experience, Education, Skills) are safer than clever section names.
- Write the cover letter from the approved resume, not from an earlier draft that still had rejected claims.
Claude ATS resume FAQ
What makes a Claude prompt ATS-friendly?
An ATS-friendly Claude prompt gives the model your real resume and the full job description, then asks for plain text with standard headings. It should label exact phrases from the posting, mark missing evidence, and refuse invented titles, dates, tools, or metrics. The prompt is doing parsing and editing work. You still choose the file type the employer requested and check that the exported text is selectable.
Can Claude make my resume pass Workday, Greenhouse, or Lever?
Claude cannot log into those systems or guarantee a pass. It can help you mirror the posting's language, use headings a parser can read, and keep claims tied to your history. Employers still use human review, knockout questions, and their own settings. Follow the application's file instructions, then open the file you upload and confirm the text reads in order.
Should I paste my whole resume and the job description together?
Yes. Claude is useful here because one message can hold a long work history and a full posting. Wrap them in labeled blocks so the model does not blend the two. If your plan includes Projects, you can keep a master resume there and start a new chat per application. Remove identity numbers, full home addresses, and other details the application does not need.
How do I stop Claude from inventing metrics?
Give it a fact bank of numbers you can defend, and tell it to write NEEDS METRIC when a bullet has no number. Ask for a change log that shows the original claim and the new wording. Reject any percentage, dollar figure, team size, or tool that you cannot point to in a review, dashboard, or your own notes.
What resume section order should I ask Claude to use?
For most experienced applicants, use contact line, target title, short summary, experience, education, and skills, in one column. Students and recent graduates often put education before experience. Ask Claude to keep headings as plain words such as Experience, Education, and Skills, and to put dates on the same line as the role. Change that order only when the employer or a local CV convention requires it.
How is this different from a general Claude resume guide?
This page is a copy-paste prompt library for one job: making a resume easier for an applicant tracking system and a recruiter to read, without adding false experience. The step-by-step workflow lives on the Claude ATS how-to, and the broader Claude resume guide covers Projects, model choice, and career-history loading. Use those pages for process. Use these prompts when you are ready to paste.
Can I use the same prompts for a cover letter?
Use the cover-letter handoff prompts after the resume is approved. They should pull only facts already on the resume or in notes you paste, name the company, and stay inside a word limit. A cover letter is not a second keyword dump. If the application has no letter field, skip it.
Do keyword lists help, or do they look like stuffing?
A keyword list helps when each term is tied to a bullet you can defend. A skills block that repeats the posting with no evidence reads as stuffing to a recruiter even if a parser counts the words. Ask Claude to split EXACT matches you have used from terms you should leave off.