Group Product Manager

About the Role

The best product leads don’t choose between building and coaching. They do both, in the same week.

Online Donations is how donors give to nonprofits through Fundraise Up: Checkout Modal & Elements, Campaign Pages, and Gift Cart. As Lead Product Manager, you own the long-term direction of this product line, run a product area yourself, and make a team of 2–4 Product Managers stronger. Your work shapes how fast and easily millions of donors can give, and how much more nonprofits raise because of it. About 70% of your time is hands-on product work; the other 30% is leading people and the team.

Key Responsibilities

• Own the long-term strategic roadmap for Online Donations, built together with your PMs, and make sure their quarterly plans ladder up to it. Present and defend it with the Director of Core Products & Platform, the VP of Product, and cross-functional partners.
• Own a product area end to end: discovery, specs, delivery, and metrics (conversion, adoption, GPV, reliability).
• Write the cross-team specifications no single PM can own alone, making scope, dependencies, sequencing, and risks explicit, and set the bar for spec quality on your team.
• Step in for any PM during vacation, overload, or a critical launch so their area keeps moving at the same quality.
• Coach 2–4 Product Managers through weekly 1:1s, concept and spec reviews, growth plans, and performance reviews, and take part in hiring and onboarding new PMs.
• Build a continuous discovery culture: talk to nonprofits and donors regularly, run market and competitor analysis, and make sure roadmap decisions trace back to evidence.
• Own your team’s operating rhythm (planning, spec reviews, demos, retros) and improve predictability, cycle time, and review rounds over time.
• Help your PMs align across Engineering, Design, Analytics, and neighbouring teams, and set up how they work with GTM (Marketing, Sales, Customer Success, Support) on launch readiness, enablement, and feedback loops.
• At Fundraise Up, AI is a default tool, not an experimental one. We expect every team member to actively use AI in their day-to-day work, identify where AI can change the shape of problems in their function, and grow their fluency as the tools evolve. In this role, that means using AI for research, synthesis, spec writing, and communication, and helping your PMs adopt AI-enabled workflows.

Skills and Qualifications

• 6+ years in Product Management
• 2+ years leading or mentoring Product Managers, ideally including running performance reviews
• A strong individual track record: products you owned end to end, with measurable results
• Excellent spec writing, including complex specs that span several teams or systems
• Hands-on continuous discovery: regular customer interviews, market and competitor analysis, and turning insights into decisions
• Experience building and managing a long-term strategy and roadmap across several related products
• Proven ability to drive cross-team initiatives without formal authority, including work with GTM teams on launches and enablement
• Experience setting up team processes (planning, rituals, delivery tracking) and improving them based on results
• Strong analytical mindset: you define metrics and make data-informed decisions
• Clear written and verbal communication with engineers, designers, and leadership
• Languages: Fluent Russian (required, as you’ll be working in a Russian-speaking team) and English at C1 level, both written and spoken.

Nice to Have

• Experience in B2B SaaS or high-growth technology companies
• Experience with online donations, fundraising, payments, or checkout products — conversion-focused flows used by end customers
• Experience with platform or API products
• Experience using AI in day-to-day product work

You’ll Thrive Here If You…

• Still love writing the hard spec yourself, even when you lead a team
• Measure your success by how much less your PMs need you over time
• Talk to customers because you want to, not because a process says so
• Switch between your own work and someone else’s without losing quality or patience
• Give direct feedback and ask for it in return
• Spot a dependency early and fix it before it becomes a release-day surprise
• Care more about the outcome than about who gets credit
• Keep trying new tools and better ways of working, AI included