with the skill
Hi Jordan—there’s a solid foundation here: experience across two B2B software products, progression from Associate PM, and a measurable customer outcome. **Cutting invoice approval time from five days to two is your strongest achievement.**
The main issue: the resume currently reads like a list of supporting responsibilities, not evidence of senior-level product ownership. For senior B2B SaaS roles, make your decisions, scope, and business impact much more visible.
Here’s how I’d strengthen it across 10 areas.
## 1. Replace the generic summary
Your current summary—“I am a passionate product person…a strategic thinker and team player”—doesn’t distinguish you from other applicants.
Use two or three lines describing your domain experience and strongest demonstrated result. For example:
> Product manager with B2B SaaS experience in invoicing and HR software. Partnered with engineering to deliver an approvals feature that reduced invoice approval time by 60%, from five days to two.
This is a credible starting point. Once you establish your ownership and commercial impact, add those details to strengthen the senior-level positioning.
## 2. Remove personal pronouns—and responsibility language
Remove “I” from both the summary and “I was responsible for the roadmap.”
Show the rest (129 more lines)
More importantly, replace passive responsibility statements with what you actually decided and accomplished.
Instead of:
> I was responsible for the roadmap
Use this structure, filling in only accurate details:
> Owned the roadmap for [product area], prioritizing [initiatives] based on [customer research, usage data, or business goals] to achieve [outcome].
“Owned” is appropriate only if you actually had that accountability; otherwise, describe your contribution precisely.
## 3. Keep it concise, but add substance
The resume is short enough; **underdevelopment, not length, is the problem**.
- Quillstack has four bullets—a good count—but three lack meaningful detail.
- Ferrow has two bullets, both describing activities without results.
- Aim for four or five substantial bullets for Quillstack and roughly three for Ferrow, assuming you have relevant evidence.
One strong page could work. A second page is reasonable if you have enough substantive experience—not filler.
## 4. Build bullets around outcome, metric, action, and context
Only one of your six bullets currently includes a quantified outcome. Use that as the model for the others.
Your strongest bullet can become:
> Partnered with engineering to deliver an invoice approvals feature that reduced approval time by 60%, from five days to two.
Then clarify your specific contribution: Did you discover the problem, define requirements, prioritize the feature, or lead rollout? Add that if true.
For other bullets, investigate these details:
| Current bullet | Evidence to add |
|---|---|
| “Helped with pricing” | Your analysis or recommendation; pricing model or packaging changes; impact on conversion, average contract value, revenue, or discounting |
| “Talked to customers” | Customer segment, research method, findings, and the product decision those findings informed |
| “Ran A/B tests on the onboarding flow” | Hypothesis, primary metric, result, and whether the change shipped |
| “Wrote specs” | Feature or problem, key trade-offs, collaboration, and resulting customer or delivery outcome |
Use verified figures, not estimates presented as facts. If metrics aren’t available, specific scope and documented decisions are still stronger than vague tasks.
## 5. Use a professional email address
“skaterboi99@example.com” looks casual for a senior-level application. If it represents your actual address, replace it with a name-based address such as:
> jordan.vale@[provider].com
Your name and Denver location are already easy to find.
## 6. Tailor for senior B2B SaaS roles
Without a specific job posting, exact keyword alignment isn’t possible. For this target, look for truthful evidence of:
- Product strategy and roadmap ownership
- Enterprise customer discovery
- Prioritization and trade-off decisions
- Pricing and packaging
- Adoption, retention, expansion, or revenue outcomes
- Partnership with Engineering, Design, Sales, and Customer Success
- Stakeholder alignment and influence
Your pricing experience could be particularly valuable, but “Helped with pricing” hides it. Explain what you contributed and what changed.
Keep employment in reverse chronological order; reorder bullets within each role to lead with the most relevant achievements.
## 7. Demonstrate product and business judgment
You mention useful PM activities—roadmaps, research, experiments, and pricing—but not the judgment behind them.
Senior hiring managers want to understand:
- What problem did you choose to solve, and why?
- What competing priorities did you balance?
- How did you influence the decision?
- What customer or business result followed?
For example, if accurate:
> Synthesized findings from [number] interviews with [customer segment] to prioritize [workflow improvement] over [alternative], addressing [validated customer problem].
Also show collaboration beyond engineering where it genuinely occurred. Don’t add a generic skills list as a substitute for evidence.
## 8. Complete the structure and missing details
Your section order is already sensible: contact information → summary → experience → education.
Add:
- A phone number and LinkedIn URL, if you want recruiters to use them
- Month-and-year employment dates
- Your university’s name under education
For example:
> **[University name]** — B.A. Economics, 2019
Certifications and technical skills can go after education if relevant. Include tools such as SQL or product analytics platforms only if you actually use them.
## 9. Position yourself as an experienced PM, not an entry-level candidate
With PM roles listed from 2019 onward, coursework and student projects should not be the focus.
Use that space for evidence of increasing responsibility:
- Broader product or customer scope
- Independent decision-making
- Strategic planning
- Cross-functional influence
- Mentoring, if applicable
- Commercial outcomes
The key question is not simply how long you’ve worked in product—it’s **how your ownership and impact have grown**.
## 10. Clarify “Product Ninja”
“Product Ninja” makes your function and level harder to assess.
If that is your official title, keep it transparent while adding a recognizable functional equivalent, if accurate:
> **Product Ninja (Product Manager)** — Quillstack
If it is just a creative label you chose, use your actual job title instead. Don’t upgrade it to “Senior Product Manager” unless that was your title.
## Your highest-priority changes
1. **Expand the Quillstack bullets** to show ownership, decisions, and outcomes—especially roadmap and pricing work.
2. **Lead with the 60% approval-time reduction**, clarifying your contribution.
3. **Replace the summary, email, and unclear title presentation.**
4. **Add results to Ferrow and complete the education and date details.**
Jordan, you don’t necessarily need more content—you need more evidence behind the experience already listed. These changes will help recruiters assess whether your work matches senior-level expectations. Share a revised version and a target posting, and I can help sharpen the positioning further.