Senior Manager, Revenue Cycle Operations

Role

This 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.

Responsibilities

• Own day-to-day outcomes for the managed RCM client book: claim submission, rejections, denials, AR follow-up, payment posting, payer coordination, and payer/ERA enrollment
• Act as the senior operational counterpart for customer practices — implementation and go-live, monthly performance reviews, recommendations, and escalation resolution
• Build the operating system: onboarding checklists, SOPs, quality assurance, KPI definitions, and a clear swim-lane model of what Oasys owns versus what the practice owns
• Partner directly with Product and Engineering to convert recurring billing failures into workflow and platform improvements
• Own and report on a core scorecard: implementation time, clean-claim and first-pass rate, touchless claim rate, denial rate, days in AR, aging AR, net collections versus expectation, SLA performance, and customer retention
• Identify and escalate provider-side blockers — credentialing gaps, missing demographics, unresponsive follow-up — before they silt up the claims queue
• Hire, train, and manage early RCM operators and external billing partners as the service grows

Requirements

• 5–10+ years of end-to-end revenue cycle experience: eligibility and authorizations through claims, denials, AR, payments, and payer coordination
• Deep behavioral health billing knowledge — therapy CPT structure and add-on codes, E&M and med management, supervision billing and modifier logic, Medicaid HCPCS and per-unit calculation rules, and payer-specific quirks
• A track record of measurably improving billing outcomes, with numbers you can point to and explain
• Credibility with practice owners and clinicians; comfort running a performance review call directly with a customer
• Experience partnering closely with Product and Engineering to scale workflows — not just filing bug reports
• A process-builder instinct: when handed a broken workflow, you ask why it exists at all rather than who owns the checklist
• Preferred: time at a tech-first behavioral health provider, MSO, or platform (Rula, Headway, Grow Therapy, Ensora Health, TherapyNotes, or similar)
• Preferred: background in specialist RCM or billing service firms, or adjacent complex outpatient settings such as ABA or PT/OT (CentralReach, Prompt, and the like)
• Preferred: you've built an SOP or QA process from a blank page and watched it survive contact with reality

About

Oasys is the AI-native EHR and practice management platform for group behavioral health practices. We combine clinical documentation, billing and revenue cycle, and an outcomes layer into a single system of record — so a practice runs on one platform instead of stitching together three.

We're a small team in New York City supporting live practices and hundreds of therapists, growing quickly. Our thesis is that behavioral health has been served by software built for other specialties, and that the practices doing the hardest clinical work deserve infrastructure that actually understands how they get paid.

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.