About this role
About the Company Verto Health is a health technology company solving some of healthcare’s most complex data fragmentation and interoperability challenges. Our patented, AI-enabled platform brings together structured and unstructured clinical data across disparate EHRs, claims, and payer systems to create a unified, actionable view of patient populations. We work with health systems and value-based care organizations across North America to turn fragmented healthcare data into personalized patient journeys, automated workflows, and more accurate risk adjustment. By connecting data to action, Verto helps healthcare providers reduce manual work, improve operational efficiency, and deliver more proactive, data-driven care at scale. •   About the Role As Principal Software Engineer, Health Data & Interoperability, you will be the senior technical voice on our engineering team and the owner of the data architecture underneath the product. You’ll set the bar for what good code looks like, build the AI-assisted development pipeline the team works through, and own the canonical model and the pipelines that feed it. This is a hands-on role. You'll write code, review everyone else's, and design the ingestion and transformation that turns fragmented and inconsistent healthcare data across HL7 v2, FHIR, claims, and third-party sources into something the product can depend on. Reporting into the CIO, you'll largely interface with four teams. The engineering team owns application architecture and software development, and will operate the pipelines you design. The AI engineering team owns AI system design and evaluation, and will depend on you for reliable modelled inputs. The product and delivery team owns the roadmap. The implementations team owns client projects and integration delivery. What You'll Do Engineering Leadership & R&D Set and hold the code review bar, and raise the standard of what ships rather than only reviewing what arrives. Build and drive our AI-assisted development pipeline, from the agentic harnesses themselves through to daily use of frontier coding tools across the team. Own technical R&D and spikes: evaluate what is worth adopting, prove it, and bring back something the team can use. Hold the line on technical debt and resilience, including retiring legacy code and fixing projects that only one person understands. Data Architecture Own the canonical healthcare data model covering patients, encounters, providers, claims, and clinical events, fit for longitudinal records, cross-source analytics, and EMPI. Own the semantic terminology service, the platform APIs applications consume, and the datasets the application and analytics layers depend on. Set the standards for data quality, lineage, and standardization, and build provenance in outputs informing a clinical or financial decision can be traced to source. Own decision rights on the data model and data standards, and make the data-side calls in the Architecture Review Board. Interoperability & Data Pipelines Design the ingestion and ETL that brings HL7 v2, FHIR, claims, and third-party data into the platform, and keep it working as sources change. Work with federated query engines such as Trino and with ingestion patterns that span many source systems. Optimize pipelines for throughput, cost, reliability, and latency, and own root cause when a feed breaks. Build for operability so the engineering team can run what you design without you in the loop. Keep ingestion patterns reusable across clients rather than rebuilding them for each client. •   What You Bring Knowledge & Experience Bachelor's degree in Computer Science, Engineering, Health Informatics, or a related field, or equivalent experience. • 7+ years in software and data engineering, including 4+ yea