> Markdown version of [/jobs/ext/4349057-architecture-lead-epic-product](https://www.wearedevelopers.com/jobs/ext/4349057-architecture-lead-epic-product). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Architecture Lead, Epic Product

- **Company:** Ensemble Health Partners
- **Location:** Austin, TX, United States (Remote available)
- **Experience:** Expert
- **Salary:** $148,800.0 - $223,200.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Application Integration Architecture, Data Integration, Data Structures, Systems Integration, Web Services, Workflow Management Systems, Data Strategy, Epic Hospital Billing
- **Published:** October 22, 2026
- **Apply:** https://ensemblehp.wd5.myworkdayjobs.com/EnsembleHealthPartnersCareers/job/Austin-TX/Architecture-Lead--Epic-Product_R053507

## About the Role

* 10+ years of Epic experience working in a technical capacity, spanning build, integration, and workflow design.
 * Epic certification in Cadence, Hospital Billing, or Professional Billing.
 * Deep working knowledge of Epic data structures and integration methods - interfaces, APIs, web services, and third-party system connectivity.
 * Demonstrated range across Epic applications beyond your certified area, and comfort operating where the answer is not documented.
 * A startup mentality: energized by ambiguity, fast cycles, and learning new topics outside core Epic scope.
 * Strong communication across technical and operational audiences - engineers, AI teams, operators, and executives.
 * Must be inquisitive and demonstrate openness to innovation including AI to explore better processes and ways to alleviate friction and improve patient and client experiences.
 * This is a remote position; however, candidates must be willing and able to travel to and work onsite at client, temporary, or corporate office locations as business needs require.
 * This position pays between $148,800-223,200 based on experience

Preferred

 * Experience in product management, solution design, or operational strategy.
 * Revenue cycle operations experience across patient access, billing, or HIM.
 * Experience connecting AI or automation solutions to Epic in a production environment., This posting addresses state specific requirements to provide pay transparency. Compensation decisions consider many job-related factors, including but not limited to geographic location; knowledge; skills; relevant experience; education; licensure; internal equity; time in position. A candidate entry rate of pay does not typically fall at the minimum or maximum of the role's range.

## Description

The Epic Architecture Lead is Orchestration Works' Epic authority. Everything OW builds has to work with Epic - and this role owns how. From concept validation through production readiness, the Epic Architecture Lead defines the Epic connection strategy for every initiative in the portfolio: what data moves, how it moves, which interfaces and API connections carry it, and what it takes for an OW solution to operate inside real Epic workflows.

The mandate is intentionally broader than any single Epic application. This role covers Epic overall, advises pods on Epic workflows during validation, and figures out what is needed when the answer

is not documented anywhere. The Epic Architecture Lead works daily with engineering, Applied AI, and Concept Engineering teams, and goes beyond core Epic scope whenever that is what it takes to get an initiative across the gate. This is an individual contributor role reporting to Epic Services but with dedication to Orchestration Works.

What You'll Own

 * Epic integration architecture: Define and own the Epic connection approach for every OW build - data integration, interfaces, APIs, and web services - from concept validation through production readiness.
 * Data strategy: Determine what Epic data each initiative needs, how it is accessed, and how it stays accurate and reliable as solutions move from shadow validation into production.
 * Epic workflow advisory: Advise pods on Epic workflows across applications throughout the 120-day cycle, so solutions are designed around how Epic actually works - not around assumptions about it.
 * Sandbox testing and trialing: Own how OW uses Ensemble's Epic sandbox environment as part of the build cycle - standing up test scenarios, trialing integration patterns and workflows, and proving solutions against realistic Epic conditions before anything moves toward production.
 * Cross-functional build partnership: Work hands-on with engineers, AI practitioners, and concept teams every day, translating between Epic architecture and the systems being built on top of it.
 * The unmapped problems: When an initiative needs an Epic connection pattern, data path, or answer that does not exist yet, this role finds it, tests it, or builds the case for creating it.
 * Standards and handoff: Ensure the Epic integration patterns OW proves out are documented and repeatable, so solutions transition cleanly to Core and to Epic Services at production readiness.
 * Interface to Epic Services: Keep OW's Epic work aligned with Ensemble's Epic standards, Standard Operating Models, and upgrade roadmap without duplicating them.