Data Integration Engineer

Oxbridge Health

About The Position

The Data Integration Engineer for Healthcare Transactions is a hands-on individual contributor on the engineering team, responsible for designing, building, testing, deploying, and operating production data pipelines and integrations that move healthcare data—including claims, enrollment, and other transactions—into and out of the organization’s systems. The engineer writes the code, mappings, and tests for each feed and owns its reliability after deployment. The role covers end-to-end partner connections, from reviewing file specifications and agreeing on requirements through building and testing feeds, running partner test cycles, and moving integrations into production. The engineer works with clients, vendors, Product, account management, and operations, and helps shape the product and engineering roadmap by surfacing integration pain points and edge cases. The role also emphasizes secure handling of healthcare data, reliable operations, reusable integration components, and clear technical documentation.

Requirements

Bachelor’s degree in Computer Science, Information Systems, Healthcare Informatics, or a related field, or equivalent practical experience.
At least 3 years of hands-on software or data engineering experience building and supporting production data integrations; healthcare-sector experience is preferred, and payer or health plan experience is a plus.
Strong proficiency in Python and SQL.
Working knowledge of healthcare transaction standards, especially X12 837 and 834.
Experience building data pipelines on AWS, such as S3 and Lambda.
Experience with RESTful APIs, JSON, and SFTP-based file exchange.
Experience with Git, automated testing, and CI/CD pipelines.
Understanding of HIPAA requirements for handling protected health information.
Strong debugging and problem-solving skills.
Clear written and verbal communication skills, including communication with external technical contacts.

Nice To Haves

Healthcare-sector experience building and supporting production data integrations.
Payer or health plan experience.
Experience with healthcare transaction standards such as 835, 270/271, HL7, or FHIR.
Experience with an integration engine or orchestration tool such as Mirth Connect, Rhapsody, InterSystems, or Airflow.

Responsibilities

Design, build, test, and deploy inbound and outbound data pipelines with providers, payers, vendors, and network partners, including feeds for claims and billing, provider directories, NPPES, ICD-10, and other data sources.
Write parsing, mapping, and transformation logic in Python and SQL to validate, normalize, and load partner data into internal data models.
Build and maintain APIs and services that move integrated data into billing and other core systems.
Create automated data quality checks, validation rules, and exception handling to catch bad or incomplete files before they reach downstream systems or clients.
Instrument pipelines with logging, monitoring, and alerting; investigate production failures, perform root cause analysis, and implement fixes to prevent recurring issues.
Build reusable components and templates to make new feeds faster to establish.
Optimize pipelines for performance and cost as data volumes and partner numbers grow.
Apply HIPAA and security requirements in code and infrastructure, including encryption, secure file transfer, access controls, and audit logging.
Own technical delivery of new client and partner connections, including reviewing file specifications, building and testing feeds, coordinating partner test cycles, and moving feeds into production.
Work directly with technical contacts at clients and vendors to troubleshoot data issues and agree on file layouts and requirements, such as custom 837 claims and 834 enrollment files.
Work with Product, account management, and operations teams to translate business requirements into technical designs with clear acceptance criteria.
Surface integration pain points and edge cases to inform the product and engineering roadmap.
Follow software development practices including version control, code review, automated testing, and CI/CD deployments.
Write and maintain technical specifications, mapping documents, and runbooks so other engineers can support and extend integrations.