RCM Architect

Joyful Health

1d•Remote

About The Position

Joyful Health is building an AI-powered financial operating system for healthcare practices. Our mission is to bring the joy back to running a private practice by simplifying financial operations so providers can focus on patient care. We spent 10 months working as fractional CFOs for a dozen practices, doing this work side by side with providers as we developed our product. We just closed a funding round led by world-class investors and angels including the founders of MongoDB & KAYAK. At the center of our model is the RCM Center of Excellence (CoE) — the layer that translates real-world billing complexity into scalable systems. If you’re excited about applying deep RCM expertise to fix a system that is fundamentally broken, we’d love to meet you. The Role We are hiring an RCM Architect to serve as the RCM knowledge layer across the organization. This is a high-leverage, cross-functional role that sits at the intersection of Sales, Customer Success & Operations, and Product & Engineering. You are the person who defines what correct RCM looks like — and ensures the organization is executing toward it. This role is accountable for outcomes, not just artifacts. RCM Architects are not measured by the quality of the document they produce — they are measured by whether the function, project, or account achieves its intended RCM result. You own the outcome. You will be responsible for translating RCM complexity into clear strategy, structured workflows, and actionable insights — ensuring that: We start customers correctly We build the right product We solve the right problems The organization develops a compounding understanding of RCM patterns and solutions

Requirements

8+ years in Revenue Cycle Management with deep expertise in denials, AR follow-up, and payer behavior
Hands-on experience analyzing claims data, denial trends, and revenue performance across multiple payers and specialties
Experience working across functions — you’ve collaborated with Sales, Operations, or Product teams, not just stayed in a billing lane
Experience designing or improving RCM workflows, SOPs, or decision frameworks — not just executing existing ones
A track record of using AI tools, automation, or data to work smarter. We expect every member of the CoE to be actively pushing the boundary of what’s possible with the tooling available to them.

Nice To Haves

A systems thinker — you think about root causes, patterns, and scalable solutions, not just the next action on a claim
Outcome-oriented — you care whether the thing you built actually worked, not just that you delivered it. You track results.
Comfortable being the person people go to when things are unclear — when root cause is murky, when the payer is behaving oddly, when the product doesn’t know what to do — you’re the one with a structured answer
Analytical and data-driven — you can go from raw data to insight to strategy to execution, and you do it naturally
Low ego, high ownership — collaborative and coachable, but you take accountability for outcomes. You don’t point to the artifact and consider the job done.
Product-minded — you think in systems and scalability. You see features not just as features but as encoded workflow logic — and you know when the logic is wrong.
A clear communicator across audiences — you can write a PRD comment that an engineer can act on, a briefing that an AE can deliver in a sales call, and an SOP that a biller can follow. These are different things, and you know the difference.
Comfortable with ambiguity and confident making calls — you don’t default to “maybe” when you mean “no.” You make a judgment, document your reasoning, and move forward.
Open to your role evolving — the RCM Architect role will begin as a generalist function and is expected to evolve toward specialization over time. You’re excited about shaping what that looks like, not threatened by it.

Responsibilities

Audit claims and drive strategy — Review claims for accuracy of action taken, validate next-best-action decisions, and translate findings into systemic recommendations. You're not fixing one claim; you're identifying the pattern behind it.
Turn denial data into actionable workflows — Translate denial patterns into root causes and resolution pathways. Define standardized recovery strategies, escalation logic, and decision frameworks that hold up against real-world payer behavior.
Codify RCM knowledge at scale — Build and maintain the SOPs, specialty guides, and decision frameworks that allow the organization to execute at a high RCM standard without you in every room. You are building a system, not just answering questions.
Set every new customer up for success — Analyze denial rates, aging, payer mix, and workflow gaps at onboarding. Deliver a data-backed strategic action plan to the RCSM so every account starts with a clear path forward.
Enable the organization — Support new hire onboarding, partner with Product and Engineering on feature release training, and communicate industry changes with a clear summary of what they mean for each team.
Shape what gets built — Serve as the embedded RCM SME throughout the product development process. Contribute to PRDs, surface edge cases before build, and hold yourself accountable for the RCM quality of what ships — not just the feedback you submitted.
Power the sales motion — Provide pre-sales RCM analysis for deals within ICP, create specialty-specific enablement materials for AEs, and review outbound copy for accuracy and appropriate framing.
Be the expert in the room on escalations — Partner with RCSMs on complex customer challenges, step in when root cause is unclear, and feed systemic insights back into the product roadmap and operational workflows.