This page collects chatgpt prompts for resume writing, cover letter drafting, and job application polish. It is for anyone updating their own materials or helping a team standardize hiring documents. The prompts work across ChatGPT, Claude, Copilot, and Gemini without modification. You will find prompts for tailoring a resume to a specific job description, writing achievement bullets, drafting cover letters from scratch, and handling the awkward parts: gaps, career pivots, and titles that do not match the role you are applying for.

What is in this pack

Twenty-three prompts, grouped into five categories: resume structure and bullets, tailoring to job descriptions, cover letter drafting, handling difficult situations (gaps, pivots, overqualification), and final review. Each prompt is ready to copy, with variables in brackets so you can drop in your own details without rewriting the logic.

The pack is built for job seekers and the people who support them, including career coaches, HR teams, and managers writing internal promotion packets. It complements the broader prompts by role library and sits alongside AI prompts for business tasks for teams that run hiring workflows at scale.

One honest note before the prompts: AI is good at structure and language, not at knowing whether your claims are accurate. Every bullet it writes needs a human check against what you actually did.

The prompts, by category

These prompts are grouped by the stage of the job search where you're most likely to need them. Work through them in order if you're starting from scratch, or jump to the category that fits where you are.

A note on scope: these prompts do well at structure, tone, and phrasing. They don't know your actual achievements. Every output needs you to swap in real numbers, real context, and real outcomes before it goes anywhere near a hiring manager.

The categories are:

CategoryWhat it coversPrompts
Resume foundationFirst drafts, summaries, formatting5
Tailoring to a jobMatching language, gap analysis4
Cover lettersOpeners, full drafts, follow-ups4
Handling hard situationsGaps, pivots, short tenures4
Interview prep from your resumeQuestions, talking points3

Resume foundation


Write a professional summary from bullet-point experience

Variables: [CURRENT TITLE], [YEARS OF EXPERIENCE], [TOP TWO OR THREE ACHIEVEMENTS], [TARGET ROLE]

When to use it: You have a list of jobs and responsibilities but no summary section.

Change first: Replace the achievement placeholders with real, specific numbers before you do anything else.

You are a professional resume writer. Write a three-to-four sentence professional summary for a [CURRENT TITLE] with [YEARS OF EXPERIENCE] years of experience. The summary should be written in first person without the pronoun "I" and should position the candidate for a [TARGET ROLE].

Key achievements to weave in:
- [ACHIEVEMENT 1]
- [ACHIEVEMENT 2]
- [ACHIEVEMENT 3]

Tone: confident, specific, no buzzwords. Avoid phrases like "results-driven" or "passionate about".

[NEEDS REAL OUTPUT] What to notice: how the model compresses bullet points into a readable arc, and where it defaults to vague language you'll need to sharpen.


Rewrite bullet points from a job description

Variables: [ORIGINAL BULLET POINTS], [TARGET ROLE], [INDUSTRY]

When to use it: Your current bullets describe duties. You need them to describe impact.

Change first: Add at least one real metric per bullet before running this.

Rewrite the following resume bullet points so they follow an action-result structure. Start each bullet with a strong past-tense verb. Remove passive constructions. Keep each bullet to one line.

Original bullets:
[ORIGINAL BULLET POINTS]

The candidate is targeting roles in [INDUSTRY] at the [TARGET ROLE] level. Preserve all specific numbers and facts exactly as written.

Generate a skills section from a job posting

Variables: [JOB POSTING TEXT], [YOUR ACTUAL SKILLS]

When to use it: You're applying to a role in a new sector and aren't sure which skills to surface.

Change first: Delete any suggested skill you don't genuinely have. This prompt over-includes by design.

Read the following job posting and extract the skills it values most, split into hard skills and soft skills.

Job posting:
[JOB POSTING TEXT]

Then compare that list against my actual skills below and suggest which ones I should feature prominently in my resume skills section. Flag any gaps honestly.

My skills:
[YOUR ACTUAL SKILLS]

Format an unstructured work history

Variables: [RAW WORK HISTORY]

When to use it: You've written your history as paragraphs or notes and need a clean, standard resume format.

Change first: Check every date before accepting the output.

Take the following unstructured work history and reformat it as a standard reverse-chronological resume. Use this structure for each role: Job Title | Company | Dates, followed by three to five bullet points. Do not add achievements that are not in the source material.

Work history:
[RAW WORK HISTORY]

Condense a two-page resume to one page

Variables: [FULL RESUME TEXT], [TARGET ROLE]

When to use it: Your resume runs long and you need to cut without losing what matters.

Change first: Tell the model which role you're targeting so it knows what to prioritize.

I need to condense the following resume to fit on one page. I am targeting [TARGET ROLE] roles. 

Keep: the most recent ten years of experience, the most relevant skills, and any quantified achievements. Remove: older roles that don't add new skills, repeated responsibilities across roles, and any generic phrases.

Resume text:
[FULL RESUME TEXT]

Show me what you removed and why.

Tailoring to a job


Identify keyword gaps between a resume and a job posting

Variables: [RESUME TEXT], [JOB POSTING TEXT]

When to use it: Before submitting to any role where ATS screening is likely.

Change first: Only add keywords you can back up with real experience.

Compare my resume against this job posting. List the keywords and phrases that appear in the job posting but are absent or underrepresented in my resume. Group them by: must-add (core to the role), consider-adding (secondary skills), and skip (I have no experience here).

Resume:
[RESUME TEXT]

Job posting:
[JOB POSTING TEXT]

[NEEDS REAL OUTPUT] What to notice: how the model sorts "must-add" versus "skip" and whether those calls match your own read of the role.


Rewrite a resume summary to match a specific job

Variables: [EXISTING SUMMARY], [JOB POSTING TEXT]

When to use it: You have a strong base summary but need to shift emphasis for each application.

Change first: Review whether the rewritten summary still sounds like you.

Here is my current resume summary and a job posting I am applying to. Rewrite my summary to better reflect the language and priorities of this specific role. Do not invent new experience. Keep it to four sentences maximum.

Current summary:
[EXISTING SUMMARY]

Job posting:
[JOB POSTING TEXT]

Score a tailored resume against a job posting

Variables: [TAILORED RESUME TEXT], [JOB POSTING TEXT]

When to use it: After tailoring, before submitting.

Change first: Ask for specific line-level suggestions, not just a score.

On a scale of 1 to 10, score how well this resume matches this job posting. Then give me three specific changes that would raise the score. Focus on language alignment, missing keywords, and relevance of the top bullet points.

Resume:
[TAILORED RESUME TEXT]

Job posting:
[JOB POSTING TEXT]

Write a targeted skills addendum

Variables: [JOB POSTING TEXT], [YOUR SKILLS AND TOOLS]

When to use it: The role is highly technical and your main resume doesn't have room to list every relevant tool.

Change first: Remove anything from the output that you'd struggle to discuss in an interview.

Based on this job posting, write a brief skills addendum (six to eight lines, two columns) that highlights the tools, platforms, and methods most relevant to this role. Only include items from my list below.

Job posting:
[JOB POSTING TEXT]

My skills and tools:
[YOUR SKILLS AND TOOLS]

Cover letters


Write a full cover letter from a resume and job posting

Variables: [RESUME TEXT], [JOB POSTING TEXT], [COMPANY NAME], [HIRING MANAGER NAME OR "Hiring Manager"]

When to use it: Starting from scratch on a cover letter.

Change first: The opening line. Model-generated openers are the most recognizable part of a machine-written letter.

Write a cover letter for the role described in the job posting below. Use my resume as the source of facts. 

Format: four paragraphs. First paragraph: a specific hook, not a generic opener. Second paragraph: the most relevant experience from my resume. Third paragraph: why this company specifically. Fourth paragraph: a short, direct close.

Address it to [HIRING MANAGER NAME OR "Hiring Manager"] at [COMPANY NAME].

Resume:
[RESUME TEXT]

Job posting:
[JOB POSTING TEXT]

[NEEDS REAL OUTPUT] What to notice: whether the third paragraph (why this company) contains anything specific or defaults to placeholder language that still needs research on your part.


Write a cover letter opening line only

Variables: [ROLE TITLE], [ONE SPECIFIC REASON YOU WANT THIS ROLE OR COMPANY]

When to use it: You have the rest of the letter but the opener reads flat.

Change first: The specific reason. Generic input produces generic output here more than anywhere else.

Write five different opening lines for a cover letter for a [ROLE TITLE] position. Each opener should feel direct and specific, not flattering. The one real detail I want to anchor on is: [ONE SPECIFIC REASON YOU WANT THIS ROLE OR COMPANY].

No opener should start with "I am writing to apply" or "I am excited to apply". No opener should mention "passion".

Write a follow-up email after submitting an application

Variables: [ROLE TITLE], [COMPANY NAME], [DATE APPLIED], [ONE RELEVANT DETAIL TO REINFORCE]

When to use it: One to two weeks after submitting, if you've heard nothing.

Change first: Keep it short. If the model returns more than five sentences, cut it.

Write a brief follow-up email for a [ROLE TITLE] application submitted to [COMPANY NAME] on [DATE APPLIED]. The email should be three to four sentences: a reminder of the application, one sentence reinforcing my interest with this specific detail ([ONE RELEVANT DETAIL TO REINFORCE]), and a low-pressure request for an update. Subject line included.

Adapt a cover letter for a different company in the same sector

Variables: [ORIGINAL COVER LETTER], [NEW COMPANY NAME], [NEW ROLE TITLE], [ONE THING DIFFERENT ABOUT THIS COMPANY]

When to use it: You're applying to multiple similar roles and want to avoid sending identical letters.

Change first: The company-specific detail in the third paragraph. That's the one part the model cannot research for you.

Adapt the following cover letter for a new application. The new company is [NEW COMPANY NAME], the role is [NEW ROLE TITLE], and the key difference about this company worth acknowledging is [ONE THING DIFFERENT ABOUT THIS COMPANY]. Keep the overall structure. Change the company name, the role title, and any company-specific references.

Original cover letter:
[ORIGINAL COVER LETTER]

Handling hard situations


Address a resume gap directly

Variables: [LENGTH OF GAP], [REASON IF COMFORTABLE SHARING], [WHAT YOU DID DURING THE GAP], [TARGET ROLE]

When to use it: You have a gap of three months or more and want a prepared, honest explanation rather than an evasive one.

Change first: The reason and what you did. Vague input produces a vague explanation that makes gaps look worse.

Write two to three sentences I can use in a cover letter or interview to address a [LENGTH OF GAP] gap in my resume. The reason is [REASON IF COMFORTABLE SHARING]. During this time I [WHAT YOU DID DURING THE GAP]. The explanation should be direct and forward-looking, not apologetic. I am targeting [TARGET ROLE] roles.

[NEEDS REAL OUTPUT] What to notice: whether the tone is genuinely direct or whether it drifts into over-explanation. Trim any sentence that sounds defensive.


Position a career pivot

Variables: [PREVIOUS FIELD], [TARGET FIELD], [TRANSFERABLE SKILLS], [REASON FOR PIVOT]

When to use it: Your work history is in one field and you're applying in another.

Change first: List transferable skills specifically. "Communication" is not a skill for this purpose.

I am pivoting from [PREVIOUS FIELD] to [TARGET FIELD]. Write a two-paragraph resume summary that positions this pivot as intentional and relevant. Use these transferable skills as the bridge: [TRANSFERABLE SKILLS]. The reason for the pivot, if I choose to share it: [REASON FOR PIVOT]. Do not hide the transition. Make it an asset.

Explain a short tenure

Variables: [ROLE TITLE], [COMPANY], [LENGTH OF TENURE], [REASON FOR LEAVING]

When to use it: You left a role after less than a year and it's on your resume.

Change first: Be honest about the reason in the prompt. The model can't help you phrase something it doesn't know.

Write one to two sentences I can include in a cover letter or use in an interview to explain a short tenure at [ROLE TITLE] at [COMPANY] ([LENGTH OF TENURE]). The real reason for leaving was [REASON FOR LEAVING]. The explanation should be honest, brief, and not dwell on the role. Move quickly to what I learned or what I did next.

Reframe a role title that undersells the work

Variables: [ACTUAL TITLE], [RESPONSIBILITIES AND SCOPE], [TARGET ROLE]

When to use it: Your job title doesn't reflect what you actually did, and you need to close that gap in writing without misrepresenting yourself.

Change first: Be precise about scope. The model will write to whatever level of responsibility you describe.

My job title was [ACTUAL TITLE], but my actual responsibilities included [RESPONSIBILITIES AND SCOPE]. I cannot change the title on my resume, but I need the bullet points and summary to communicate the real scope of the work. Write three to four bullet points and one summary sentence that accurately reflect the level of the work, without inflating the title or misrepresenting anything.

Target role:
[TARGET ROLE]

Interview prep from your resume


Generate likely interview questions from a resume

Variables: [RESUME TEXT], [TARGET ROLE]

When to use it: Before a first-round interview, to identify where a interviewer is likely to probe.

Change first: Add the specific company or role level to get sharper questions.

Read this resume and generate ten interview questions a hiring manager for a [TARGET ROLE] position would likely ask based on what they see. Flag two or three areas where the resume might raise skepticism or invite a follow-up question.

Resume:
[RESUME TEXT]

Write a STAR-format answer from a resume bullet point

Variables: [RESUME BULLET POINT], [INTERVIEW QUESTION]

When to use it: You have a strong bullet point but struggle to expand it into a spoken answer.

Change first: Fill in the actual context. The model will invent plausible-sounding detail if you leave gaps, and invented detail fails under follow-up questions.

Turn the following resume bullet point into a STAR-format interview answer (Situation, Task, Action, Result) for the question: "[INTERVIEW QUESTION]".

Bullet point:
[RESUME BULLET POINT]

Use first person. Keep the full answer under two minutes when read aloud. Mark clearly where I need to add specific context or numbers that only I know.

[NEEDS REAL OUTPUT] What to notice: where the model inserts brackets asking for your real numbers. Those are the places an interviewer will push. Prepare them.


Write a 60-second elevator pitch from a resume

Variables: [RESUME TEXT], [TARGET ROLE OR INDUSTRY]

When to use it: For the "tell me about yourself" opener. Prepare it before every interview, not just once.

Change first: Read it aloud. What sounds natural in text often sounds stilted when spoken. Edit from how you actually talk.

Based on this resume, write a 60-second spoken elevator pitch I can use at the start of an interview for [TARGET ROLE OR INDUSTRY] roles. The pitch should cover: where I have been, what I am best at, and why I am making this move. Write it the way a person talks, not the way a resume reads. Avoid resume clichés.

Resume:
[RESUME TEXT]

Real example outputs

The five prompts marked [NEEDS REAL OUTPUT] require actual model responses captured from a live session before this page publishes. Do not substitute invented text.

For each captured output, include a "what to notice" line that explains what the model got right and what a human editor should still check. For example, a cover letter output might nail the structure but misattribute a company detail that was not in the prompt. That kind of candid note is more useful to readers than a polished example that looks too clean to be real.

Until real outputs are captured, treat these prompts as tested in structure only. The variables, the instruction logic, and the output format have been reviewed, but the quality of any given response will depend on the model you use and the specifics you supply.

How to adapt these for your team

These prompts were written for individual job seekers, but they transfer cleanly to career services teams, HR departments, and recruiting coordinators who help multiple people through the same process.

The main change is scope. Instead of writing [YOUR NAME] and [TARGET ROLE] once, you fill those brackets for each person you are supporting. If you manage a cohort, a simple spreadsheet with one row per candidate and one column per variable keeps the work systematic.

Use caseVariables to standardizeVariables to personalize
University career centerTone, formatting rules, industryStudent name, degree, experience
Outplacement programTarget industry, job levelCandidate background, skills
Internal mobility teamCompany style, role familyEmployee history, development goals
Recruiting coordinationJob description, hiring team voiceApplicant materials

For teams running these prompts regularly, Convergence shared folders let you store the finalized versions in one place so everyone on the team pulls from the same prompt, not a copy someone edited three months ago.

One honest caveat: AI performs best here when the human inputs are rich. Thin bullet points in, thin resume out. The prompts are only as useful as the context you feed them.

Save this folder to your workspace

These prompts work best when your whole team can reach them without hunting through old chat histories or shared docs. In Convergence, you can save this entire pack as a shared folder, so every prompt stays in one place, editable, and available across ChatGPT, Claude, Copilot, and Gemini.

That matters for hiring managers and recruiters running high-volume searches. When the "tailor this resume" prompt lives in a shared folder, anyone on the team pulls the same tested version instead of writing from scratch each time.

If you are working alone, a personal folder works just as well. Rename prompts to match your own job search, swap in standing variables like your target role or industry, and the prompts are ready without any setup each session.

For other role-specific packs, the full prompts library by role has collections covering marketing, business, and more.

Frequently asked questions

Do these prompts work on Claude and Gemini, not just ChatGPT?

Yes. Every prompt in this pack works across ChatGPT, Claude, Copilot, and Gemini without modification. The variables in brackets behave the same way on each platform. If one model's output feels too formal or too casual, adjust the tone instruction in the prompt rather than switching tools.

Will AI-written resumes get flagged by applicant tracking systems?

AI detection in hiring is unreliable and inconsistently applied. The real risk is a resume that sounds generic because the prompts were run without real job details. Fill every bracket with specific information and edit the output before sending.

Can I use these prompts for someone else's resume?

Yes, though accuracy depends on the detail you supply. The more specific the role history and achievements you provide, the better the output.

Are these prompts suitable for career changers?

The career pivot and skills translation prompts in the Positioning category are designed exactly for that situation.

How do I save these prompts for my whole team?

Convergence shared folders let a team lead store, organize, and push prompts to every team member from one place.