Pay
$127K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,383 postings in the last year. Stated ranges, not salaries paid.
Norwalk, CT
Live, first seen by us 18 days agoEmployment type in the employer’s posting: SALARIED_FTFrom the employer’s posting
Design, build, test and deploy inbound and outbound partner data pipelines
Write Python and SQL parsing, mapping and validation logic for partner data
Build automated data quality checks and exception handling for bad files
Investigate production failures and ship root-cause fixes
Own technical setup of new client and partner connections through production
Design, build, test, and deploy inbound and outbound data pipelines with providers, payers, vendors, and network partners
Write the parsing, mapping, and transformation logic in Python and SQL that validates, normalizes, and loads partner data into internal data models.
Build automated data quality checks, validation rules, and exception handling so bad or incomplete files are caught before they reach downstream systems or clients.
investigate production failures, perform root cause analysis, and ship fixes that keep issues from recurring
Own the technical side of new client and partner connections end to end
Our company is a start-up that specializes in episodes of care benefit plans. We have a deep expertise in episode pricing and analytics and our goal is to bring transparency and efficiency to the healthcare market. Our company is committed to providing high-quality, affordable healthcare to our customers. Role Description The Data Integration Engineer for Healthcare Transactions is a hands-on software engineer responsible for designing, building, and operating the data pipelines and integrations that move healthcare data, including claims, enrollment, and other transactions, into and out of the organization's systems. This is an individual contributor role on the engineering team: this person writes the code, mappings, and tests behind each feed, deploys it to production, and owns its reliability from there. The ideal candidate is an engineer who knows healthcare data standards in detail and treats integrations as production software. ResponsibilitiesRead the full posting
3+ years of hands-on software or data engineering experience building and supporting production data integrations
Strong proficiency in Python and SQL.
Working knowledge of healthcare transaction standards, especially X12 837 and 834
Experience with RESTful APIs, JSON, and SFTP-based file exchange.
Experience with Git, automated testing, and CI/CD pipelines.
3+ years of hands-on software or data engineering experience building and supporting production data integrations, preferably within the healthcare sector (payer or health plan experience a plus).
Experience with an integration engine or orchestration tool (e.g., Mirth Connect, Rhapsody, InterSystems, Airflow) a plus.
- Describe the experience and attributes of the ideal candidate - Bachelor's degree in Computer Science, Information Systems, Healthcare Informatics, or a related field, or equivalent practical experience. - 3+ years of hands-on software or data engineering experience building and supporting production data integrations, preferably within the healthcare sector (payer or health plan experience a plus).
From the employer’s posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$127K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,383 postings in the last year. Stated ranges, not salaries paid.
Day 18
Similar jobs usually come down between day 6 and day 56.
From 13,985 similar postings that came down. Coming down is not always a hire.
4 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Design, build, test, and deploy inbound and outbound data pipelines with providers, payers, vendors, and network partners, covering Claims and Billing files, Provider Directory files, NPPES, ICD10 and other data sources. - Write the parsing, mapping, and transformation logic in Python and SQL that validates, normalizes, and loads partner data into internal data models. - Build and maintain the APIs and services that move integrated data into billing and other core systems.
- 3+ years of hands-on software or data engineering experience building and supporting production data integrations, preferably within the healthcare sector (payer or health plan experience a plus). - Strong proficiency in Python and SQL. - Working knowledge of healthcare transaction standards, especially X12 837 and 834; experience with 835, 270/271, HL7, or FHIR a plus.
- Working knowledge of healthcare transaction standards, especially X12 837 and 834; experience with 835, 270/271, HL7, or FHIR a plus. - Experience building data pipelines on AWS (e.g., S3, Lambda). - Experience with RESTful APIs, JSON, and SFTP-based file exchange.
- Experience with Git, automated testing, and CI/CD pipelines. - Experience with an integration engine or orchestration tool (e.g., Mirth Connect, Rhapsody, InterSystems, Airflow) a plus. - Understanding of HIPAA requirements for handling protected health information.
Complete your application on ats.rippling.com. The employer’s form will show what is required.
Already applied? Track this application
New Data Engineer postings at the employers we follow are up 7% over the last 6 weeks compared with the 6 before.
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.
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.
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.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Company Overview:
Our company is a start-up that specializes in episodes of care benefit plans. We have a deep expertise in episode pricing and analytics and our goal is to bring transparency and efficiency to the healthcare market. Our company is committed to providing high-quality, affordable healthcare to our customers.
Role Description
The Data Integration Engineer for Healthcare Transactions is a hands-on software engineer responsible for designing, building, and operating the data pipelines and integrations that move healthcare data, including claims, enrollment, and other transactions, into and out of the organization's systems. This is an individual contributor role on the engineering team: this person writes the code, mappings, and tests behind each feed, deploys it to production, and owns its reliability from there. The ideal candidate is an engineer who knows healthcare data standards in detail and treats integrations as production software.
Responsibilities
Qualifications
Benefits
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Norwalk, CT
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.