ChatGPT Prompt to Rewrite an Engineer Resume for Senior Roles

What this prompt does

This prompt rewrites an engineer's resume for senior roles, optimizing for outcome-driven bullets that survive a hiring screen. You give it a [target_title], a [company_type], and your current [resume], and it returns a one-page Markdown rewrite under strict rules: every bullet starts with an action verb, at least 70% of bullets include a number, pure-responsibility lines are cut, and the skills section lists only tools used in the last two years.

The rules do the heavy lifting. Forcing a number into at least 70% of bullets pushes you to quantify impact — time saved, revenue, latency, users — which is exactly what separates a callback from a pass when a reviewer skims a stack of resumes in seconds. Dropping responsibility-style bullets without outcomes removes the filler that makes mid-level resumes blur together and read like a job description. The [target_title] and [company_type] shape tone and emphasis, so the same career reads differently for a fast-moving startup than for a mid-sized product SaaS, and the markdown output drops straight into a document for final polish.

When to use it

• Applying for a [target_title] role and your current resume reads as a list of duties
• Tailoring one base resume to a specific [company_type] without rewriting from scratch
• Cutting a two-page resume down to a single focused page
• Converting "responsible for" bullets into outcome-and-number bullets
• Refreshing a skills section that still lists tools you have not touched in years
• Preparing for a senior screen where reviewers skim for measurable impact

Example output

You get a clean, one-page Markdown resume: a tightened summary, experience entries where each bullet opens with an action verb and most carry a concrete number, and a skills section pruned to tools from the last two years. Responsibility-only bullets are gone. It is ready to paste into a document and adjust, not a vague set of suggestions.

Pro tips

• Set [target_title] to the exact role on the posting — "Senior Full-Stack Engineer" steers emphasis differently than "Staff Backend Engineer"
• Match [company_type] to where you are applying; a mid-sized product SaaS rewrite reads differently than a FAANG-tier one
• Paste a complete [resume], including rough numbers you remember, so the model quantifies rather than inventing figures
• After the rewrite, verify every number is true — the model will keep whatever you gave it, so fabricated metrics are on you
• If a real achievement has no metric, add an honest qualifier ("reduced manual steps") rather than letting the bullet get cut
• Re-run with a different [target_title] to see how emphasis shifts before you settle on one version
• Keep the skills section honest to the last two years; listing tools you have not touched invites questions you cannot answer in the screen