Platform Engineer, Data Services at Vytalize Health
KS
—
Jul 20, 2026
KS
Jul 22, 2026
What this job asks for AI summary
A senior-to-staff platform engineering role focused on building and operating a clinical decision support platform centered on CDS Hooks and REST APIs, integrating with EMR systems such as Epic, NextGen, and Athena. The work spans API contract design, real-time data pipelines, healthcare interoperability standards (FHIR, SMART on FHIR, HL7), security and compliance, and reliability engineering — suited to someone with deep healthcare data integration experience.
Senior level · 8+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 1,200 people nationally plausibly meet what this posting asks for (software developers). range 350–1,750
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (10)
No work location or remote policy is stated in the posting. The role is assumed to be US-based; remote flag is set to true as no office location is specified and the company (Vytalize Health) is a distributed healthcare technology firm.
The title 'Platform Engineer on Data Services' carries no seniority level word; advertised seniority is Unspecified. However, the required qualifications (8+ years, senior/staff IC scope, end-to-end system ownership) firmly support a Senior classification.
The role sits at the intersection of API platform engineering and healthcare interoperability. 15-1252 (Software Developers) was chosen as the primary SOC because the role's core work is designing and building software systems (CDS Hooks platform, REST APIs, data pipelines). 15-1299 is noted as an alternative given the strong healthcare-interoperability/standards focus that doesn't map cleanly to a single standard SOC.
AWS and GCP are listed together as cloud platform options ('AWS, Databricks, GCP'); Databricks is listed separately as a distinct platform and is emitted as its own skill. AWS is emitted as the primary with GCP as an alternative.
Docker and Kubernetes are listed together as containerization options ('Docker, Kubernetes, or managed services'); both are emitted as separate skills since they are distinct technologies commonly used together, not true substitutes.
Epic, NextGen, Athena, and ECW appear under 'Strong Pluses' (the preferred section), so EMR system experience is marked preferred. Epic is the primary with the others as alternatives since they are interchangeable EMR platforms for this requirement.
Healthcare data formats (FHIR resources, CCD/C-CDA, claims data 837s/835s, HL7 v2/v3) appear in both required and preferred sections. FHIR and HL7 are marked required (explicitly gated in Required Qualifications); CCD/C-CDA and claims formats appear only under Strong Pluses and are marked preferred.
OIDC and SAML appear only under 'Strong Pluses' and are marked preferred. OAuth 2.0 is explicitly required in the Required Qualifications section.
CI/CD, HEDIS, and HCC/RAF appear only under 'Strong Pluses' and are marked preferred.
No compensation range is provided in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.