RCM Architect

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.

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 are the person who defines what correct RCM looks like — and ensures the organization is executing toward it.
• 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

What You’ll Do

• You are the connective tissue between Joyful's RCM expertise and every team that depends on it.
• On any given day, you might be deep in a customer's denial data identifying the root cause of a revenue leakage pattern, sitting alongside Engineering to validate whether a new agent workflow reflects how billing actually works, or building the SOP that a BPO team will use to execute against a new specialty.
• This is not a role defined by a single function. You are embedded across Sales, Customer Success, Product, and Operations — not as a support resource, but as the person who sets the standard for what correct RCM looks like and ensures the organization is executing toward it.
• You own the outcome, not just the deliverable.

How You’ll Be Measured

• Primary metric: Reduction in upheld denials and rejections — the clearest signal that actions taken are correct and effective.
• Resolution effectiveness rate
• Reduction in rework and incorrect actions
• Time to resolution
• Adherence to the historical backlog burndown rate — how successful was the strategic approach?
• Product feedback tied to measurable outcomes — not just written feedback, but whether what you influenced actually improved results
• Degree to which you can operate independently without Head of RCM review — a key signal that the function is scaling as intended

What Success Looks Like

• In 30–60 Days
• Deep familiarity with Joyful’s workflows, product, customer base, and internal team structure
• Producing clear, well-structured onboarding analyses for new customers with actionable recommendations
• Contributing meaningfully to product conversations — opinions are grounded in real-world RCM, communicated with confidence
• First SOPs and workflow definitions drafted and in review

• In 90 Days
• Independently owning the onboarding support function for new customers without Head of RCM review
• Actively identifying systemic denial patterns across the customer base and translating them into product improvements and SOPs
• Recognized by Product and Engineering as a trusted RCM authority — your feedback is shaping what gets built
• Sales team is relying on your pre-sales analysis to close and scope deals with confidence

• In 6–12 Months
• The organization has a compounding, structured body of RCM knowledge — SOPs, enablement guides, denial frameworks — that scales beyond any single person
• Measurable reduction in upheld denials across the customer base attributable to workflow and strategy changes you led
• The CoE is emerging as a recognized center of expertise — the function other teams go to when things are hard

Why This Role Matters

• Most organizations treat RCM as a series of disconnected tasks. We treat RCM as a system that can be understood, structured, and improved.
• The RCM Architect is the role that makes that possible. When you define a workflow, audit a decision, or translate a denial pattern into a product requirement, you are building something that compounds.
• Every system you design, every piece of knowledge you codify, every SOP you write — it doesn’t just help one claim or one customer. It improves how the entire organization operates.