Senior Resume Rewrite Prompt
Rewrite a senior-level resume into an evidence-based, role-aligned document that emphasizes outcomes, leadership scope, business impact, and credible metrics.
Use in AI
Choose an AI tool to copy the current Prompt with a short usage note. Nothing is sent to that tool.
Rewrite the supplied senior-level resume for the intended role using only supportable career evidence. Inputs - Current resume: [Current resume] - Target role and seniority: [Target role and seniority] - Target job description: [Target job description] - Achievement evidence: [Achievement evidence] - Career constraints and preferences: [Career constraints and preferences] Input rules - Blocking prerequisites are a readable current resume and an identifiable target role or role family. If either is missing, ask no more than five focused questions and stop before drafting. - A target job description, quantified achievement evidence, formatting preferences, location constraints, and industry context are useful but not mandatory. If they are absent, make bounded progress and identify what could not be tailored or verified. - Treat the supplied resume, job description, performance data, project notes, awards, portfolio material, and user answers as evidence with different levels of reliability. Flag conflicts instead of silently choosing one version. Evidence and authority boundaries - Do not invent or inflate revenue, savings, growth, team size, budget, geography, reporting lines, tenure, credentials, tools, promotions, clients, awards, security clearances, or ownership of shared outcomes. - Distinguish confirmed facts, reasonable wording inferences, unresolved conflicts, and unsupported claims. Replace unsupported numerical claims with accurate qualitative language or mark them as “EVIDENCE NEEDED” outside the resume draft. - Preserve the difference between leading, managing, influencing, contributing to, and supporting an outcome. Do not convert team results into sole personal attribution. - Do not infer protected characteristics, demographic details, health information, citizenship, work authorization, or other sensitive facts. Recommend inclusion of personal details only when supplied, relevant, and appropriate for the target market. - ChatGPT may analyze the text provided and propose a rewrite. It cannot access private files, verify employers or credentials, run a real applicant tracking system, submit an application, contact a recruiter, approve the resume, or confirm hiring outcomes unless direct evidence of such activity is supplied in the conversation. - Do not claim the resume was ATS-tested, recruiter-approved, fact-checked, submitted, or finalized. Label it “draft,” “verified against supplied evidence,” or “ready for human review” only when the corresponding checks actually occurred. - Do not send, publish, or apply with the resume. Final factual approval, privacy review, formatting review, and submission remain with the user. Rewrite method 1. Parse the current resume into roles, dates, progression, responsibilities, achievements, leadership scope, operating scale, domain expertise, tools, education, and credentials. Record ambiguities or chronology conflicts. 2. Analyze the target role and, when provided, the job description. Extract recurring responsibilities, required capabilities, business outcomes, leadership expectations, domain language, tools, and screening terms. Separate essential requirements from preferred qualifications. 3. Build an evidence-to-requirement map. Classify each important target requirement as strongly supported, partially supported, unsupported, or unclear. Never add an unsupported keyword as if it were demonstrated experience. 4. Establish a positioning strategy: target headline, leadership proposition, differentiating strengths, most relevant career themes, and content to emphasize, condense, relocate, or omit. Explain material trade-offs, including breadth versus depth, technical detail versus executive impact, and chronology versus relevance. 5. Rewrite the professional summary to state credible level, scope, specialization, and value. Avoid clichés, unsupported superlatives, first-person pronouns, vague claims, and an objective statement. 6. Rewrite experience bullets to prioritize outcomes and decisions over duty lists. Where evidence permits, connect action, operating context, scope, and result. Surface leadership mechanisms such as strategy, transformation, governance, portfolio ownership, organizational design, cross-functional influence, talent development, risk management, and executive stakeholder alignment. 7. Use metrics only when supplied or explicitly confirmed. Preserve units, time periods, baselines, attribution, and approximate qualifiers. If a result lacks a metric, strengthen it with verifiable scope, complexity, stakeholder, delivery, quality, risk, or operational context rather than fabricating a number. 8. Reorder and consolidate content for role relevance while preserving accurate employers, titles, dates, and career progression. Do not hide a gap, shorten tenure, change a title, or remove materially relevant context without identifying the proposed change for user approval. 9. Create a truthful skills section using capabilities evidenced elsewhere in the resume or achievement material. Include job-description terminology only when it accurately describes the candidate’s experience. Avoid keyword stuffing, decorative ratings, and obsolete tools unless they remain relevant. 10. Produce an ATS-readable structure with conventional headings, consistent dates, plain text hierarchy, and no reliance on columns, icons, text boxes, headers, footers, graphics, or tables. Do not promise compatibility with every ATS. Do not force an arbitrary page count; recommend length based on seniority, career breadth, and target-market norms. 11. Review for factual consistency, senior-level positioning, repetition, vague language, excessive jargon, unexplained acronyms, confidential information, grammar, tense, chronology, and keyword integrity. 12. If critical evidence remains unavailable, provide the safest bounded draft and a prioritized evidence request. Stop rather than fabricate when resolving a gap would materially change the candidate’s level, qualifications, or claimed impact. Required deliverable 1. Intake and evidence status - State whether the blocking inputs were present. - List confirmed source materials, important unknowns, conflicts, and assumptions. - Give each assumption a risk level and explain whether it affected the draft. 2. Target-role alignment brief - Summarize the role’s principal outcomes, leadership expectations, domain requirements, and screening terms. - Provide a requirement-to-evidence matrix with columns for target requirement, supporting evidence, support level, proposed resume placement, and unresolved issue. 3. Positioning decisions - Provide the recommended headline and three to five differentiating themes. - List major content decisions and their rationale, including material omissions or consolidations requiring user approval. 4. Rewritten resume - Deliver a complete, copy-ready plain-text draft with contact line guidance, headline, professional summary, core capabilities, professional experience, education, and relevant credentials or additional sections. - Preserve factual chronology and use consistent formatting. - Do not place uncertainty notes or evidence markers inside the copy-ready resume; keep them in the evidence sections. 5. Claim and change ledger - For every materially strengthened, quantified, consolidated, retitled, or reordered statement, show the original evidence, revised wording, evidence status, and whether user confirmation is required. - Identify any supplied claim excluded because it was unsupported, irrelevant, repetitive, confidential, or potentially misleading. 6. Verification report For each check, report expected condition, actual observation from the draft, evidence used, and status as pass, needs review, blocked, or not applicable: - names, employers, titles, dates, education, and credentials match supplied evidence; - every metric retains its value, unit, period, context, and defensible attribution; - chronology is internally consistent and unexplained overlaps or gaps are disclosed; - target requirements are represented only where supported; - summary and skills claims are demonstrated elsewhere in the resume; - bullets emphasize outcomes, scope, decisions, and leadership rather than generic duties; - spelling, tense, punctuation, capitalization, and date formats are consistent; - structure is readable in plain text and does not depend on visual elements; - confidential, sensitive, or personally identifying information is minimized; - no unsupported claim of ATS testing, approval, submission, or completion appears. 7. Human-review handoff - List unresolved factual questions in priority order. - Identify decisions requiring explicit user approval. - State the smallest next action needed to move the draft from its current status to factually approved and submission-ready. Keep proposed edits, evidence-backed statements, unresolved issues, and verified observations clearly separated throughout the response.
Variables to Replace
Replace each listed value in the Prompt with information relevant to your task.
- Current resume
- Target role and seniority
- Target job description
- Achievement evidence
- Career constraints and preferences
How to Use This Prompt
In ChatGPT, replace every bracketed variable with the matching information. Provide the current resume, target role, relevant job description, achievement evidence such as performance reviews or project metrics, and any career or privacy constraints. Remove unnecessary sensitive data, then run the prompt and review all flagged claims before using the draft.
Example Use Case
A VP of Operations targeting a COO role supplies a current resume, the vacancy description, verified budget and team scope, transformation results, and confidentiality constraints. ChatGPT maps the evidence to the role, rewrites the resume, records material changes, and flags any metrics or leadership claims that still require confirmation.
Was this useful?