Resume Bullet Rewriter (Impact + Metrics)
Rewrites flat resume bullets into accomplishment statements with scope, action, and measurable outcome — and interviews you for missing numbers instead of inventing them.
Prompt variables
2 variables detected — fill them and Copy inserts your values (0/2 filled).
Rewrite my resume bullets into accomplishment statements. Target role: {{target_role}}.
The formula: strong verb + what I did + scope/scale + measurable outcome. ("Rebuilt the billing reconciliation job, cutting month-end close from 5 days to 1 for a 40-person finance team.")
Process each bullet:
1. **Diagnose** — is it a duty ("responsible for X"), a task with no outcome, or already an accomplishment?
2. **Rewrite** — lead with a precise verb (built, negotiated, migrated, cut, won — ban: helped, assisted, worked on, was involved in, spearheaded, utilized). Include scale (users, requests, budget, team size) and the outcome.
3. **Where a number is missing, DO NOT INVENT ONE.** Insert [METRIC: specific question] — e.g. [METRIC: how many hours/week did the team save?]. Give me 2–3 such questions per bullet where impact is implied but unquantified; even a defensible estimate range from me beats a fabricated figure from you.
Rules:
- ≤ 2 lines per bullet. One accomplishment per bullet — split compound ones.
- Tailor vocabulary to {{target_role}}: mirror how that role's job posts describe the work, without keyword-stuffing.
- Cut anything that describes the team's work rather than mine, or flag it to reframe around my contribution.
- Keep my seniority honest — don't inflate "contributed to" into "led" unless I confirm I led it (ask).
After rewriting all bullets, rank them best-first for this target role and mark any bullet you'd cut entirely (weak even after rewrite) with a one-line reason.
My bullets:
{{bullets}}
Proof of work
Example outputs
Before: "Responsible for the migration of the legacy reporting system" After: "Migrated a 40-report legacy BI system to Looker over one quarter, retiring a $30k/yr vendor contract [METRIC: how many analyst-hours per week did the team save?]" Before: "Worked on improving API performance" After: "Cut p95 latency of the orders API from 1.8s to 210ms by adding read-through caching and killing three N+1 queries"
Comments (0)