20 Claude Prompts for Resume Writing That Get Interviews
XML-structured prompts that give Claude your career context, target role, and constraints — so every bullet point sounds like you, only sharper.
Resume Writing
4 promptsRewrite Resume Bullets With Impact
1/20<context> My role: [job title] Company: [company name and what they do] Industry: [industry] Target role: [what I'm applying for next] </context> <task> Rewrite these resume bullet points to be stronger: [paste your current bullet points] For each bullet: 1. Start with a strong action verb (not "responsible for" or "helped with") 2. Include a quantifiable result (number, percentage, or scope) 3. Show the impact on the business, not just the task </task> <constraints> - Keep each bullet under 2 lines - Use the XYZ formula: "Accomplished [X] as measured by [Y] by doing [Z]" - If I didn't provide metrics, suggest realistic ones I can fill in with [brackets] - Don't exaggerate — keep it honest but compelling - Tailor language to the target role's industry </constraints>
Transforms weak resume bullets into impact-driven statements with the XYZ formula.
Pro tip: Paste your entire resume and target job description together. Claude will tailor every bullet to what the hiring manager is looking for.
Write a Resume Summary
2/20<context> Years of experience: [number] Current/recent role: [title at company] Key skills: [list 3-5 top skills] Target role: [what I'm applying for] Biggest achievement: [your career highlight] </context> <task> Write 3 resume summary options (3-4 sentences each): 1. Achievement-led: Open with your biggest career win 2. Expertise-led: Open with your area of specialization 3. Value-led: Open with what you deliver for employers Each should: - Be specific to my experience (not interchangeable with anyone in my field) - Include at least one number or metric - End with what I bring to the target role </task> <constraints> - No "results-driven professional" or "passionate about" — use specific language - No first person ("I") — resumes use implied first person - Under 60 words each (recruiters scan, they don't read) - Each option should feel meaningfully different, not just reworded </constraints>
Three distinct resume summaries — achievement-led, expertise-led, and value-led — all specific to your experience.
Pro tip: After Claude generates the summaries, ask: "Which one would stand out most for a [target role] at a [company type]? Why?" Claude gives good editorial judgment.
Tailor Resume to a Job Description
3/20<context> My current resume: [paste full resume] Target job description: [paste the job description] </context> <task> Tailor my resume for this specific role: 1. Identify the top 5 keywords/skills from the job description I should emphasize 2. Rewrite my summary to align with this role 3. Reorder and rewrite bullet points to highlight relevant experience 4. Flag any gaps between my experience and their requirements 5. Suggest which experiences to expand and which to trim </task> <constraints> - Don't fabricate experience — only reframe what I've actually done - If there's a gap, suggest how to address it (transferable skills, not lies) - Keep the resume to 1 page if I have under 10 years experience, 2 pages max otherwise - Preserve my voice — don't make it sound generic - ATS-friendly: use standard section headers and avoid tables/columns </constraints>
Tailors your entire resume to a specific job description — keywords, reordering, and gap analysis included.
Pro tip: This is one of Claude's strongest use cases. Paste both documents in full — Claude will cross-reference every requirement against your experience.
Create a Skills Section That Passes ATS
4/20<context> My background: [brief description] Target roles: [list 2-3 job titles you're targeting] Industry: [industry] </context> <task> Build a skills section for my resume: 1. Technical skills — tools, platforms, and technologies I should list 2. Functional skills — capabilities relevant to my target roles 3. Certifications or credentials worth highlighting Also: - Map each skill to which target role it's most relevant for - Flag skills I should add to my LinkedIn but not my resume (and vice versa) - Suggest the order (most relevant first) </task> <constraints> - Only include skills I can credibly claim (I'll validate the list) - Use the exact terminology from job descriptions (ATS matching) - No soft skills on the resume (show those through bullet points instead) - Group skills logically, not alphabetically </constraints>
Builds an ATS-optimized skills section mapped to your target roles with exact job description terminology.
Pro tip: Paste 3-4 job descriptions for roles you want. Claude will extract the common skills and prioritize the ones that appear most frequently.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Cover Letters
4 promptsWrite a Cover Letter That Gets Read
5/20<context> My background: [brief career summary] Target role: [job title at company] Job description: [paste or summarize key requirements] Why this company: [genuine reason — not just "I admire your mission"] Connection point: [anything specific — referral, their recent news, shared interest] </context> <task> Write a cover letter (250-300 words): 1. Opening: A specific hook — not "I'm writing to express my interest" 2. Fit paragraph: Connect my top 2-3 relevant experiences to their requirements 3. Value paragraph: What I'll contribute that other candidates can't 4. Close: Confident, specific next step </task> <constraints> - Never start with "I'm writing to apply for" — start with something specific - Show, don't tell: "Led a team of 8 to ship X" not "I'm a strong leader" - No more than 3 paragraphs plus a closing line - Match the tone to the company culture (startup vs. corporate vs. creative) - Don't repeat the resume — add context the resume can't convey </constraints>
A concise cover letter with a specific hook, tailored fit, and a unique value proposition.
Pro tip: Paste the company's About page or recent blog post in <context>. Claude will reference specific details that show you did your homework.
Follow-Up Email After Application
6/20<context> Role applied for: [job title at company] Applied on: [date] Contact: [hiring manager name if known, otherwise "the hiring team"] Application method: [job board, referral, direct application] My strongest qualification: [the one thing that makes me a great fit] </context> <task> Write a follow-up email (under 80 words): 1. Reference the role and when I applied 2. Reiterate one specific reason I'm a strong fit (not a summary — ONE thing) 3. Add something useful (relevant article, insight about their industry, portfolio piece) 4. End with a low-pressure ask </task> <constraints> - Not desperate, not pushy — confident and brief - Subject line: clear and professional (not cute) - Don't restate the entire cover letter — this is a nudge, not a pitch - The "something useful" must genuinely be useful, not a thinly veiled self-promotion </constraints>
A brief, confident follow-up that adds value — not just "checking in on my application."
Pro tip: Claude writes better follow-ups when you specify what makes you uniquely qualified. One specific detail beats three generic qualifications.
Thank You Email After Interview
7/20<context> Role: [job title at company] Interviewed with: [name(s) and their role(s)] Interview details: [what was discussed — key topics, questions asked, any concerns raised] What went well: [moments that felt strong] What I wish I'd said: [anything I forgot or could have answered better] </context> <task> Write a thank you email (under 100 words) that: 1. Thanks them for something specific from the conversation (not just their time) 2. Addresses one concern they raised or topic I could strengthen 3. Reinforces my fit with a brief new point (something I didn't cover in the interview) 4. Closes with enthusiasm without desperation </task> <constraints> - Send within 24 hours (note this in the email's context) - No "I think I'd be a great fit" — show, don't tell - If there were multiple interviewers, the core message is the same but personalize the specific reference for each - Under 100 words — they're busy </constraints>
A concise thank-you that addresses concerns, adds a new point, and reinforces your fit.
Pro tip: If you interviewed with multiple people, ask Claude: "Write personalized versions for each interviewer based on what we discussed." Give brief notes on each conversation.
Networking Request Email
8/20<context> I want to connect with: [name, role, company] How I found them: [LinkedIn, conference, referral, their content] What I want: [informational interview, advice, referral, mentorship] What I can offer: [how I might be useful to them — even if small] My relevant background: [brief] </context> <task> Write a networking email (under 75 words): 1. Opening that shows I know who they are (reference something specific) 2. One sentence on why I'm reaching out 3. A specific, time-bounded ask ("15-minute call this week") 4. An offer (how I might be helpful to them) </task> <constraints> - Under 75 words total - No "I'd love to pick your brain" — be specific about what you want to know - The ask must be easy to say yes to (15 minutes, not "coffee sometime") - Sound like a person, not a LinkedIn template - Include why NOW (not just in general) </constraints>
A short, specific networking request that respects their time and offers mutual value.
Pro tip: Claude is great at finding the right tone — confident but not entitled. Specify the relationship dynamic and Claude adjusts automatically.
LinkedIn Optimization
4 promptsRewrite LinkedIn Headline
9/20<context> Current role: [job title at company] Target audience: [who I want to attract — recruiters, clients, collaborators] Key strength: [what I'm known for] Industry: [industry] </context> <task> Write 5 LinkedIn headline options: 1. Role-focused: Clear title + key value 2. Outcome-focused: What I help people achieve 3. Niche-focused: Specific expertise that differentiates me 4. Keyword-optimized: Packed with searchable terms 5. Bold/memorable: Something that stands out in search results For each, explain why it works and who it would attract. </task> <constraints> - Maximum 220 characters each (LinkedIn's limit) - Include at least one searchable keyword in each - No "guru," "ninja," "rockstar," or "passionate about" - Each should be meaningfully different, not variations of the same idea - Must work whether I'm job-seeking or not </constraints>
Five distinct LinkedIn headlines optimized for different goals — role, outcome, niche, keywords, and memorability.
Pro tip: Tell Claude whether you're actively job-seeking or building your professional brand. The ideal headline differs based on your goal.
Write LinkedIn About Section
10/20<context> Current role: [title at company] Career path: [brief trajectory] What I do: [responsibilities and impact] What I care about: [professional interests and values] Target audience: [recruiters, clients, peers — who should read this] Tone: [professional, conversational, bold — pick one] </context> <task> Write a LinkedIn About section (200-300 words): 1. Opening hook (first 2 lines are visible before "see more" — make them count) 2. What I do and who I do it for 3. Key achievements (2-3, with numbers) 4. What drives me (professional motivation, not personal life story) 5. CTA (what I want the reader to do — connect, message, visit my site) </task> <constraints> - First person ("I") is fine for LinkedIn - Use short paragraphs (2-3 sentences max) with line breaks - Include relevant keywords naturally (LinkedIn search picks these up) - No "I'm a results-driven professional" — start with something specific - The opening line should make someone click "see more" </constraints>
A LinkedIn About section with a strong hook, keyword optimization, and a clear CTA.
Pro tip: Claude writes good LinkedIn copy because it understands the platform's conventions. Specify your tone — LinkedIn culture varies wildly by industry.
Turn a Job Into a LinkedIn Story
11/20<context> Role: [job title] Company: [company name] Duration: [how long] What I did: [describe responsibilities and projects] What I achieved: [key results] What I learned: [biggest takeaway] </context> <task> Turn this work experience into a compelling LinkedIn Experience entry: 1. Role description (2 sentences — what I owned, not a job description copy-paste) 2. 4-6 bullet points showing impact (achievement-focused, not task-focused) 3. A "Featured" recommendation: write what a manager or colleague might say about me in this role (I'll ask them to adapt it) </task> <constraints> - Bullet points use the "did X → achieved Y" format - Include numbers where possible (revenue, team size, percentage improvements) - Don't list job duties — show what changed because I was there - The recommendation draft should sound natural, not corporate </constraints>
Transforms a work experience entry into achievement-focused bullets with a recommendation draft.
Pro tip: The recommendation draft is a great touch — send it to a former colleague as a starting point. People are more likely to write a recommendation when you give them a draft.
LinkedIn Post About a Career Milestone
12/20<context> Milestone: [e.g. new job, promotion, project launch, career pivot, anniversary, lesson learned] My audience: [who follows me on LinkedIn] Tone: [grateful, reflective, energized, honest — pick one] </context> <task> Write a LinkedIn post about this milestone: 1. Hook line that makes people stop scrolling 2. The story: what happened, what it took, what I learned 3. A takeaway for the reader (make it about THEM, not just me) 4. A question or CTA that drives engagement </task> <constraints> - Under 1300 characters - Don't start with "Excited to announce" or "Thrilled to share" — everyone does that - Include one vulnerable or honest moment (makes it human) - The takeaway should be actionable, not just inspirational - Use line breaks for readability - Max 3 hashtags at the bottom </constraints>
Creates a LinkedIn milestone post with a scroll-stopping hook, honest storytelling, and an audience-focused takeaway.
Pro tip: Claude writes better LinkedIn posts when you share the emotion behind the milestone. "I was terrified" is more compelling than "I was excited."
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Interview Preparation
4 promptsPrepare for Behavioral Interview Questions
13/20<context> Role I'm interviewing for: [job title at company] My background: [brief career summary] Key experiences I want to highlight: 1. [experience 1 — brief description] 2. [experience 2 — brief description] 3. [experience 3 — brief description] </context> <task> Prepare STAR-format answers for these common behavioral questions: 1. "Tell me about a time you led a project under a tight deadline" 2. "Describe a situation where you had to deal with a difficult colleague" 3. "Tell me about a time you failed and what you learned" 4. "Describe a time you had to make a decision with incomplete information" 5. "Tell me about your biggest professional achievement" For each: - Map it to the most relevant experience from my background - Write the STAR response (Situation, Task, Action, Result) - Keep each under 2 minutes when spoken - End with what I learned or how it applies to this role </task> <constraints> - Answers must be based on MY experiences, not generic examples - Each answer should highlight a different skill - Results must be specific ("increased retention by 15%" not "improved things") - The "learning" at the end should connect to the target role - If an experience doesn't fit a question well, say so and suggest which question it's better for </constraints>
STAR-format interview answers mapped to your actual experiences — specific results, not generic stories.
Pro tip: After generating, ask Claude: "Play the interviewer. Ask me follow-up questions on answer #3 that would probe for more depth." This prepares you for the real thing.
Research a Company Before Interview
14/20<context> Company: [name] Role: [what I'm interviewing for] Interview stage: [phone screen / onsite / final round] What I already know: [any existing knowledge about the company] </context> <task> Help me prepare by analyzing: 1. Company overview — what they do, business model, market position 2. Recent news — product launches, funding, leadership changes, challenges 3. Culture signals — based on their careers page, social media, and leadership communication style 4. Likely interview focus areas — what they probably care about given the role 5. Smart questions I should ask (that show I've done homework, not just Googled them) 6. Red flags to watch for during the interview </task> <constraints> - Base analysis on publicly available information - Smart questions should be specific to this company, not generic - Include at least one question about challenges or strategy (shows business thinking) - Red flags should be realistic things to watch for, not paranoia </constraints>
A pre-interview research brief with company analysis, likely focus areas, and smart questions to ask.
Pro tip: Claude can analyze company information deeply. Paste their About page, recent blog posts, or press releases for even more specific preparation.
Practice Technical Interview Questions
15/20<context> Role: [job title] Technical domain: [e.g. data analysis, financial modeling, product management, engineering] Experience level: [junior / mid / senior] Company type: [startup / enterprise / agency / consulting] </context> <task> Generate 10 technical interview questions for this role, grouped by difficulty: - 3 fundamentals (should answer confidently) - 4 intermediate (demonstrate depth) - 3 advanced (separate great candidates from good ones) For each question: 1. The question itself 2. What they're really testing (the skill behind the question) 3. A strong answer framework (not a full script — key points to hit) 4. A common mistake candidates make on this question </task> <constraints> - Questions should reflect what this specific type of company would ask - Include at least one scenario-based question ("how would you approach...") - Strong answers should demonstrate thinking process, not just knowledge - Common mistakes should be genuinely common, not obvious errors </constraints>
Ten role-specific interview questions with answer frameworks, hidden tests, and common mistakes to avoid.
Pro tip: After generating, ask Claude to conduct a mock interview: "Ask me question #4 and then follow up based on my answer." Claude adapts its follow-ups realistically.
Negotiate a Job Offer
16/20<context> Offer received: [base salary, equity, bonus, benefits — what they've offered] Role: [job title at company] My target: [what I want] My leverage: [competing offers, unique skills, market rate data] Their situation: [startup needing to hire fast, large company with rigid bands, etc.] </context> <task> Help me negotiate: 1. Assessment — is this offer competitive? (based on role, level, and market) 2. Negotiation strategy — what to push on and what to accept 3. The email/script — exact language for my counter-offer 4. If they say no — fallback positions ranked by value to me 5. Non-salary items to negotiate (that companies find easier to say yes to) </task> <constraints> - The counter should be ambitious but not insulting - Frame everything as mutual value, not "I deserve more" - Include specific language to use, not just strategy - Non-salary suggestions should be genuinely valuable (not just perks) - If the offer is already strong, say so — don't negotiate for the sake of it </constraints>
A complete negotiation strategy with exact counter-offer language, fallback positions, and non-salary levers.
Pro tip: Claude gives realistic negotiation advice — it won't just tell you to "always negotiate." If the offer is strong, it'll say so. Share as much context as you're comfortable with for the best strategy.
Career Transition
4 promptsPosition a Career Change on Your Resume
17/20<context> Current/recent role: [job title in industry] Target role: [new job title in new industry] Transferable skills: [what carries over] Gap: [what I'm missing for the new role] Why the change: [brief motivation] </context> <task> Help me position my career change: 1. Rewrite my professional summary to bridge old and new careers 2. Identify which of my current experiences translate directly (reframe the language) 3. Identify gaps and suggest how to fill them quickly (courses, projects, volunteer work) 4. Rewrite my 3 strongest bullet points to highlight transferable skills 5. Suggest a "bridge" job title if my current one doesn't match (for LinkedIn headline) </task> <constraints> - Don't hide the career change — own it as a strength - Reframed bullet points must be honest (don't invent experience) - Gap-filling suggestions should be achievable in under 3 months - The bridge title should be searchable by recruiters in the target field </constraints>
Positions a career change as a strength — reframed experience, gap analysis, and bridge positioning.
Pro tip: Claude is excellent at finding non-obvious transferable skills. Describe your daily work in detail — Claude will spot connections to the target role that you might miss.
Build a 90-Day Career Transition Plan
18/20<context> Current situation: [employed/unemployed, current role] Target: [desired role and industry] Timeline: [when I want to make the move] Resources: [time available per week, budget for courses/tools] Network: [existing connections in target field, if any] </context> <task> Create a 90-day career transition plan: Days 1-30: Foundation - Skills to learn and resources to use - People to connect with - Portfolio pieces to create Days 31-60: Build Credibility - Projects or volunteer work to gain experience - Content to publish (show expertise publicly) - Applications to start Days 61-90: Launch - Interview preparation - Application strategy (where and how) - Milestones to hit before applying to dream companies </task> <constraints> - Be realistic about time constraints (I have [X] hours per week) - Every week should have a specific, checkable deliverable - Include both skills building and networking (most jobs come through connections) - Don't just say "take a course" — recommend specific actions - Include metrics to track progress </constraints>
A structured 90-day plan with weekly deliverables, networking targets, and progress metrics.
Pro tip: Save this plan as a Claude Project and check in weekly: "It's day 14. Here's what I've done: [update]. What should I adjust?" Claude will adapt the plan based on your progress.
Write a Career Pivot Story
19/20<context> Previous career: [industry, role, years] New direction: [target industry and role] The catalyst: [what made me want to change] What I bring: [skills and perspectives from my previous career] </context> <task> Write my career pivot story for 3 contexts: 1. LinkedIn About section version (250 words) — for passive networking 2. Interview version (90 seconds spoken) — for "tell me about yourself" 3. Networking event version (30 seconds) — for quick introductions Each should: - Frame the pivot as intentional, not accidental - Connect the dots between old and new career - Highlight what my non-traditional background adds - End with where I'm headed (forward-looking) </task> <constraints> - Don't apologize for the career change — it's an asset - The interview version must be speakable (write for the ear) - Include one specific moment or insight that triggered the change (makes it memorable) - Each version should stand alone (don't assume they've read the others) </constraints>
Three versions of your career pivot story — LinkedIn, interview, and networking — each framing the change as a strength.
Pro tip: The "catalyst moment" is what makes career pivot stories memorable. Give Claude a specific, honest moment and it will build the narrative around it.
Identify Transferable Skills
20/20<context> My current/past role: [describe in detail — daily tasks, projects, responsibilities] Target role: [what I want to do next] Target job descriptions: [paste 1-2 job descriptions, or describe requirements] </context> <task> Analyze my transferable skills: 1. Direct transfers — skills that apply exactly (just different context) 2. Adjacent transfers — skills that need slight repositioning 3. Hidden transfers — skills I'm not seeing because I'm too close to my own experience 4. For each skill: how to describe it on a resume using the target role's language 5. Priority skills to develop — what's missing that I can't transfer from current experience </task> <constraints> - Be specific: "managed a $2M project budget" not "project management skills" - Hidden transfers are the most valuable part — dig deep - Use the exact language from the target job descriptions - Priority skills should be ranked by: importance for the target role × ease of acquiring </constraints>
Uncovers direct, adjacent, and hidden transferable skills — with exact language for your target role.
Pro tip: Describe your daily work in granular detail — meetings you run, tools you use, decisions you make. Claude finds transferable skills in the details that generic descriptions miss.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
14-day free trial. Cancel anytime.