Lead Data Engineer, Senior Data Engineer

Virtasant

. Build connectors and pipelines from HR, scheduling, EHR, and external benchmark sources into Snowflake on Azure .

Posted 11/6/2026contractRemote • United StatesSeniorWebsite

Core Competencies

Role fit

Core Competencies

Use this summary to align your resume positioning with the role.

Demonstrates expertise in building and managing data integrations, particularly in sensitive environments, while leading engineering teams and ensuring data quality and compliance with regulations. Proficient in utilizing Azure and Snowflake for scalable data solutions and implementing best practices for data governance.

Highest-signal resume keywords

SQLPythonSnowflakeAzure Infrastructure as CodeData Quality and Lineage

ATS Keywords

Tailor your resume

Applicant Tracking System Keywords

Tip: use these terms in your resume and cover letter to boost ATS matches.

Hard Skills

Data IntegrationData ContractsSchema EvolutionMulti-Tenant Data PlatformsEntity ResolutionGraph Database (Neo4j)Event-Ready Batch PipelinesData QualityLayered Pipelines (dbt)Coding Assistants

Soft Skills

LeadershipProblem-SolvingCollaborationCommunicationIndependence

Tools & Technologies

TerraformBicepAzure StorageEHR SystemsWorkdayUKGEpicCernerMEDITECHOpenLineage

Industry Keywords

PHIPIIHIPAAData GovernanceHealthcare Data

Tech Stack

Tools & technologies

AzureNeo4jPythonSnowflakeSQLTerraform

About the role

Key responsibilities & impact

Build connectors and pipelines from HR, scheduling, EHR, and external benchmark sources into Snowflake on Azure
Map enterprise data into a shared ontology and publish it to a Neo4j graph
Make customer data onboarding repeatable so new customer data can go live in days rather than months
Work with real, sensitive client data
Use AI-assisted development as a normal part of development
Lead: own the technical direction, design, standards, and work sequencing of a pod
Lead: work directly with client architects and data owners to agree source extracts, data contracts, and acceptance criteria
Lead: review engineers’ code and designs and remain accountable for pod deliverables
Senior: own significant components end to end, such as source connectors, mappings, or domain reconciliation
Build production data integrations that handle late files, schema drift, duplicates, and conflicting records
Validate incoming data, quarantine failures, and evolve schemas without breaking downstream systems
Ensure data totals reconcile with source systems, provide record-level lineage, and support idempotent reruns
Implement masking, tokenization, least-privilege access, audit trails, and sensitive-field controls
Build repeatable multi-tenant onboarding based on configuration and mapping rather than separate codebases
Build Azure storage, identity, and infrastructure-as-code components
Potentially travel domestically on occasion

Requirements

What you’ll need

Must be based in the United States
Authorized to work in the United States
Available around December 1, 2026
Experience integrating messy enterprise source systems in production
Strong SQL and Python skills
Hands-on Snowflake experience
Experience building and running layered pipelines using dbt or equivalent
Experience with data contracts and versioned schemas
Experience with data quality, lineage, and reconciliation
Experience working with regulated or sensitive data under PHI/PII controls such as HIPAA
Experience building multi-tenant data platforms with strict per-customer isolation
Azure experience with storage, identity, and infrastructure as code using Terraform or Bicep
Daily use of coding assistants with verification of generated output
Lead level: experience leading a small engineering team, setting technical direction, and working directly with client architects and stakeholders
Senior level: ability to own significant pieces end to end, work independently, raise problems early, and work without day-to-day supervision
Strong plus: healthcare data experience with Workday, UKG, Epic, Cerner, or MEDITECH
Strong plus: graph database experience, ideally Neo4j
Strong plus: ontology or common data model mapping
Strong plus: entity resolution
Strong plus: external benchmark or reference data feeds
Strong plus: event-ready batch pipelines with idempotent loads and incremental refresh
Strong plus: OpenLineage or similar lineage and metadata standards
Strong plus: production data-feed monitoring for freshness, volume, and failure alerts

Benefits

Comp & perks

Multi-month engagement, likely to extend
Fully remote work arrangement
Occasional domestic travel may be required