Data Engineering Tech Lead
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like EEO etc. Must preserve all substantive info.
We need to parse the posting and extract sections.
Let's identify content:
- Intro paragraph about company: "Expion Health is building the future of pharmacy economics..." This is about the role? Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have sections:
- "The Role" description: responsibilities, what you'll own, etc. Could be "Responsibilities" and maybe "About the role". The "What You'll Own" includes Architecture, Pipelines, Data Quality & Trust, Team Leadership & Mentorship, Analytics & Business Partnership, Scope & Mandate.
- "What We're Looking For": qualifications, requirements, skills.
- "Bonus Points For": additional qualifications.
- "Why Expion, Why Now": maybe about company but could be omitted? Not needed.
- "Benefits & Perks": list of benefits.
- No explicit Pay or Schedule info. So we should not create Pay or Schedule sections because they are not stated.
Thus we will have sections: About the role? Could be the introductory paragraph about the role and company. Could also be "About the role" summarizing the role purpose. We'll include that.
Then Responsibilities: maybe combine "What You'll Own" bullet points.
Then Requirements/Qualifications/Skills: we can combine into Qualifications (or Requirements). The instruction says we can have multiple sections but prefer few substantive sections. We could have "Qualifications" covering required experience, skills, etc. And maybe "Bonus Qualifications" as extra? But we could combine bonus into Qualifications as well.
Better to have sections: About the role, Responsibilities, Qualifications, Benefits.
We must not repeat job title as heading.
We need to use for each section heading.
Inside sections, use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details but can format as lists.
We must not include boilerplate like EEO etc. Also remove duplicated lines.
Let's extract substantive content.
Intro paragraph:
"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."
That's about company. Could be placed under About the role? Might be better as "About the role" includes that plus role description.
"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."
That's more role description.
Then "What You'll Own" with subheadings: Architecture, Pipelines, Data Quality & Trust, Team Leadership & Mentorship, Analytics & Business Partnership, Scope & Mandate.
We can turn each subheading into a list item under Responsibilities? Or we could keep them as subheadings inside Responsibilities using
? But instruction only mentions using for section headings (About the role, Responsibilities, etc). It doesn't forbid other headings, but we should follow instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we can just use - for lists and
for prose. We could embed the subheadings as inside - maybe.
But we need to preserve all substantive information. We can create a Responsibilities section with a list of responsibilities derived from the "What You'll Own" bullet points.
Let's extract each bullet:
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 months include:
- Standardize ingestion and transformation patterns and stand up automated data quality checks and SLAs on the highest-risk pipelines.
- Reduce data incidents and manual reconciliation while modernizing legacy claim-processing flows without disrupting production volume.
- Build a scalable, documented platform that supports new client onboarding and new savings products with materially less engineering effort per client.
Now "What We're Looking For":
- 8 or more years in data engineering, including 2 or more years as a tech lead, staff engineer, or equivalent technical owner of a team's delivery.
- Expert SQL and strong Python, with production experience building and operating distributed data processing such as Spark or AWS Glue.
- Deep hands-on Snowflake experience at scale, including warehouse sizing and cost control, RBAC, secure data sharing, streams and tasks, time travel, query tuning on large claim tables, and clustering strategy.
- Snowpipe experience, including continuous and auto-ingest loading from S3, Snowpipe Streaming, error handling and reconciliation, and knowing when Snowpipe fits versus batch COPY or external tables.
- Snowpark in Python for pushing transformation and feature engineering into Snowflake, including UDFs, UDTFs, and stored procedures.
- Deep AWS data stack experience across S3, Glue, Lambda, Step Functions, and RDS, with IAM and networking fundamentals and AWS-to-Snowflake integration patterns.
- Proven dimensional and warehouse modeling on messy, high-cardinality real-world data, with the ability to defend your grain choices.
- Production orchestration and transformation tooling such as Airflow or Step Functions and dbt on Snowflake.
- Software engineering discipline applied to data: version control, automated testing, CI/CD, infrastructure as code, and monitoring and alerting.
- Demonstrated ownership of data quality and observability in a system where wrong numbers have external consequences.
- A track record of mentoring junior engineers, with specific examples of people who got measurably better working with you.
- Proven ability to work directly with analytics and non-technical business stakeholders, gathering requirements, aligning on definitions, and managing expectations.
- Clear written communication across design docs, runbooks, and incident write-ups that people actually use.
Bonus Points For:
- Healthcare payor or RCM data experience, including claims (837/835), eligibility (834), CPT/HCPCS/ICD-10/DRG/NDC coding, provider data, fee schedules, and reference-based pricing.
- PBM or pharmacy data experience, including formulary, rebates, specialty drug pricing, and claim-level adjudication data.
- Working knowledge of HIPAA in practice, plus SOC 2 or HITRUST control environments.
- Snowflake Cortex, Snowflake ML, or Snowpark ML for in-warehouse AI/ML workloads, plus streaming patterns such as Kinesis or Snowpipe for near-real-time delivery.
- Experience migrating legacy ETL or another warehouse onto Snowflake, and a Snowflake cost optimization track record.
"Why Expion, Why Now": Could be omitted as not needed for sections.
"Benefits & Perks":
- 100% remote – work anywhere in the US
- Medical, dental & vision insurance
- HSA & FSA options
- Access to GLP-1 weight loss program
- Short & long-term disability
- Life Insurance and AD&D
- 401(k) with company match
- Paid Time Off
- Phone & internet allowance
- Town halls & direct access to executive leadership
- A
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details but can format as lists. We must not include boilerplate like EEO etc. Also remove duplicated lines. Let's extract substantive content. Intro paragraph: "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." That's about company. Could be placed under About the role? Might be better as "About the role" includes that plus role description. "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." That's more role description. Then "What You'll Own" with subheadings: Architecture, Pipelines, Data Quality & Trust, Team Leadership & Mentorship, Analytics & Business Partnership, Scope & Mandate. We can turn each subheading into a list item under Responsibilities? Or we could keep them as subheadings inside Responsibilities using
? But instruction only mentions using
for section headings (About the role, Responsibilities, etc). It doesn't forbid other headings, but we should follow instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we can just use
- for lists and
for prose. We could embed the subheadings as inside
- maybe. But we need to preserve all substantive information. We can create a Responsibilities section with a list of responsibilities derived from the "What You'll Own" bullet points. Let's extract each bullet: 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 months include: - Standardize ingestion and transformation patterns and stand up automated data quality checks and SLAs on the highest-risk pipelines. - Reduce data incidents and manual reconciliation while modernizing legacy claim-processing flows without disrupting production volume. - Build a scalable, documented platform that supports new client onboarding and new savings products with materially less engineering effort per client. Now "What We're Looking For": - 8 or more years in data engineering, including 2 or more years as a tech lead, staff engineer, or equivalent technical owner of a team's delivery. - Expert SQL and strong Python, with production experience building and operating distributed data processing such as Spark or AWS Glue. - Deep hands-on Snowflake experience at scale, including warehouse sizing and cost control, RBAC, secure data sharing, streams and tasks, time travel, query tuning on large claim tables, and clustering strategy. - Snowpipe experience, including continuous and auto-ingest loading from S3, Snowpipe Streaming, error handling and reconciliation, and knowing when Snowpipe fits versus batch COPY or external tables. - Snowpark in Python for pushing transformation and feature engineering into Snowflake, including UDFs, UDTFs, and stored procedures. - Deep AWS data stack experience across S3, Glue, Lambda, Step Functions, and RDS, with IAM and networking fundamentals and AWS-to-Snowflake integration patterns. - Proven dimensional and warehouse modeling on messy, high-cardinality real-world data, with the ability to defend your grain choices. - Production orchestration and transformation tooling such as Airflow or Step Functions and dbt on Snowflake. - Software engineering discipline applied to data: version control, automated testing, CI/CD, infrastructure as code, and monitoring and alerting. - Demonstrated ownership of data quality and observability in a system where wrong numbers have external consequences. - A track record of mentoring junior engineers, with specific examples of people who got measurably better working with you. - Proven ability to work directly with analytics and non-technical business stakeholders, gathering requirements, aligning on definitions, and managing expectations. - Clear written communication across design docs, runbooks, and incident write-ups that people actually use. Bonus Points For: - Healthcare payor or RCM data experience, including claims (837/835), eligibility (834), CPT/HCPCS/ICD-10/DRG/NDC coding, provider data, fee schedules, and reference-based pricing. - PBM or pharmacy data experience, including formulary, rebates, specialty drug pricing, and claim-level adjudication data. - Working knowledge of HIPAA in practice, plus SOC 2 or HITRUST control environments. - Snowflake Cortex, Snowflake ML, or Snowpark ML for in-warehouse AI/ML workloads, plus streaming patterns such as Kinesis or Snowpipe for near-real-time delivery. - Experience migrating legacy ETL or another warehouse onto Snowflake, and a Snowflake cost optimization track record. "Why Expion, Why Now": Could be omitted as not needed for sections. "Benefits & Perks": - 100% remote – work anywhere in the US - Medical, dental & vision insurance - HSA & FSA options - Access to GLP-1 weight loss program - Short & long-term disability - Life Insurance and AD&D - 401(k) with company match - Paid Time Off - Phone & internet allowance - Town halls & direct access to executive leadership - A
- for lists and