Job Summary
The Senior Platform Product Manager I owns the product strategy, roadmap, and outcomes for an assigned set of shared modules within the CaseWorthy Platform: capabilities built once and embedded across ClientTrack, MediSked, and ServTracker, along with the APIs, events, and AI-ready interfaces that connect them to our applications and to Cara. Specific module assignments are set by product leadership based on platform need.
Platform product management at CaseWorthy is a service role. The direct customers of this role are the application teams that build on what it ships, and through them, every organization that uses ClientTrack, MediSked, and ServTracker. The central discipline is building a capability once so every application benefits, rather than building the same thing separately inside each application. A capability that only one application can use is not yet a platform capability, and this role is accountable for knowing the difference.
This is a senior individual contributor role reporting to the Director of Product Management. It partners closely with engineering, UI/UX, application product managers, the Cara team, and go-to-market teams, and works within an AI-assisted product development model in which AI tools help research, draft, and analyze while product managers own the judgment, validation, and decisions.
Responsibilities
- Platform Strategy & Roadmap: Define and maintain the strategy and roadmap for assigned shared modules and platform capabilities, aligned to the overall direction of the CaseWorthy Platform. Every roadmap item names the applications and teams that will consume it and the interface through which they will consume it. When a capability has no named consumer, this role asks whether it should be built at all.
- Build Once, Use Everywhere: Ensure capabilities needed by more than one application are built as shared modules rather than inside a single application's codebase. Identify one-off builds early, route integration needs to Automate, and help application teams adopt shared capabilities in place of local workarounds.
- Application Teams as Customers: Treat application product and engineering teams as the primary customers of the platform. Understand their roadmaps, customer commitments, and constraints; reconcile competing requests into a single shared roadmap; and help decide where requested work should be built, which is not always with the team that raised it.
- APIs, Events & Contracts: Define product requirements for the APIs, events, and integration contracts that assigned capabilities expose. Uphold the platform's patterns: shared modules publish events and applications subscribe and interpret them within their own models; internal teams, integration partners, customers, and AI assistants all consume one supported, documented, versioned API surface; and the supported way is the easy way.
- AI Readiness & Cara Enablement: Partner with the Cara team so assigned capabilities are exposed through supported application APIs that Cara can act through. Design AI-enabled experiences on the principle that Cara recommends and humans decide, with configurable autonomy whose boundaries are always set by people.
- Discovery & Problem Definition: Lead continuous discovery with customers, implementers, support, and application teams. Frame problems before solutions; gather evidence from customer conversations, usage data, and product signal channels; and apply a consistent scoring framework to prioritize.
- Requirements & Delivery: Write clear product requirements documents, solution definitions, user stories, and acceptance criteria. Own and prioritize the backlog, work daily with engineering on scope and tradeoffs, and ensure timely, high-quality delivery.
- AI-Assisted Product Practice: Use AI tools and agentic workflows as an everyday part of the job, including research, feedback synthesis, requirements drafting, and usage analysis. Review and validate everything AI produces before it becomes a decision. AI speeds up the writing; the learning and the judgment stay with the product manager.
- Experience & Accessibility: Partner with UI/UX to design for every audience these capabilities serve: administrators and implementers who configure them, developers who integrate with them, and caseworkers and clients who use what gets built. Hold documentation, developer experience, and accessibility to the same standard as the interface.
- Outcomes & Measurement: Define success measures for assigned capabilities and track adoption across applications and customers. Pair every volume measure (such as the number of integrations, events, or API calls) with a quality measure (such as error rates, time to configure, or customer-reported reliability) so the team optimizes for real value rather than activity.
- Data Stewardship: Protect the people our customers serve. Work with de-identified data in discovery, testing, and AI work, and build privacy and security requirements for protected health information and personally identifiable information into every capability from the start.
- Release & Market Readiness: Partner with Product Marketing, Training & Documentation, Professional Services, and Support so every release is ready to sell, implement, and support, including packaging and positioning input for shared modules offered as add-on capabilities.
- Stakeholder Communication: Communicate roadmap, progress, tradeoffs, and customer impact clearly to product leadership, engineering, application teams, and go-to-market teams. Write decisions down where others can find them.
- Ability to travel nationwide, up to 10% annually.
- Performs other duties as assigned.
Required Skills & Qualifications
- Bachelor's degree in a relevant field (e.g., Computer Science, Information Systems, Business, Human-Computer Interaction) or equivalent practical experience.
- 5–8 years of product management experience delivering software in a SaaS environment, including at least two years owning a platform, API, integration, or shared-services product used by other product or engineering teams.
- Technical fluency sufficient to partner on design decisions: reading API specifications, reasoning about data models and multi-tenant architecture, and understanding event-driven and integration patterns. Writing code is not required.
- Demonstrated, regular use of AI tools in product work, with sound judgment about when AI output needs verification.
- Proven experience owning a backlog and working directly with engineering in an Agile setting (Scrum/Kanban), including writing clear requirements, user stories, and acceptance criteria.
- A track record of reconciling competing needs from multiple internal teams into one roadmap, and of saying no with clear reasons.
- Strong understanding of user-centered design for both technical administrators and non-technical end users, including accessibility standards (WCAG).
- Strong analytical skills: able to define metrics, interpret usage data, and turn evidence into prioritized decisions.
- Excellent written and verbal communication, presentation, and stakeholder management skills.
- Comfort with ambiguity, and with modernizing capabilities while keeping existing customers whole.
Preferred Skills & Qualifications
- Experience in health and human services (HMIS, aging services, HCBS, behavioral health, workforce development) or with government and nonprofit customers and public-sector procurement.
- Experience owning shared services or cross-product capabilities, such as integration, workflow automation, or administration tools, used by multiple products or teams.
- Exposure to exposing application capabilities to AI assistants, such as Model Context Protocol (MCP), tool design, or AI evaluation.
- Familiarity with privacy and security requirements for sensitive data, such as HIPAA, 42 CFR Part 2, and HMIS data standards.
- Experience with Jira, Jira Product Discovery, and Confluence.
- Experience mentoring or guiding other product professionals, formally or informally.
We are unable to sponsor employment visas or support STEM OPT work authorization for this role.