Technical Product Manager

About PRM PRM is a healthcare revenue cycle management (RCM) company helping physician practices from solo practitioners to larger groups run their billing, coding, and collections smoothly. We're now building AI-powered products to modernize how that work gets done, and this role is part of that build. About the Role We're looking for a Product Manager to take true, end-to-end ownership of PRM products working directly with the CEO and our engineering team to shape the product from first idea through to client delivery. This is a hands-on ownership role, not coordination or ticket-management a great fit for someone with sharp judgment, an obsessive eye for detail, and the confidence to work closely with both engineers and business stakeholders on something being built from the ground up. What You'll Own End-to-end ownership — from idea reception to client delivery, you're accountable for a requirement exiting the pipeline as a complete, correct product capability. Problem & solution understanding — build a first-principles grasp of the RCM workflow (claims, coding, denials, eligibility, payment posting, AR) deep enough to challenge assumptions and answer "why are we building this?" Prototype & release validation — personally test every prototype and release candidate. You're the final checkpoint before anything reaches a client. Business analysis — elicit and document requirements, map processes, define acceptance criteria, and define what "done" means before development starts. Client engagement — run discovery sessions, demo the product, present releases, gather feedback. Stakeholder alignment — work daily with engineers/solution architects and business stakeholders (CEO, clients, ops) to keep scope, priorities, and trade-offs aligned. AI-driven development — shape how AI capabilities are used in the product; define AI feature behavior, evaluate model outputs, set quality bars, and understand what AI can't do. Day-to-Day Own the backlog, roadmap, and release plan Write clear PRDs, user stories, and acceptance criteria Review designs/builds in detail; give precise, actionable feedback Run structured UAT before every release; sign off on quality Conduct client calls, demos, and requirement workshops Analyze usage and edge cases to drive product improvements Prioritize ruthlessly; make fast, well-reasoned decisions to unblock the team Must-Haves 4–7+ years in product management, product ownership, or senior business analysis for software products Hands-on experience shipping AI-powered features (LLMs, ML, or intelligent automation) — understands prompting, evaluation, and AI product quality Working fluency with the tech stack (APIs, cloud, databases, integrations) to hold credible engineering conversations Strong business analysis: requirements elicitation, process mapping, spec writing Sharp eye for detail — catches the edge case everyone else missed Strong communication — can run a client demo and write a spec an engineer can build from Owns outcomes without waiting to be told; comfortable in ambiguity Nice-to-Haves Healthcare RCM, medical billing/coding, or health tech experience (strongly preferred) Familiarity with payers, CPT/ICD coding, denials, eligibility, credentialing, HIPAA B2B / enterprise SaaS experience Agile tools (Jira, Linear, Notion, Figma) Prior experience as the first/sole PM on a product What Success Looks Like 30 days: Understands PRM's RCM services, product, clients, and gaps well enough to review prototypes independently. 90 days: Full ownership of the backlog, roadmap, and validation process for PRM products. 6 months: Every release ships with their sign-off; gaps between "what was asked" and "what was built" trend toward zero. To Apply Send your CV along with short, specific answers to the following. We're less interested in polished theory and more in the details only someone who's actually done the work would know: Name one product or feature you owned end-to-end. What was the exact gap between what was asked for and what got built the first time around — and how did you catch it? Describe a specific edge case or bug that slipped past everyone else on the team before you caught it. What was it, and how did you find it? Walk through one real requirement you had to translate from a vague business ask into a spec an engineer could build from. What did the original ask sound like, and what did the final spec say?