Billing Product Owner

Role Summary We are rebuilding our billing module and we want one person who owns it end to end. You will own the roadmap, write the requirements, sit with engineering and QA through delivery, and answer for whether claims go out clean and money comes back. This is a revenue cycle role as much as a product role, so you need to have lived inside United States medical billing, not just read about it. You will work directly with our Chief Product Officer, with our implementation and support teams who hear every billing complaint first, and with the provider organizations that run their revenue through our platform every day. What You Will Own Own the billing module roadmap end to end, from claim creation through payment posting, denials, and aging, and defend the sequence you choose. Write the requirements and acceptance criteria for claim generation and submission, including professional and institutional claims, replacement and void claims, and secondary billing. Define how remittance advice posts automatically, how exceptions get queued, and how a biller works a denial without leaving the screen. Lead clearinghouse and payer integrations, including eligibility verification, claim status, and rejection handling, and hold vendors to their file specifications. Translate state Medicaid and Medicare billing rules into product logic, covering service authorizations, units, rate tables, modifiers, and payer-specific edits per state. Build the claim scrubbing rules so errors get caught before submission rather than after a rejection. Partner with the iddbilling.ai team to decide where automation genuinely reduces manual work, and where it should not be trusted yet. Run discovery with billing staff at provider organizations, then turn what you hear into a prioritized backlog with measurable outcomes. Report on clean claim rate, days in accounts receivable, denial rate, and rework volume, and own the trend line on each. Requirements What You Bring Five or more years owning a revenue cycle, medical billing, or claims product, or running revenue cycle operations with at least two years shaping the software behind it. Hands-on United States claims experience, including professional and institutional claim formats, remittance files, eligibility checks, and claim status transactions. Working knowledge of Medicaid and Medicare billing, including waiver and state plan services, rate structures, units, prior authorization, and timely filing limits. Clearinghouse integration experience, meaning you have built, launched, or managed the connection and handled the file failures that follow. The ability to read a payer companion guide or state billing manual and turn it into acceptance criteria an engineer can build from. Real product discipline, including user stories, acceptance criteria, sprint work with engineers and QA, and release notes written for a non-technical audience. Comfort troubleshooting EDI files and interpreting denial and remark codes without…