Expion Health is building the future of pharmacy economics. As architects of prescription economics, we design how pharmacy value is created, aligning cost, clinical decisions, and performance into one accountable system that moves beyond rebates. We help organizations stay ahead of pharmacy market change with clear insight, bold thinking, and strategies built for what's next, leading the next era of prescription economics.
The Role
The Data Engineering Tech Lead is the senior technical owner for a data engineering pod at Expion Health, hands-on for the hardest work and accountable for the design, quality, and delivery of the rest. You will build and scale the ingestion, transformation, and serving layers behind claim repricing, savings analytics, and client reporting, in an environment where a data defect is a mispriced claim and a compliance issue, not just a broken dashboard.
This is a lead role, not a people-management role, but two things are core to it and not optional: growing junior and mid-level engineers, and working shoulder to shoulder with analytics and the business. You will set technical direction, run design and code review, coach the team, and sit close enough to pharmacy and medical cost-management stakeholders to know what actually drives savings.
If you have built healthcare data platforms at scale, know Snowflake and AWS deeply, and want to shape a platform that is central to how the business makes money, this role was built for you.
What You'll Own
- Architecture
- Design and evolve the data platform on Snowflake and AWS, including ingestion, storage, orchestrated transformation, and the serving layer feeding ExpionIQ analytics, client reporting, and ML/AI models.
- Own Snowflake architecture end to end: database and schema design, Snowpipe ingestion, in-warehouse transformation with Snowpark and dbt, RBAC and PHI-safe access patterns, and warehouse sizing and credit consumption against a budget.
- Make and document the build-vs-buy and pattern decisions across batch versus streaming, ELT in Snowflake versus external Spark, modeling, and CDC, and drive them to consensus with architecture and security.
- Modernize legacy claim-processing data flows onto repeatable, testable pipelines without disrupting production repricing volume.
- Pipelines
- Ingest and normalize high-volume healthcare data, including X12 EDI (837 claims, 835 remittance, 834 eligibility), provider and facility rosters, CMS and state fee schedules, contract and network terms, NDC and drug pricing files, and rebate and invoice data.
- Build dimensional and semantic models that let analysts answer how much was saved, on which claims, versus what benchmark, without reverse-engineering SQL.
- Support AI and automation workflows such as document understanding, claim reconciliation, and anomaly detection with clean, well-labeled, reproducible training and inference data.
- Data Quality & Trust
- Stand up data quality as a first-class system: contracts, expectations, reconciliation controls against source-of-truth totals, freshness and volume SLAs, and alerting that pages a human before a client notices.
- Own lineage, cataloging, and documentation so pricing logic is auditable end to end.
- Enforce PHI and PII handling by design under HIPAA, including least-privilege access, encryption, tokenization or de-identification, and retention rules.
- Team Leadership & Mentorship
- Mentor junior and mid-level engineers day to day through pairing, teaching-oriented code review, and direct, useful feedback.
- Assign work deliberately for development, stretching engineers onto designs and pipelines you could have written yourself while staying available to unblock them.
- Onboard new engineers into the claim and pharmacy data domains and build the documentation, runbooks, and reference implementations that shorten the ramp for the next hire.
- Set and enforce engineering standards for code review, testing, CI/CD, infrastructure as code, and observability, and reduce key-person risk across the pod.
- Run technical design reviews, break roadmap epics into estimable work, and serve as the escalation point for production data incidents.
- Analytics & Business Partnership
- Partner with analytics and BI teams to co-design the semantic and reporting layer and agree on metric definitions so savings means the same thing in every dashboard, client report, and model.
- Sit with pharmacy and medical cost-management, operations, and client-facing teams to understand the workflows behind the data before designing for it.
- Translate in both directions, turning ambiguous business asks into concrete data requirements and explaining technical trade-offs in terms stakeholders can decide on.
- Support client onboarding and audit or reporting requests as a partner to the business, turning recurring one-off asks into self-service data products.
Take on other work as needed to support the broader goals of the department and the company.
Scope & Mandate
Role
This role owns the data platform behind claim repricing, savings analytics, and client reporting, and leads a pod that combines direct employees and contract resources. Priority mandates for the first 6 to 12