Product Manager Resume
Writes product management resumes for associate, growth, platform, technical and senior...
Install
npx skills add reactive-resume/reactive-resume --skill product-manager-resume -g -a claude-code -y- Repository
- reactive-resume/reactive-resume45.2k
- Category
- Marketing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 963 tokens
- Runs scripts
- No, instructions only
What it does
Writes product management resumes for associate, growth, platform, technical and senior product roles. Shows customer problems, prioritization, decisions and outcomes with accurate attribution; use project-manager-resume for delivery governance rather than product direction.
Product Manager Resume
Use the user's evidence, never facts or numbers from worked examples. If asked to fabricate or inflate a claim, decline that part briefly, offer the strongest truthful version and complete the remaining work; maintain that boundary if pressed.
Make product judgment visible, not just a list of launches and ceremonies. Work from the user's facts without requiring an account.
Gather the right evidence
Clarify product versus project management, the target level, product type and users. Ask about the problem, discovery evidence, decisions the user owned, collaborators, constraints, what shipped and what was learned or measured afterward.
| Product work | Evidence prompts |
|---|---|
| Discovery/0-to-1 | User problem, interviews or other actual research, alternatives, validation and launch status |
| Growth | Funnel stage, hypothesis, experiment role, cohort, period and guardrail metrics |
| Platform/technical | Developer or internal customer needs, adoption, interface tradeoffs and operational constraints |
| Enterprise | Customer workflow, rollout, permissions or integrations, adoption and retention context |
| Senior leadership | Portfolio decisions, strategy, allocation and cross-team influence, separated from direct-report management |
Treat these as editorial prompts, not universal hiring criteria. “Worked with engineering” does not establish technical architecture ownership, and “ran standups” does not establish product strategy.
