Senior Manager, Revenue Cycle Operations

RoleThis is our first dedicated revenue cycle hire, and it's a build role before it's a management role. Oasys offers Managed RCM as a service on top of our platform: we submit claims, work rejections and denials, post payments, and handle EDI/ERA enrollment on behalf of our customers. It's a real service with real customers, and it's growing fast enough that it now deserves a dedicated owner. You'll be that owner - accountable not just for day-to-day outcomes, but for the operating system underneath them: SOPs, escalation paths, the division-of-responsibility model we give customers, the KPIs we hold ourselves to, and the feedback loop into the product itself. That last part is why this job is different from a billing operations seat at an RCM firm. When you find a denial pattern here, the answer usually isn't a new checklist for a human to follow. It's a change to how the platform validates data before a note gets signed, or a rule that prevents a bad code combination from ever reaching the clearinghouse. You'll sit next to engineering and turn recurring billing failures into product. Our north-star metric is touchless claim rate - the share of claims that go out, adjudicate, and post with zero human intervention - and your job is to drive it up while the book of business grows underneath you. You'll own a scorecard including time-to-first-clean-claim, clean claim and first-pass resolution rate, touchless claim rate, denial rate and resolution time, days in AR, aging AR, net collections versus expectation, SLA performance, and retention on managed accounts. You'll have real latitude to define how we measure and where we set the bar. A note on what this role is not. It is not a claims-processing or payment-posting seat - that work is largely automated here, and where it isn't, our goal is to automate it. It is not a role where you inherit someone else's playbook; you'll write your own. And it is not a role insulated from customers. You'll be on calls with practice owners regularly. This starts as an individual contributor role with a clear path to leading the function as the book grows.

Applying Our process: an intro call, a deep-dive conversation on your revenue cycle experience, a short practical exercise built around a real (anonymized) billing workflow problem, and conversations with the founders and engineering. Send your resume along with a few sentences on a billing process you rebuilt - what was broken, what you changed, and what it did to the numbers. We read those closely.