Senior Data Engineer

Senior Data Engineer — EHR Integrations

📍 Remote (Latin America-based; English-fluent)

Feel free to apply via this link for a quicker response: https://tricurainsurance.io/careers/senior-data-engineer-ehr-integrations

About the Company:

Tricura Insurance Group is a next-generation, tech-enabled insurance and risk management company transforming how healthcare organizations protect, manage, and grow their operations.

We're a global, remote-first team with headquarters in New York, reshaping the future of healthcare insurance. By combining deep industry expertise with modern technology, we deliver smarter, faster, and more transparent insurance solutions across the continuum of care.

If you're motivated by impact, innovation, and purpose, you'll find your place here.

About the Role:

We're looking for a Senior Data Engineer to own the integration layer between Tricura's platform and Electronic Health Record (EHR) systems.

Our software transforms clinical data from long-term care and senior living providers into real-time alerts, compliance checks, and analytics. As our customer base grows, so does the number of EHR systems we need to support.

Your mission is to make our platform genuinely EHR-agnostic—building the architecture that allows new EHR systems to be integrated through a common abstraction layer instead of vendor-specific implementations.

Every EHR exposes clinical data differently. Some provide REST APIs, others rely on webhooks, SOAP services, flat-file exports, or database replication. You'll design the canonical data model and integration architecture that hides those differences, allowing the rest of the platform to work with standardized clinical entities regardless of where the data originated.

This is a high-ownership engineering role. You'll own the integration platform end-to-end—from completing existing integration work to defining the long-term architecture for scalable onboarding of new healthcare systems and preparing the platform for standards-based interoperability through HL7 and FHIR.

What You'll Do:

• Design the canonical clinical data model and translation layer that normalizes data from diverse EHR systems into consistent clinical entities. Your goal is to make future integrations primarily a configuration and mapping exercise rather than custom engineering work.
• Own Electronic Health Record (EHR) integrations end-to-end—from vendor API discovery and authentication to rate limits, webhooks vs. batch export tradeoffs, backfill strategy, incremental sync, and production monitoring.
• Build and operate ingestion pipelines using a modern data stack, including workflow orchestration, a cloud data warehouse, SQL-based transformation tooling, and AWS infrastructure.
• Prepare the platform for HL7 and FHIR by defining a pragmatic strategy for adopting standards-based interoperability as regulatory requirements evolve.
• Own data quality at the integration boundary, including schema-drift detection, freshness SLAs, reconciliation between source systems and our platform, and customer onboarding runbooks.
• Investigate and design around imperfect vendor systems. Many integrations won't behave exactly as documented—you'll build resilient solutions that account for real-world API limitations and inconsistencies.
• Own the long-term health of production integrations, including ongoing maintenance, troubleshooting, adapting to vendor changes, and ensuring reliable operation as new customers are onboarded.

Who We're Looking For:

• 5+ years of experience in data engineering or backend engineering with a strong data focus, including production ownership of third-party integrations.
• Experience integrating multiple external vendor systems through APIs, webhooks, flat-file exchanges, database replication, or similar automated data interfaces.
• Strong Python and SQL skills, with experience using workflow orchestrators (e.g., Airflow) and modern cloud data warehouses with dbt or similar transformation tooling.
• Experience designing event-driven integrations, including webhooks, queues, idempotency, dead-letter handling, and making tradeoffs between streaming and batch processing.
• Experience building production systems on AWS, including enough infrastructure knowledge to make architecture and deployment decisions independently while collaborating with DevOps when needed.
• Strong architectural judgment—you can design a metadata-driven mapping layer without over-engineering it, and you know when a vendor's API won't realistically support the required workload.
• Highly proactive, ownership-oriented, and comfortable operating in ambiguity.
• Adaptable, collaborative, and startup-ready.
• Fluent English. Comfortable working directly with external US-based vendors, navigating technical documentation, and communicating effectively.
• Based in a Latin American country.
• Available to work full-time from 9 am to 6 pm EST and more.

Strong Plus:

• Hands-on experience integrating with El