Senior Product Manager, Shared Platform

Campminder is a company that builds software for summer camps, focusing on creating meaningful experiences for kids. They are seeking a Senior Product Manager for Shared Platform Services who will own the product vision and roadmap, ensuring that shared services are built effectively to serve both internal product teams and external users.

Responsibilities:

• Own the product vision, strategy, and roadmap for a subset of Campminder's Shared Services — which may include identity and authentication, communications, and payments and financials — driving initiatives from discovery through delivery
• Build for two sets of customers simultaneously: the product teams who depend on shared services being reliable, well-documented, and easy to integrate — and the camp directors, staff, and families who experience them directly
• Lead ongoing discovery with camp directors, camp staff, families, and internal engineering teams to understand how they experience shared services — where the friction is, and what great looks like — then translate those insights into clear, well-scoped product decisions
• Partner closely with engineering to shape the architecture of each shared service — ensuring they're extracted cleanly from existing products, built to serve multiple products, and designed to evolve without breaking the teams that depend on them
• Define success metrics for each service area and hold yourself accountable to them — tracking adoption, reliability, and product team satisfaction, and using what you learn to sharpen the roadmap
• Evaluate build, buy, and integrate decisions for shared service tooling - assessing the vendor landscape and making recommendations that don't constrain what we want to build long-term
• Serve as the connective tissue between the Shared Services teams and the broader platform and product organization, ensuring what gets built here is understood, adopted, and built on across all products
• Use AI prototyping tools — Lovable, Bolt, Claude Code, or similar — to rapidly build working prototypes with customers, compressing the feedback loop between idea and validated product direction

Requirements:

• Meaningful experience shipping platform, infrastructure, or shared services products — you've owned a roadmap that involved building capabilities consumed by other teams, and you understand what makes that different from building end-user features
• A clear understanding of what it means to have two sets of customers — internal product teams and external end users — and the judgment to balance their needs when they're in tension
• Experience in one or more Shared Service domains: communications (email, text, social), payments & financials, people & relationships, authentication, or registration (forms, enrollment)
• Strong enough technical grounding that engineers trust your input — you don't need to write the code, but you understand APIs, authentication flows, event-driven messaging, and payment infrastructure well enough to ask the right questions and push back when something doesn't add up
• Experience evaluating build/buy/integrate decisions — you've assessed vendor options against internal capabilities, weighed the tradeoffs, and made a call you could defend
• A track record of staying close to users — you've done enough discovery to catch yourself when you're building for the obvious request instead of the real problem
• The ability to move decisions forward in the face of ambiguity — balancing the urgency to ship with the reality that shared service choices are hard to reverse, and knowing when to slow down to get the design right
• Clear, direct communication across levels of technical expertise — you can explain an authentication architecture decision to a camp director who just wants to know why login is hard, and explain a camp director's mental model to an engineering team building the infrastructure underneath it
• You use AI prototyping tools — Lovable, Bolt, Claude Code, or similar — as a natural part of how you do discovery. You reach for them to compress the loop between idea and validated direction, and you bring that instinct into every product conversation