You will work closely with architects and engineering teams to design and deliver high-scale, reliable platform systems.
Drive integration with interoperability platforms (e.g., Redox, Mirth) and with EHR, practice management, and clearinghouse systems
Partner with RCM operations, coding, and finance stakeholders to turn revenue cycle pain points into platform requirements
From the employer’s posting
AI-ready data pipelines powering recommendations, patient insights, and revenue cycle intelligence
This is a highly technical, execution-focused role. You will work closely with architects and engineering teams to design and deliver high-scale, reliable platform systems.
What You'll Own
Define and deliver scalable ingestion pipelines for clinical and administrative data: HL7 v2, X12 EDI transactions (837, 835, 270/271, 276/277, 278), claims and remittance feeds, flat files, and FHIR R4 APIs where applicable
Drive integration with interoperability platforms (e.g., Redox, Mirth) and with EHR, practice management, and clearinghouse systems
Ensure high data quality, schema validation, and fault-tolerant ingestion
Enable data foundations for AI use cases such as denial prediction and prevention, coding and documentation gap detection, under-payment identification, and prior authorization automation
Partner with RCM operations, coding, and finance stakeholders to turn revenue cycle pain points into platform requirements
Data Normalization & Canonical Data Model
Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.
Applying through Greenhouse
No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.
New Data Engineer postings at the employers we follow are up 7% over the last 6 weeks compared with the 6 before.
August 17Last week
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
About the role
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
US government figures for database architects
Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
We are building a scalable, AI-first healthcare data platform that turns raw clinical and financial data into actionable intelligence.
As a Technical Product Manager, you will drive the development of core platform capabilities spanning:
Healthcare data ingestion and interoperability across clinical and revenue cycle sources
Data normalization and canonical modeling that connects clinical, claims, and financial data
Temporal data processing and workflow orchestration
AI-ready data pipelines powering recommendations, patient insights, and revenue cycle intelligence
This is a highly technical, execution-focused role. You will work closely with architects and engineering teams to design and deliver high-scale, reliable platform systems.
What You'll Own
Healthcare Data Ingestion & Interoperability
Define and deliver scalable ingestion pipelines for clinical and administrative data: HL7 v2, X12 EDI transactions (837, 835, 270/271, 276/277, 278), claims and remittance feeds, flat files, and FHIR R4 APIs where applicable
Drive integration with interoperability platforms (e.g., Redox, Mirth) and with EHR, practice management, and clearinghouse systems
Ensure high data quality, schema validation, and fault-tolerant ingestion
Revenue Cycle Data & Intelligence
Own the platform capabilities that support RCM workflows across patient access, mid-cycle, and back end: eligibility and benefits, prior authorization, charge capture, coding, claims submission, denials, and payment posting
Link clinical documentation and encounters to charges, claims, and remittances to create a complete view from encounter to payment
Enable data foundations for AI use cases such as denial prediction and prevention, coding and documentation gap detection, under-payment identification, and prior authorization automation
Partner with RCM operations, coding, and finance stakeholders to turn revenue cycle pain points into platform requirements
Data Normalization & Canonical Data Model
Own the design and evolution of a canonical data model across clinical domains (encounters, medications, labs, notes) and financial domains (charges, claims, remittances, payers, contracts)
Define mapping frameworks for clinical and billing terminologies and coding systems (ICD-10-CM/PCS, CPT, HCPCS, DRG, CARC/RARC, SNOMED, LOINC, RxNorm)
Ensure consistent representation of structured and semi-structured data, aligned with industry standards (including FHIR resources where appropriate)
Data Processing & Workflow Orchestration
Define systems for event-driven and batch data processing pipelines
Drive temporal alignment of clinical and financial events to support longitudinal patient views and claim lifecycle tracking
Partner with engineering to implement scalable workflows using orchestration frameworks (e.g., Temporal)
Platform APIs & Data Services
Define APIs for:
Data ingestion and transformation
Access to normalized patient, encounter, and claims data
Downstream consumption for analytics, RCM applications, and AI use cases
Ensure high performance, scalability, and reliability of platform services
AI-Ready Data Foundation
Enable data pipelines that support:
Clinical decision support
Patient summaries
Recommendation systems
Revenue cycle automation and financial insights
Collaborate with AI/ML teams to ensure data is structured, contextualized, and usable for model development
Execution, Roadmap & Delivery
Translate platform vision into a clear product backlog (epics, user stories, acceptance criteria)
Prioritize and sequence work across ingestion, processing, RCM data capabilities, and platform services
Drive execution with engineering teams from 0 → 1 → scale
Track success through platform reliability, performance, and downstream clinical and financial impact
Examples of Problem Spaces You'll Tackle
Designing a unified data model that connects fragmented clinical and claims sources
Building high-throughput ingestion systems for real-time and batch clinical, EDI, and remittance data
Creating temporal patient timelines and encounter-to-payment views from multi-source events
Enabling AI-driven insights that reduce denials, improve coding accuracy, and speed up reimbursement
Solving data consistency, mapping, and interoperability challenges at scale
Required Experience
Technical Product Management (Must-Have)
5–8+ years of product management experience in a technical domain
Strong experience building platforms, APIs, or data infrastructure products
Ability to work deeply with engineers on architecture, system design, and trade-offs
Proven track record of delivering scalable systems from concept to production
Revenue Cycle Management (Must-Have)
Hands-on experience building products or data platforms for healthcare RCM (provider, payer, or RCM vendor side)
Solid understanding of the end-to-end revenue cycle: registration and eligibility, prior authorization, charge capture, coding, claims, denials management, and payment posting
Working knowledge of X12 EDI transactions (837, 835, 270/271, 276/277) and clearinghouse workflows
Familiarity with billing code sets and payer concepts (CPT, HCPCS, ICD-10, DRG, CARC/RARC, payer contracts, and fee schedules)
Experience with HL7 v2 messaging and healthcare data exchange
Working knowledge of FHIR R4 resources and APIs, including financial resources such as Claim, Explanation of Benefit, and Coverage (deep FHIR implementation expertise is a plus, not a requirement)
Familiarity with interoperability engines (e.g., Redox, Mirth, Rhapsody)
Understanding of clinical data domains and how clinical documentation drives billing and reimbursement
Data & Platform Expertise
Strong understanding of:
Data modeling and schema design
ETL / ELT pipelines
Batch and streaming architectures
Experience working with PostgreSQL or similar relational databases