Resume Bullet Point Rewriter for ChatGPT
Rewrite weak resume bullets into achievement statements with a strong verb, a measurable result and the method that produced it, tuned to the job you are targeting.
Fill in the variables
Prompt
<role>
You are a resume writer who has worked with recruiters at large companies and knows how applicant tracking systems and six-second human scans actually treat a resume. You turn duties into results.
</role>
<context>
Target role: {{target_role}}
Seniority: {{seniority}}
Current bullets (one per line, as they appear on my resume):
{{bullets}}
Extra facts I can add (numbers, tools, team sizes, outcomes I remember):
{{extra_facts}}
</context>
<constraints>
- One bullet in, one bullet out, same order. 12–25 words each.
- Each rewritten bullet follows: strong past-tense verb + what I did + measurable or observable result + how (method, tool or scope).
- Use only facts present in the current bullets or the extra facts. Where a number is missing, write a bracketed placeholder like [X%] and list it in the questions section; never invent one.
- No first person, no articles at the start, no "responsible for", "helped", "worked on", "assisted with".
- Prefer verbs that match the target role's level: "owned", "led", "designed", "cut", "grew", "shipped" for senior; "built", "delivered", "analyzed", "improved" for mid-level.
- Keep technical terms the ATS will look for; do not paraphrase tool names.
</constraints>
<goals>
- Bullets a recruiter can quantify at a glance.
- Language that matches the target role without exaggerating my level.
- A short list of the numbers I should go and find.
</goals>
<instructions>
1. Rewrite every bullet following the formula.
2. Mark any bullet where you had to add a placeholder with (needs number).
3. After the list, add "Questions for you": the specific facts that would turn placeholders into real numbers, phrased so I can answer in one line each.
4. Finally, flag any bullet that is still a duty rather than an achievement and suggest what evidence would fix it.
</instructions>
<output_format>
A numbered list of rewritten bullets, then "Questions for you" as a short list, then "Still weak" (only if any). No introduction.
</output_format>
Example input
Target role: Product Manager Seniority: mid-level Current bullets: - Responsible for the onboarding flow of the mobile app - Worked with engineers and designers on new features - Helped run user interviews - Managed the backlog in Jira - Wrote release notes and communicated updates to the company Extra facts: the onboarding redesign shipped in March; activation (users completing setup within 24h) went from 41% to 58%. Team was 5 engineers and 1 designer. I ran about 25 user interviews last year and kept a synthesis doc. Backlog had ~300 items, I cut it to ~120 by archiving and merging. Release notes went out every two weeks to ~200 employees.
Example output generated with Claude Sonnet 4.6 from the example input above
1. Redesigned the mobile app onboarding flow with a 5-engineer, 1-designer squad, raising 24-hour activation from 41% to 58% after the March release.
2. Delivered new features end to end with engineering and design, from problem framing through launch, in biweekly release cycles. (needs number: features shipped per quarter)
3. Conducted 25 user interviews in one year and maintained a synthesis document that fed [X] roadmap decisions. (needs number)
4. Reduced a 300-item Jira backlog to 120 by archiving stale tickets and merging duplicates, giving the squad a plannable queue.
5. Wrote biweekly release notes for 200 employees, turning engineering changes into plain-language updates the whole company read.
Questions for you:
- How many features or projects did you ship last year (or per quarter)?
- Can you name 2–3 roadmap decisions that came directly out of the interview synthesis?
- Do you know open rates or any feedback on the release notes? If not, a count of releases covered is fine.
Still weak:
- Bullet 2 is still a duty. The fix is a specific feature with its outcome, e.g. "Shipped in-app payments, adopted by 30% of active users in 60 days." Pick the one feature you are proudest of and give me its result.
Why this works & how to customize
Why it works: the formula (verb + action + result + method) is what recruiters are trained to look for, and the "no invented numbers" rule with placeholders turns the prompt into a worksheet. You get a list of exactly which facts to dig up from old reports, which is the part people skip.
How to customize: change seniority to "senior" and the verbs shift to ownership language automatically. For technical roles, add "keep every tool and language name exactly as written" is already enforced, but you can add a line listing the ATS keywords from the posting so the model works them in where true. Run the prompt once per job section, not for the whole resume at once; quality drops after about 8 bullets.
How to customize: change seniority to "senior" and the verbs shift to ownership language automatically. For technical roles, add "keep every tool and language name exactly as written" is already enforced, but you can add a line listing the ATS keywords from the posting so the model works them in where true. Run the prompt once per job section, not for the whole resume at once; quality drops after about 8 bullets.
Comments (0)
Sign in to comment.
No comments yet.