Data Architect
US$140,000 – US$160,000 / yr base salary
Posted 24 Jul 2026
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 7+ yrs
- Management level
- Individual contributor
- Employment
- Remote
- Visa sponsorship
- Not offered
| Base salary | US$140,000 – US$160,000 / yr |
|---|
Field of studyComputer Science, Data Engineering, Information Systems (or related)
Study levelBachelor's
Our vision is a world of peaceful relationships with food, weight, and body image, where everyone with an eating disorder can experience recovery. We believe that exceptional, individualized care leads to lasting recovery from eating disorders. That’s why our teams are comprised of compassionate, dedicated professionals from a variety of backgrounds who collaborate to provide the very best evidence-based care for our clients at all levels of care.
Position Summary:
The Data Architect defines and governs the enterprise data architecture for a modern Azure-based platform integrating Avatar NX, Salesforce, and financial systems. This role establishes a scalable, consistent, and governed data ecosystem aligned with business and regulatory requirements. A critical responsibility is reverse engineering the Avatar NX EHR data model, due to limited vendor documentation, to enable accurate integration, reporting, and long-term data governance.
Schedule
- 8am-5pm CST
Salary Range:
$140,000- $160,000 commensurate with experience
Location: Remote- Must be US based, and able to work with no restrictions in the US in a remote home office.
Visa / work permit sponsorship is not available for this position
How Data Architects Empower Recovery:
Enterprise Data Architecture
-
Design end-to-end Azure data architecture (ingestion, staging, curated, reporting layers)
-
Define enterprise data domains (Clinical, RCM, CRM, Finance)
-
Establish canonical data models (e.g., Patient, Encounter, Claim, Revenue)
-
Reverse engineer and document the Avatar NX data model, including:
-
Table structures, relationships, and data flows
-
Enterprise ERDs and logical models
-
Mapping vendor-specific schemas to normalized structures
-
Interpreting and modeling data from a non-traditional database architecture (InterSystems Caché/IRIS), where the SQL layer represents an abstraction over a non-relational core, resulting in limited schema transparency, minimal documentation, and increased complexity in reverse engineering
Integration Strategy
-
Define integration patterns across: