Choose by the output you need to make

ChatGPT Prompts for Job Seekers

People improving resumes, applications, interviews, and career-change materials.

Where ChatGPT helps this role

  • Rewrite resume bullets from real work history, tools, scope, and target job language without inventing metrics.
  • Write a cover letter that connects company reason, role fit, and one proof paragraph instead of broad enthusiasm.
  • Build interview practice from the job description, resume facts, likely concerns, and stories the candidate can defend.
  • Shape STAR stories so action ownership, result evidence, lesson learned, and target competency stay clear.
  • Plan salary negotiation from offer details, priorities, market notes, fallback options, and what the candidate will not claim.
  • Turn a career-change story into a credibility bridge that uses true transferable proof rather than inflated seniority.

Main Risks

  • Resume and interview wording can imply credentials, ownership, metrics, or seniority the candidate cannot defend.
  • Generic job-search prompts often sound confident while losing the actual target role and company reason.
  • A salary or follow-up prompt should not create market claims, promises, or pressure language the user cannot support.
  • The final answer must preserve the user's real experience even when the wording becomes sharper.

Recommended Workflow

  1. Paste the target role, real experience notes, measurable proof if it exists, and any claim that must stay cautious.
  2. Pick the task page by hiring moment: resume screen, application, interview, follow-up, negotiation, or career-change explanation.
  3. Ask ChatGPT to mark unsupported metrics, weak proof, and language that could be challenged in an interview.
  4. Run a review pass for truthfulness, role fit, tone, and whether every claim traces back to the user's notes.
  5. Save reusable prompts by job-search moment, not as one universal career prompt.

Choose the first task by situation

Start with Rewrite resume bullets when the user has source notes but does not yet know the right output structure, then move to Write cover letters or Improve LinkedIn summaries only after the audience and review owner are clear.

Choose by situation

  • Choose Rewrite resume bullets when the main problem is shaping raw context into something a recruiter, hiring manager, or networking contact can inspect.
  • Choose Write cover letters when the user already has a first version and needs the next artifact in the same job seekers loop.
  • Choose Improve LinkedIn summaries when the risk is quality control, review consistency, or a clearer handoff to another person.
  • Open the role guide when the user cannot name the task yet and needs to decide whether to create, revise, review, or sanitize context first.

Avoid starting with

  • Do not start from a broad role prompt when the user already knows the concrete task.
  • Do not start from a writing prompt when the missing piece is source material or reviewer approval.
  • Do not reuse a job seekers prompt across unrelated tasks without changing inputs, constraints, and review checks.

Job Seekers pages are organized by the decision a person is trying to make, not by a long list of clever prompt phrases. The role page should help the user pick the first useful task, then the task page should carry the details: source material, variable fill, example, stronger prompt, and human review boundary.

Pick the workflow by decision

Rewrite resume bullets

Use when the next decision is the shape, review path, or reuse rule for resume bullets.

Rewrite resume bullets needs role history, measurable outcomes, tools, scope, and target job description; its review lens is resume bullets quality, achievement framing and measurable scope, and source-backed next step, not a generic writing pass.

Write cover letters

Use when the next decision is the shape, review path, or reuse rule for a cover letter.

Write cover letters needs target role, company reason, relevant proof, career story, and tone preference; its review lens is cover letter quality, company motivation and proof paragraph, and recipient-safe next step, not a generic writing pass.

Improve LinkedIn summaries

Use when the next decision is the shape, review path, or reuse rule for a LinkedIn summary.

Improve LinkedIn summaries needs target audience, career themes, proof points, keywords, and voice; its review lens is LinkedIn summary quality, headline promise and proof themes, and source-backed next step, not a generic writing pass.

Prepare interview answers

Use when the next decision is the shape, review path, or reuse rule for interview answer practice.

Prepare interview answers needs job description, resume notes, likely concerns, and interview format; its review lens is interview answer practice quality, likely questions and evidence bank, and fairness and policy fit, not a generic writing pass.

Shape STAR stories

Use when the next decision is the shape, review path, or reuse rule for STAR interview stories.

Shape STAR stories needs situation, task, action, result, lesson learned, and target competency; its review lens is STAR interview stories quality, situation compression and action ownership, and source-backed next step, not a generic writing pass.

Plan salary negotiation

Use when the next decision is the shape, review path, or reuse rule for a salary negotiation plan.

Plan salary negotiation needs offer details, market evidence, priorities, constraints, and fallback options; its review lens is salary negotiation plan quality, value proof and tradeoff list, and scope and value-risk check, not a generic writing pass.

Send follow-up emails

Use when the next decision is the shape, review path, or reuse rule for a follow-up email.

Send follow-up emails needs interview notes, recruiter name, hiring timeline, role interest, and one promised follow-up item; its review lens is follow-up email quality, interview recap and hiring timeline, and recipient-safe next step, not a generic writing pass.

Explain a career change

Use when the next decision is the shape, review path, or reuse rule for a career-change explanation.

Explain a career change needs past experience, new target role, transferable proof, and credibility gaps; its review lens is career-change explanation quality, transferable proof and credibility bridge, and source-backed next step, not a generic writing pass.

Open a prompt workbench

Review-first run

Rewrite Resume Bullets: keep bullet rewrite table with metric slots sourced

Turn rough resume bullets notes into resume bullets; use the prompt, sample input, rejection rules, and review checklist together. resume bullets review starts at the moment where a bullet can sound stronger by implying a metric the candidate cannot defend.

Turn role history, measurable outcomes, tools, scope, and target job description into resume bullets for a recruiter, hiring manager, or networking contact.

Bring first
Old bullet: helped with tickets and trained people. Need bullets for SaaS customer success role, no fake numbers, can mention Zendesk and onboarding. Examples for rewrite resume bullets help only when they keep the source note visible while shaping bullet rewrite table with metric slots. The response should leave the source trail easy to inspect. In rewrite resume bullets, the supplied note becomes the base for resume bullets. A usable rewrite resume bullets input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Ready-to-run path

Write Cover Letters: avoid Prompts should help users clarify true

Build a cover letter from target role, company reason, relevant proof, career story, and tone preference, then inspect true experience, measurable proof, and target role fit and the handoff before it reaches a recruiter, hiring manager, or networking contact. cover letters stays close to a hiring workflow where claims must survive recruiter or interviewer follow-up, which keeps ChatGPT from drifting into generic advice.

Turn target role, company reason, relevant proof, career story, and tone preference into a cover letter for a recruiter, hiring manager, or networking contact.

Bring first
I managed scheduling, inventory counts, and shift handoffs. Want to sound analytical without pretending I already worked as an analyst. paragraph map tied to the target role needs the source note, output shape, and review owner in the same pass. The prompt run should carry the rough note forward. a cover letter should use the note as its source. Before job seekers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if
Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Ready-to-run path

Improve Linkedin Summaries: keep profile summary with proof and keyword lines sourced

Use this LinkedIn summaries page to turn target audience, career themes, proof points, keywords, and voice into a LinkedIn summary with examples, rejection rules, and a human review pass. LinkedIn summaries review starts at the moment where linkedin summary for job seekers can sound useful while hiding the missing detail a reviewer needs.

Turn target audience, career themes, proof points, keywords, and voice into a LinkedIn summary for a recruiter, hiring manager, or networking contact.

Bring first
Mention onboarding, ticket triage, Zendesk, coaching two teammates, customer empathy, and target CSM role. No fake metrics or buzzwords. Examples for improve linkedin summaries help only when they keep the source note visible while shaping profile summary with proof and keyword lines. The working prompt should keep this as the factual base. In improve linkedin summaries, the supplied note becomes the base for a LinkedIn summary. A usable improve linkedin summaries input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Review-first run

Prepare Interview Answers: keep answer bank with risk and proof notes sourced

A real-use interview answers page with a field note, runnable prompts, repair instructions, and checks for true experience, measurable proof, and target role fit. interview answers review starts at the moment where interview prep can turn into memorized lines without evidence, concern handling, or follow-up notes.

Turn job description, resume notes, likely concerns, and interview format into interview answer practice for a recruiter, hiring manager, or networking contact.

Bring first
Need questions about failure, cross-functional conflict, metrics, and prioritization. Also need one STAR answer outline, not a script to memorize. Examples for prepare interview answers help only when they keep the source note visible while shaping answer bank with risk and proof notes. A careful pass should keep the user's limit visible. In prepare interview answers, the supplied note becomes the base for interview answer practice. A usable prepare interview answers input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Ready-to-run path

Shape STAR Stories: prep recruiter, hiring manager, or networking contact handoff

A copy-ready star stories workflow that starts with situation, task, action, result, lesson learned, and target competency, produces STAR interview stories formatted as clear sections, bullets, and a review checklist, and flags what humans must verify. star stories examples stay close to a hiring workflow where claims must survive recruiter or interviewer follow-up, so the prompt has a real work setting.

Turn situation, task, action, result, lesson learned, and target competency into STAR interview stories for a recruiter, hiring manager, or networking contact.

Bring first
Situation was delayed shipment. I coordinated support, sales, and warehouse, gave daily updates, saved relationship. Need STAR outline, not a script. STAR story table with result evidence would be weak without the source details, so the evidence has to stay attached. The prompt should keep the approval point close to the output. Job Seekers should use the note as the base for STAR interview stories. Before job seekers run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if
Do not use the answer if it hides unsupported claims about true experience, measurable proof, and target role fit or treats uncertainty as fact.

Ready-to-run path

Plan Salary Negotiation: check value proof and tradeoff list

For job seekers, this page turns salary negotiation into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. salary negotiation needs a human pass that can replace polished filler with source-backed lines inside a salary negotiation plan before the answer is reused.

Turn offer details, market evidence, priorities, constraints, and fallback options into a salary negotiation plan for a recruiter, hiring manager, or networking contact.

Bring first
Offer is 74k, target is 80k, can trade for signing bonus or review at 6 months. Need email and talking points, respectful tone. Job Seekers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A useful run should keep the approval moment in view. a recruiter, hiring manager, or networking contact should still see the note while a salary negotiation plan is being built. Plan Salary Negotiation works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Stop before sharing if it cannot show proof, numbers, or authority that the user did not provide.

Review-first run

Send Follow-up Emails: check interview recap and hiring timeline

For job seekers, this page turns follow-up emails into a repeatable prompt process with source notes, examples, and a reviewer checkpoint. follow-up emails needs a human pass that can replace polished filler with source-backed lines inside a follow-up email before the answer is reused.

Turn interview notes, recruiter name, hiring timeline, role interest, and one promised follow-up item into a follow-up email for a recruiter, hiring manager, or networking contact.

Bring first
Need thank-you email, mention process improvement discussion, attach sample dashboard, restate interest, ask about timeline lightly. Job Seekers need more than broad ChatGPT advice here; the answer has to work against the actual note and reviewer. A useful run should keep the approval moment in view. a recruiter, hiring manager, or networking contact should still see the note while a follow-up email is being built. Send Follow-up Emails works better when the context is in named fields, because each variable can be checked before copying.
Reject if
Stop before sharing if it cannot show proof, numbers, or authority that the user did not provide.

Ready-to-run path

Explain a Career Change: use past experience and new target role

Move from a rough career change request to a career-change explanation formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. career change catches the failure point where career change for job seekers can sound useful while hiding the missing detail a reviewer needs, because that is where polished answers usually fail.

Turn past experience, new target role, transferable proof, and credibility gaps into a career-change explanation for a recruiter, hiring manager, or networking contact.

Bring first
Past work: scheduling, shrink reports, inventory counts, staff handoffs. Target: operations analyst. Need honest narrative and proof points. Reviewer approval for explain a career change has to compare the first answer with the supplied note. The response should keep the actual request visible through the edit. Start explain a career change from the rough request before shaping a career-change explanation. A usable explain a career change input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if
Ask for a correction if it ignores the original notes and answers from general knowledge instead.