jirawatp/resume-career-toolkit / skills/executive-resume
Executive Resume
VerifiedWrite resumes for VP, C-suite, and board-level positions that emphasize strategic leadership and organizational impact. Use this skill when someone has 15+ years of experience and is targeting executive roles, or mentions "executive resume", "VP resume", "C-suite", "board resume", "senior leadership", or "strategic leadership". Also trigger for anyone describing P&L responsibility, organizational transformation, M&A experience, or board-level communication.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.7 KB |
SKILL.md
View on GitHub---
name: Executive Resume
description: Write resumes for VP, C-suite, and board-level positions that emphasize strategic leadership and organizational impact. Use this skill when someone has 15+ years of experience and is targeting executive roles, or mentions "executive resume", "VP resume", "C-suite", "board resume", "senior leadership", or "strategic leadership". Also trigger for anyone describing P&L responsibility, organizational transformation, M&A experience, or board-level communication.
---
# Executive Resume
Write a resume that speaks to boards, executive recruiters, and PE/VC partners.
## How Executive Resumes Differ
An executive resume does not list what you did. It communicates your leadership brand: what kind of leader you are, what transformations you drive, and what scale you operate at.
**Length:** 2-3 pages (acceptable at this level)
**Audience:** Executive recruiters, board members, CEOs, CHROs
**Tone:** Strategic, outcome-focused, transformation-oriented
## Structure
### Executive Profile (replaces Summary)
3-5 sentences establishing your leadership identity:
- Your function and operating level
- Scale (revenue, headcount, geography)
- Signature achievements (2-3 with numbers)
- Leadership philosophy in one line
### Career Highlights
A standalone section of 4-6 bullets representing your most significant career achievements, pulled from across all roles. These are your headline numbers.
### Professional Experience
For each role, include:
- Company name with context (revenue, headcount, stage, industry)
- Your reporting structure and span of control
- P&L or budget responsibility
- 4-6 bullets focused on transformation narratives: "Inherited [situation]. Drove [strategic change]. Achieved [result at scale]."
### Board and Advisory Roles
List separately with company, your role (Board Director, Advisor, Observer), and one line of context.
### Education and Executive Development
Degrees, executive programs (Harvard AMP, Stanford SEP, etc.), board certifications.
## Executive Language
Use strategic verbs: Spearheaded, Orchestrated, Championed, Architected, Steered, Transformed, Scaled
Avoid tactical verbs: Managed, Handled, Assisted, Helped, Worked on
Every bullet should answer "so what?" at the organizational level. Not "improved the process" but "redesigned operations, improving EBITDA margins from 12% to 28% and positioning the company for a $400M exit."
## Confidentiality
When current or former employer data is sensitive:
- Use percentages instead of absolute numbers
- Use ranges for revenue and headcount
- Describe relative improvement without revealing proprietary figures
- Never name undisclosed acquisition targets or strategies
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |