Director of Data Platform & Engineering
Fully Remote • Columbus, OH
Description

 

Director of Data Platform & Engineering


About Us

At Gifthealth, we're revolutionizing the way people experience healthcare by simplifying the process of managing prescriptions and health services. Our mission is to provide a seamless, personalized, and efficient healthcare experience for all our customers. We're a dynamic, innovative, and customer-centric company dedicated to making a positive impact on people's lives.


Position Summary

We are seeking a Director of Data Platform & Engineering to own everything upstream of the business: the ingestion, warehouse, orchestration, and data infrastructure that every report, partner data feed, and agentic AI product at Gifthealth depends on. This position plays a key role in supporting the Data Platform & Engineering team (not labeled as a formal department in the source job description) and reports to the CTO, ensuring alignment with organizational goals, operational excellence, and compliance standards.

Peers in this role include the Director of Data & Analytics, Director of Engineering, Director of IT, and Director of IT Security. The team today is a small, senior data engineering group with a platform mandate and room to grow, covering ingestion, warehouse, orchestration, data infrastructure, and the staging and intermediate dbt layers.

You'll lead the engineers who build and run our Snowflake warehouse, Fivetran and custom ingestion, the foundational dbt layers, and the orchestration around it, and you'll be hands-on enough to review a dbt model, read a slow query plan, or debug a failed load when it matters.

The bigger reason this role exists is the seam between software engineering and data. Our product and platform engineers ship GifthealthOS and our hub services every day, including the real-time partner integrations that drive operational workflows. Our data team turns what those systems produce into analytics, partner deliverables, and AI inputs. Nobody owns the handoff between them today. You will: the data contracts, change data capture, schema change discipline, and shared onboarding and monitoring standards that let the two sides work as one system. You'll sit at the same table as the Director of Engineering and the Director of Data & Analytics, and the bridge you build is made of contracts and standards, not reorgs.

This is a builder's role in a regulated environment. Our data includes protected health information, and our manufacturer and payer partners hold us to contractual timeliness and quality SLAs. The right person treats HIPAA, auditability, and data contracts as design inputs, not afterthoughts, and still ships fast.


Key Responsibilities

  • The bridge between engineering and data:
    • Data contracts with product and platform engineering: define what GifthealthOS and our hub services commit to emitting (tables, events, change notices), review schema changes before they ship, and make breaking a downstream dataset as visible as breaking a build.
    • Change data capture from the operational systems: own CDC from RDS and the event streams the warehouse and AI products consume, designed with the engineers who own the source systems rather than reverse-engineered after the fact.
    • One partner onboarding and monitoring standard: a shared checklist and observability pattern so a manufacturer or pharmacy feed looks the same operationally whether Engineering built it or your team did. Engineering adopts the standard; you write and maintain it.
    • The SLA evidence layer: proving timeliness and completeness to a partner is a reporting problem even when the feed itself is operational. You own the monitoring and audit trail that answers 'did we meet it' for every partner commitment, across both teams.
    • One set of infrastructure practices: run data infrastructure inside the same AWS accounts, IaC, CI/CD, observability, and on-call model the platform team uses, instead of a parallel stack with its own rules.
    • A seat in engineering's rituals: architecture reviews, release planning, incident reviews, and design docs, so new features and integrations ship with their data story already answered.
  • Where the lines are:
    • Engineering owns operational integrations end to end: anything that runs through GifthealthOS or Digi+Hub and drives a workflow, such as real-time specialty pharmacy status feeds, manufacturer hub APIs, e-prescribing and claims paths. You get that data via CDC and contracts, not by owning the integration.
    • You own warehouse-bound integrations: SaaS and vendor ingestion, batch files from pharmacies and vendors used for reporting, and every outbound reporting deliverable to manufacturers and payers.
    • Data & Analytics owns meaning: marts, metrics, and the semantic layer. You own sources through the staging and intermediate dbt layers. You and the Director of Data & Analytics hold that line together and move it deliberately when it needs to move.
    • The routing rule is yours to enforce: if someone needs to act on data inside the product, it belongs in the product. When a reporting-only feed turns out to matter operationally, you flag it and hand it to Engineering rather than quietly owning it forever.
  • Data platform architecture and roadmap:
    • Own the end-to-end data platform: ingestion, storage, modeling, orchestration, quality, observability, and serving, on Snowflake, dbt, Fivetran, and AWS.
    • Set the architecture: a layered warehouse with clean staging and intermediate foundations that Looker, Metabase, partner feeds, and AI products can all trust.
    • Finish the modernization: complete the move off legacy BI, consolidate orchestration (Airflow, n8n, dbt jobs) onto a supported pattern, and retire one-off pipelines.
    • Manage cost: own Snowflake and Fivetran spend, with rightsizing, workload isolation, and clear chargeback visibility for leadership.
  • Pipelines, integrations, and partner data:
    • Inbound, warehouse-bound: GifthealthOS (our Rails and PostgreSQL platform) via CDC, the pharmacy management system, CloudScript and Digi+Hub services, telephony and support tools, product analytics, and batch files from specialty pharmacies and vendors that exist for reporting, all landed reliably and incrementally.
    • Outbound reporting deliverables: manufacturer, payer, and PBM data exchanges with contractual timeliness and completeness requirements, delivered via SFTP, API, and secure data sharing. You own the delivery pipeline, transport, and SLA evidence. Data & Analytics owns what the file contains, the definitions behind it, and the client conversation.
    • Healthcare data fluency: pharmacy claims (NCPDP), e-prescribing (NCPDP SCRIPT), eligibility and benefit verification, prior authorization, and adverse event reporting, modeled correctly the first time.
    • Change data capture and freshness: move the platform toward near-real-time where the business needs it (fill status, outreach triggers, partner feeds) and batch where it doesn't.
  • Reliability, quality, and governance:
    • SLOs for data: define freshness, completeness, and accuracy targets for tier-1 assets (board reporting, partner feeds, regulatory and safety data), monitor them, and run incident response and postmortems when they're missed.
    • Testing and CI/CD: dbt tests, schema contracts, GitHub-based review, and automated deployment are the default, not the exception.
    • PHI governance, the technical controls: role-based access, column-level masking, de-identified layers for analytics and AI, audit logging, and retention policies that hold up under SOC 2 and HIPAA review. Data & Analytics decides who needs what; you build and enforce the controls that make it true.
    • Catalog and lineage: every tier-1 dataset has a technical owner, documentation, and traceable lineage from source to mart. Business stewardship and metric definitions sit with Data & Analytics; you make them discoverable and enforceable.
  • AI-ready data:
    • Feature and context data: build the clean, well-documented datasets that power predictive modeling in Data & Analytics and the voice and agentic AI products built by Engineering. Own the feature and evaluation datasets; the models and the products that use them belong to those teams.
    • Foundations for self-serve and natural-language analytics: the metadata, lineage, and documented base layers the semantic layer depends on, so conversational and LLM-driven analytics built by Data & Analytics return correct answers.
    • AI-assisted engineering: lead adoption of AI coding and agentic development tools in the data team, with the review discipline to keep quality high.
  • Team and leadership:
    • Build the team: hire, coach, and set career paths for data engineers and analytics engineers; raise the bar on engineering practice; define the on-call and support model.
    • Partner across the company: Data & Analytics, Engineering, Security, pharmacy operations, hub services, and finance all depend on this platform. Translate their needs into a prioritized roadmap and say no when you need to.
    • Represent data engineering to leadership: clear status, honest risk, and a cost story the exec team and board can follow.

Qualifications

  • Education: Bachelors degree preferred. 
  • Experience: 10+ years in data engineering or data platform work, with 4+ years leading teams, including at least one platform you built or materially re-architected and then ran in production.
  • Knowledge, Skills, and Abilities:  
    • Deep, current hands-on skill with the modern stack: Snowflake (or an equivalent cloud warehouse), dbt, a managed ingestion tool such as Fivetran, an orchestrator such as Airflow or Dagster, and AWS. Expert SQL. Strong Python.
    • A software engineering background, not just a data one: you've built or operated production application services (ideally on AWS), you speak the language of API contracts, migrations, and release trains, and engineers see you as one of them.
    • Software engineering discipline applied to data: version control, code review, testing, CI/CD, infrastructure as code, and observability as non-negotiables.
    • Experience with regulated or sensitive data: you've designed access controls, masking, audit, and retention for PHI, PII, or financial data and been through a SOC 2, HITRUST, or similar audit.
    • Operational ownership: you've defined SLOs for data, run on-call, led incident response, and reduced recurring failures over time.
    • Demonstrated application of the above Qualification
    • Cost accountability: you've owned a warehouse and tooling budget and made it smaller or more predictable without slowing the business down.
    • Influence without authority: you've changed how a software engineering team you didn't manage ships data, and you can explain a lineage problem to an engineer, a freshness SLA to a manufacturer partner, and a platform investment to a board member.
    • Nice to have: pharmacy, PBM, hub services, or life sciences experience, especially with NCPDP claims, e-prescribing, eligibility, or prior authorization data.
    • Nice to have: experience sourcing from a Rails and PostgreSQL application, including CDC from RDS and partnering with product engineers on data contracts.
    • Nice to have: experience supporting a BI migration (Looker, Domo, Tableau) from the platform side, including sunsetting legacy extracts and pipelines.
    • Nice to have: building data foundations for ML or LLM products, including feature pipelines, evaluation datasets, retrieval corpora, and model monitoring.
    • Nice to have: experience in a growth-stage company where you built the function rather than inheriting it.

Our Stack

  • Warehouse: Snowflake
  • Ingestion: Fivetran, custom Python connectors, CDC from AWS RDS
  • Transformation: dbt
  • Orchestration: Airflow and n8n today, consolidating
  • BI and analytics: Looker, Metabase
  • Source systems: GifthealthOS (Ruby on Rails, PostgreSQL), pharmacy management system, CloudScript and Digi+Hub services, Five9, Zendesk, Mixpanel
  • Cloud and infra: AWS (RDS, S3, Lambda), GitHub
  • Delivery and tracking: Linear, Notion, Slack
  • AI: Anthropic Claude, in-house voice and agentic AI products built by Engineering, predictive modeling in Data & Analytics

Work Environment

  • Location: Remote (US).
  • Schedule: Full-time; standard business hours.
  • May require participation in an on-call rotation and flexibility for incident response and data SLA escalations.
  • Regular collaboration with Engineering, Data & Analytics, Security, pharmacy operations, hub services, and finance to ensure alignment.

Key Essential Functions

  • Must be able to work at a computer for extended periods
  • Must be able to communicate effectively, verbally and in writing, with engineers, leadership, and cross-functional partners
  • Must be able to handle and access PHI in compliance with HIPAA and data governance requirements
  • Must be able to review code, debug production systems, and respond to incidents, including during on-call rotations

Employment Classification

Status: Full-time
FLSA: Exempt 

Equal Employment Opportunity (EEO) Statement

Gifthealth is an Equal Opportunity Employer and prohibits discrimination and harassment of any kind. All employment decisions are made without regard to race, color, religion, sex, sexual orientation, gender identity, transgender status, national origin, age, disability, veteran status, or any other legally protected status.  

We celebrate diversity and are committed to creating an inclusive environment for all employees. If you do not meet every requirement but still feel you would be a great fit for this role, we encourage you to apply!

Disclaimer

This job description is intended to describe the general nature and level of work being performed. It is not intended to be an exhaustive list of all responsibilities, duties, or skills required of personnel. Gifthealth reserves the right to modify job duties or descriptions at any time.


Salary Description
$164,000-225,000