Tech & product example
Product management resume example
A product management resume example for Berlin and European B2B SaaS roles. Five years from engineer to PM with outcome metrics, cross-functional framing and discovery evidence — the profile funds and scale-ups screen when hiring operator-PMs who can still read a technical spec.
Why this resume is shaped this way
Elena moved engineer → PM — experience shows the split with shipping metrics in both eras. PM bullets lead with retention, ARPU and integration adoption; engineering years prove technical credibility without dominating the page. Cross-functional language (discovery, RICE, stakeholders) appears in outcomes, not buzzword headers. Slate template suits Berlin startup and scale-up applications. No custom section — portfolio features belong as shipped outcomes in bullets. Ex-engineer PMs should not list every language; SQL basics and API fluency are enough.
Professional Summary
Product manager with five years across engineering and product in B2B SaaS. Ex-software engineer; owns activation, retention and integrations with measurable outcomes and structured discovery.
Experience
- Owned activation funnel; raised D7 retention from 28% to 37% in two quarters
- Shipped integrations roadmap covering Salesforce and HubSpot used by 40% of accounts
- Ran discovery with 30 customers; prioritised bets using RICE and opportunity scoring
- Partnered with engineering on API versioning; cut integration breakage incidents 60%
- Launched onboarding redesign lifting trial-to-paid conversion 9%
- Defined success metrics and event taxonomy with data team for funnel analytics
- Built billing and subscription APIs in TypeScript; reduced payment failures 15%
- Shipped feature flags enabling gradual rollout for 3 major product releases
Education
Focus: software systems and human-computer interaction
Skills
Languages
Slate template · see layout
What recruiters look for
- Outcome metrics — retention, conversion, ARPU — with time bounds
- Discovery and prioritisation frameworks named with context
- Cross-functional partnership with engineering and data
- Ex-engineer credibility without engineering-heavy resume
- B2B SaaS scope — integrations, activation, enterprise buyers
- Chronological PM progression from APM to PM
- One page for five years unless multiple product lines need space
Common mistakes
- Engineering resume with “PM” title swapped in
- Feature lists without retention or revenue outcomes
- Buzzword prioritisation with no RICE or discovery evidence
- Hiding engineering years when they differentiate ex-engineer PMs
- Two pages of roadmap prose without metrics
ATS keywords
| Keyword | Why it matters |
|---|---|
| Activation | Funnel ownership |
| Retention | North-star metric |
| RICE | Prioritisation |
| Discovery | Customer research |
| B2B SaaS | Sector context |
| Integrations | Platform work |
| Roadmap | Planning signal |
| Cross-functional | Stakeholder work |
Frequently asked questions
Lead with product outcomes — retention, conversion, discovery. Keep engineering years short with technical credibility bullets only.