The Opportunity:
Revenue Cycle Innovation Operators are the permanent operational voice inside Orchestration Works. Operators serve as subject matter experts in specific revenue cycle domains while understanding the broader end-to-end revenue cycle. They redesign workflows, identify upstream root causes, build knowledge graphs, participate in design sessions, and validate emerging automation and AI-driven models — working shoulder to shoulder with product, engineering, and AI teammates as full members of the team, not advisors.
This is a role for operators who want to change how the work is done, not just do it faster. Every initiative starts by challenging why the work is done the way it is; Operators bring the domain judgment that makes that challenge credible and the redesign real.
Core Responsibilities
- Act as the domain SME while maintaining literacy across the full revenue cycle.
- Identify structural root causes that drive downstream rework, friction, and leakage.
- Design future-state workflows and operating models with measurable impact.
- Build and maintain domain-specific knowledge graphs capturing inputs, rules, actions, and outcomes.
- Participate in design sessions and rapid innovation sprints with product, engineering, and analytics teams.
- Test and validate automation, ML, AI, and agentic models using real operational scenarios.
- Translate SME judgment into rules, decision trees, training data, and guardrails.
- Support pilots and controlled rollouts with clear success criteria and measurement.
- Document operational logic and findings for reuse and scale.
Domain Focus Areas
Each Operator is hired into one of the five domains below. Candidates should indicate their domain of expertise when applying.
Back End — (AR follow-up, denials, billing, posting)
- Identify structural AR drivers, payer behavior patterns, and true root causes of denials — separating provider errors from payer behavior.
- Design prioritization models that optimize for yield and resolution speed; build knowledge graphs mapping payer actions, responses, and optimal operator strategies.
- Design more actionable denial taxonomies and prevention models; build predictive models linking denial risk to upstream process failures; test AI-assisted appeal generation.
- Analyze systemic causes of claim edits, rejections, posting errors, and reconciliation lag; design workflows and automated logic that raise clean claim rates and posting accuracy.
What You Bring
- 5+ years of hands-on experience in the revenue cycle, with depth in your domain.
- Strong end-to-end revenue cycle literacy.
- Exceptional process mapping and improvement capability.
- Data-driven problem solving and comfort with variance analysis.
- Ability to operate effectively in ambiguity; self-motivated and proactive.
- Strong communication skills for both technical and non-technical audiences.
- Curiosity and aptitude for automation, ML, AI, and agentic technologies.
- Ability to multi-task and maintain quality under changing priorities.
How We Work at Orchestration Works
- 120 days, three gates: Every initiative moves from intake to deployment-ready in 120 days or less, through three decision gates. Killing a concept at the gate is a legitimate, expected outcome — that is the model working, not breaking.
- Multi-hat, startup-like team: Roles here are broader than their titles. Leaders operate hands-on, pods rotate in and out on initiative cycles, and everyone contributes beyond their lane.
- Validated on real work: Front-line Ensemble teammates use what we build on real workflow before anything is locked. Solutions are designed around validated work, not assumption.
- Built on Core: Same codebase, same CI/CD, same Ensemble engineering bar. OW proves it; Core scales it.
- Co-located in Austin: The dedicated team and active pod members work together in person at the OW office. Candidates must currently reside in the Austin area or be willing to relocate; relocation assistance may be available for eligible candidates.
