review-resume

## 3. Concision Length is fine, since you're well within one page. The issue is that you're under-delivering. Quillstack has 4 bullets, but three are only a few words each. Ferrow has just 2. Aim for 3-5 substantive bullets per role, especially for your current one. You have room to add real content. ## 4. XYZ+S Formula Only the approvals bullet comes close. Here's how it could look fully built out: > *Current:* "Worked with engineering on the new approvals feature, which cut invoice approval time from 5 days to 2" > > *Stronger:* "Reduced invoice approval time 60% (5 days → 2) by leading discovery and delivery of a new approvals workflow with a team of [N] engineers and [N] designer(s), driving [adoption %/retention/expansion revenue] among [customer segment]" Your other bullets need the same treatment: - *"Ran A/B tests on the onboarding flow"* → What changed, and by how much? Activation rate? Time-to-value? Trial conversion? "Increased onboarding completion from X% to Y% by running [N] A/B tests on…" - *"Wrote specs"* → Specs for what, and what shipped as a result? Cut this or fold it into a bullet with an outcome. ## 5. Professional Email **skaterboi99@example.com** should change. For senior roles, recruiters notice this, and it can undercut an otherwise strong application. Create something like **jordan.vale@gmail.com**. Your contact line is also missing a **phone number** and **LinkedIn URL**, both of which recruiters expect. ## 6. Tailoring to the Job I'd love to see the posting you're targeting. In the meantime, senior B2B SaaS PM postings typically emphasize: - Roadmap ownership and prioritization - Pricing and packaging - Revenue, ARR, retention/churn, expansion - Customer discovery and research - Cross-functional leadership (Eng, Design, Sales, CS) - Data and experimentation You touch on several of these (roadmap, pricing, customers, A/B testing), but only as thin fragments. Once you share a posting, I can help you mirror its language naturally. Also lead each role with your bullets most relevant to the target job. ## 7. Showcasing Product and Business Skills This is the biggest gap. Your skills are present but invisible: - *"Helped with pricing"* → Pricing is one of the most valuable skills in B2B SaaS, so don't undersell it. What was your role? What changed? "Redesigned pricing tiers based on [analysis/customer interviews], increasing ARPA by X% / improving conversion by Y%." - *"Talked to customers"* → "Conducted [N] customer interviews across [segment]; synthesized findings into [decision], which reprioritized the roadmap toward [feature] and [result]." - *"Responsible for the roadmap"* → Describe how you prioritized (framework, inputs, trade-offs) and what the roadmap delivered. Even if the numbers aren't perfect, rough, defensible figures beat none. Use "~" where needed, and only claim what you can speak to in an interview. ## 8. Structure and Order Your order (Summary → Experience → Education) is right. What's missing is a complete contact block (phone, LinkedIn, email). If you have any PM certifications (Reforge, Pragmatic, etc.) or a short technical skills line (SQL, Amplitude, Mixpanel, Jira), add them after Education. Both are optional. ## 9. Early-Career / Career-Changer Guidance This doesn't apply to you. You have 6 years of PM experience, so there's no need to lean on coursework or side projects. Your APM-to-PM progression is a plus, and you can make it more visible by showing increasing scope between roles. ## 10. Standard Titles and Language - **"Product Ninja"** is the biggest flag. It doesn't communicate level, and ATS filters and recruiters search for standard titles. If your official title was "Product Ninja" but you worked as a Product Manager, you can write **"Product Manager"** and explain the context in interviews. Keep it honest: use the title that reflects your actual scope, and be aware that employment verification may show the official title. Only use "Senior Product Manager" if that's genuinely accurate. - **Dates:** Use Month-Year (e.g., "Mar 2021 – Present"), not just years. - **Verbs:** Use consistent, strong ones: Led, Launched, Increased, Reduced, Owned. Avoid "Helped with," "Talked to," and "Worked with." They undersell your ownership, which is what senior roles hire for. --- ## Quick Rewrite Skeleton **JORDAN VALE** Denver, CO | (xxx) xxx-xxxx | jordan.vale@gmail.com | linkedin.com/in/… **SUMMARY** Product Manager with 6 years in B2B SaaS… *(see above)* **EXPERIENCE** **Product Manager**, Quillstack (B2B invoicing software) | *Mon YYYY – Present* - Reduced invoice approval time 60% (5 days → 2) by leading… - Owned roadmap for [product area], prioritizing [N] initiatives using [framework], delivering [outcome] - Redesigned pricing/packaging…, resulting in [metric] - Conducted [N] customer interviews…, leading to [decision/result] **Associate Product Manager**, Ferrow (HR software) | *Mon YYYY – Mon YYYY* - Increased onboarding [activation/completion] from X% to Y% by running [N] A/B tests… - Defined requirements for [feature(s)] with [team], shipping [result] - *(Add 1-2 more with outcomes)* **EDUCATION** B.A. Economics, [University], 2019 --- ## Wrapping Up You're in good shape, Jordan. You have the experience, but the resume doesn't show it yet. Your top priorities: 1. Fix the email and add phone and LinkedIn. 2. Replace the summary with specific evidence. 3. Rewrite the vague bullets with metrics and ownership, especially pricing and customer research. 4. Use a standard job title and drop the "I" statements. If you send me your updated draft, plus a target job posting if you have one, I'm happy to take another pass.