Director, Data Platforms and Tooling
Zelis · New Jersey, United States · 1 mo ago
$169k–$214k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Position Overview", "What You’ll Do", "What You’ll Bring To Zelis", "Location and Workplace Flexibility", "Base Salary Range", benefits description. Also "A Little About Us" and "A Little About You" but those are generic fluff; we should include only sections with real specific content. The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include: "Position Overview" could be "About the role". "What You’ll Do" could be "Responsibilities". "What You’ll Bring To Zelis" could be "Requirements" or "Qualifications". "Location and Workplace Flexibility" maybe not needed unless specific; but it's generic. Could omit. "Base Salary Range" -> Pay section. Benefits description -> Benefits section.
We should not include "A Little About Us" or "A Little About You" as they are fluff. Also "Equal Employment Opportunity", "Accessibility Support", "Disclaimer" are boilerplate to remove.
Thus sections: About the role (Position Overview), Responsibilities (What You’ll Do), Requirements (What You’ll Bring To Zelis), Pay (Base Salary Range), Benefits (benefits description). Possibly also "Qualifications" but we can combine Requirements.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include: "Position Overview" could be "About the role". "What You’ll Do" could be "Responsibilities". "What You’ll Bring To Zelis" could be "Requirements" or "Qualifications". "Location and Workplace Flexibility" maybe not needed unless specific; but it's generic. Could omit. "Base Salary Range" -> Pay section. Benefits description -> Benefits section.
We should not include "A Little About Us" or "A Little About You" as they are fluff. Also "Equal Employment Opportunity", "Accessibility Support", "Disclaimer" are boilerplate to remove.
Thus sections: About the role (Position Overview), Responsibilities (What You’ll Do), Requirements (What You’ll Bring To Zelis), Pay (Base Salary Range), Benefits (benefits description). Possibly also "Qualifications" but we can combine Requirements.
We need to use - for any list of duties/requirements/benefits. For prose use
. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details from each section.
Let's extract content.
Position Overview paragraph: "Zelis is becoming an AI-Native company, and the Zelis Data Cloud (ZDC) is the data foundation that our analytics, AI, and agentic engineering stand on. The Director, Data Platforms & Tooling owns that foundation's engineering layer: Snowflake platform engineering and scalability, foundational tooling, CI/CD and DevOps for data, and platform governance and security — including the PHI/DLP guardrails required for healthcare data. This leader sets the reference architecture and standards that the other ZDC teams build against. This is a builder-leader role: accountable for a production-grade, secure, scalable platform — not a coordination seat."
We'll put that in
under
About the role
.
Responsibilities: "What You’ll Do" bullet list items (each line starts with a bold heading?). Let's capture each bullet:
- Snowflake platform engineering & scalability — own platform architecture, scalability, and roadmap across data-warehouse, data-lake, and Data Sharing use cases, including open table formats (Apache Iceberg on AWS S3); manage multiple Snowflake accounts (consolidation, migration, modernization); design for resilience (replication, disaster recovery / failover); ensure the platform scales with ingestion volume, AI workloads, and business demand.
- Foundational tooling, CI/CD & DevOps for data — build and own the data DevOps stack: version control, CI/CD for Snowflake / dbt objects, environment automation, infrastructure-as-code, secrets management (Vault / AWS Secrets Manager), and release discipline.
- dbt project administration & standards — own dbt project configuration, model architecture standards, test-coverage enforcement, and model-promotion workflows across environments.
- Platform governance, security & PHI/DLP guardrails — set and enforce governance, security, and data-protection standards (masking, access control, tokenization, encryption, Snowflake Horizon) across environments; partner with Security and Compliance on HIPAA / PHI.
- Reference architecture & standards — define the patterns, standards, and guardrails the other teams adopt — including medallion layering (Bronze/Silver/Gold), semantic views, and ELT/ETL patterns; act as the technical authority for platform decisions.
- Snowflake capability adoption — evaluate emerging Snowflake features (e.g., Cortex AI, Horizon, Data Sharing) and drive adoption to improve performance, scalability, security, and cost.
- Lead & grow the platform team — build and lead the platform engineering, tooling, and release-engineering function; partner closely with the Snowflake administration function on platform standards and reference architecture.
- Enable the AI layer — ready the platform for Cortex AI / Relational AI and agentic workloads (governed access to semantic / ontology layers, safe compute patterns).
- Cost & FinOps stewardship — own platform-level cost governance and consumption efficiency in partnership with Data Operations.
We need to put each as - inside
. Keep the text exactly as given (maybe preserve punctuation). Should we keep the em dash? It's fine.
Requirements: "What You’ll Bring To Zelis" list:
- 10+ years in data platform / data engineering, including 4+ years in engineering leadership.
- Deep Snowflake platform architecture experience at enterprise scale, including performance tuning and cost optimization.
- Strong DevOps / CI/CD / IaC background for data platforms (Terraform, dbt, schemachange, Git-based workflows).
- Proven ownership of platform governance and security, ideally including sensitive-data protection.
- Experience setting reference architecture and standards adopted across multiple teams.
- Deep experience running Snowflake on AWS (S3, storage integrations, networking) and familiarity with core AWS services and cloud cost management.
- Preferred Qualifications (these are separate but we can include as part of Requirements? The instruction: Use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have Requirements for mandatory, Qualifications for preferred. But we prefer few substantive sections; we could combine both into Requirements (or Qualifications). However we need to not create thin sections. Could have Requirements (mandatory) and Qualifications (preferred) as two sections. That's okay if both have content. Let's do that.
Thus:
Requirements
with the first six bullet points (mandatory). Then Qualifications
with the preferred qualifications list:
- Healthcare data experience; strong grasp of HIPAA / PHI and DLP in a cloud data platform.
- Experience preparing a platform for AI/ML and agentic (Cortex / Relational AI) workloads.
- Familiarity with OpenFlow ingestion, medallion architecture, ontology / semantic layers, and Sigma.
- Track record building durable platform teams and maturing platform capabilities.
- SnowPro Advanced: Architect certification a plus.
- Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future. (This is a note; maybe include as part of Qualifications? It's a constraint; we could include as a separate note but maybe better to include as a paragraph under Qualifications? It's not a qualification but a restriction. Could be placed as a after the list. However instructions: remove boilerplate; this is not boilerplate but a constraint. Might keep as a
under Qualifications.
Pay: Base Salary Range $169,000.00 - $213,750.00 plus description about total rewards. We'll put that in
under
Pay
. Include the sentence about base salary range and total rewards description.
Benefits: The paragraph about benefits: "Zelis’ full-time associates are eligible for a highly competitive benefits package as well, which demonstrates our commitment to our employees’ health, well-being, and financial protection. The US-based benefits include a 401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, and health benefits including medical, dental, vision, and prescription drug coverage."
We'll put that under Benefits
as .
We should not include Location and Workplace Flexibility (generic). Also not include "A Little About Us", "A Little About You", EEO, Accessibility, Disclaimer.
Now produce HTML fragment: only the HTML, no markdown fences.
Let's craft.
We need to ensure proper nesting:
About the role
...
Responsibilities
- ...
...
etc.
Make sure to escape any HTML special characters? The text includes ampersands (&) and maybe less-than/greater-than? There's "Snowflake Horizon" etc. No HTML tags. Ampersand should be escaped as & but the instruction didn't mention escaping; but to be safe we can keep as is; but if we output raw & it's okay in HTML as long as not forming an entity. Safer to escape: replace & with &. However the text includes "Snowflake Horizon" no &; "CI/CD" includes slash; "Vault / AWS Secrets Manager" includes slash; "PHI/DLP" includes slash; "SnowPro Advanced: Architect". There's an ampersand in "health, well-being, and financial protection"? Actually "health, well-being, and financial protection" includes "and". No &. There's "401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, and health benefits including medical, dental, vision, and prescription drug coverage." No &. There's "Snowflake platform engineering & scalability" includes an ampersand! Yes: "Snowflake platform engineering & scalability". Also "CI/CD & DevOps". Also "PHI/DLP guardrails". Also "Snowflake Horizon". Also "Snowflake platform engineering & scalability". Also "Foundational tooling, CI/CD & DevOps for data". Also "Snowflake capability adoption — evaluate emerging Snowflake features (e.g., Cortex AI, Horizon, Data Sharing)". Also "Enable the AI layer — ready the platform for Cortex AI / Relational AI and agentic workloads". Also "Cost & FinOps stewardship". Also "health, well-being, and financial protection" no &. Also "Zelis sees across the system". No &.
Thus we need to escape & as &.
Let's replace each & with &.
We'll produce the HTML with escaped ampersands.
Now craft content.
About the role paragraph: copy exactly but replace &.
Original: "Zelis is becoming an AI-Native company, and the Zelis Data Cloud (ZDC) is the data foundation that our analytics, AI, and agentic engineering stand on. The Director, Data Platforms & Tooling owns that foundation's engineering layer: Snowflake platform engineering and scalability, foundational tooling, CI/CD and DevOps for data, and platform governance and security — including the PHI/DLP guardrails required for healthcare data. This leader sets the reference architecture and standards that the other ZDC teams build against. This is a builder-leader role: accountable for a production-grade, secure, scalable platform — not a coordination seat."
Replace & in "Data Platforms & Tooling" -> "Data Platforms& Tooling". Also "CI/CD and DevOps" no &. "PHI/DLP" no &. So only that one.
Also "Snowflake platform engineering and scalability" no &.
Thus paragraph: "Zelis is becoming an AI-Native company, and the Zelis Data Cloud (ZDC) is the data foundation that our analytics, AI, and agentic engineering stand on. The Director, Data Platforms& Tooling owns that foundation's engineering layer: Snowflake platform engineering and scalability, foundational tooling, CI/CD and DevOps for data, and platform governance and security — including the PHI/DLP guardrails required for healthcare data. This leader sets the reference architecture and standards that the other ZDC teams build against. This is a builder-leader role
. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details from each section. Let's extract content. Position Overview paragraph: "Zelis is becoming an AI-Native company, and the Zelis Data Cloud (ZDC) is the data foundation that our analytics, AI, and agentic engineering stand on. The Director, Data Platforms & Tooling owns that foundation's engineering layer: Snowflake platform engineering and scalability, foundational tooling, CI/CD and DevOps for data, and platform governance and security — including the PHI/DLP guardrails required for healthcare data. This leader sets the reference architecture and standards that the other ZDC teams build against. This is a builder-leader role: accountable for a production-grade, secure, scalable platform — not a coordination seat." We'll put that in
under
About the role
. Responsibilities: "What You’ll Do" bullet list items (each line starts with a bold heading?). Let's capture each bullet: - Snowflake platform engineering & scalability — own platform architecture, scalability, and roadmap across data-warehouse, data-lake, and Data Sharing use cases, including open table formats (Apache Iceberg on AWS S3); manage multiple Snowflake accounts (consolidation, migration, modernization); design for resilience (replication, disaster recovery / failover); ensure the platform scales with ingestion volume, AI workloads, and business demand. - Foundational tooling, CI/CD & DevOps for data — build and own the data DevOps stack: version control, CI/CD for Snowflake / dbt objects, environment automation, infrastructure-as-code, secrets management (Vault / AWS Secrets Manager), and release discipline. - dbt project administration & standards — own dbt project configuration, model architecture standards, test-coverage enforcement, and model-promotion workflows across environments. - Platform governance, security & PHI/DLP guardrails — set and enforce governance, security, and data-protection standards (masking, access control, tokenization, encryption, Snowflake Horizon) across environments; partner with Security and Compliance on HIPAA / PHI. - Reference architecture & standards — define the patterns, standards, and guardrails the other teams adopt — including medallion layering (Bronze/Silver/Gold), semantic views, and ELT/ETL patterns; act as the technical authority for platform decisions. - Snowflake capability adoption — evaluate emerging Snowflake features (e.g., Cortex AI, Horizon, Data Sharing) and drive adoption to improve performance, scalability, security, and cost. - Lead & grow the platform team — build and lead the platform engineering, tooling, and release-engineering function; partner closely with the Snowflake administration function on platform standards and reference architecture. - Enable the AI layer — ready the platform for Cortex AI / Relational AI and agentic workloads (governed access to semantic / ontology layers, safe compute patterns). - Cost & FinOps stewardship — own platform-level cost governance and consumption efficiency in partnership with Data Operations. We need to put each as- . Keep the text exactly as given (maybe preserve punctuation). Should we keep the em dash? It's fine.
Requirements: "What You’ll Bring To Zelis" list:
- 10+ years in data platform / data engineering, including 4+ years in engineering leadership.
- Deep Snowflake platform architecture experience at enterprise scale, including performance tuning and cost optimization.
- Strong DevOps / CI/CD / IaC background for data platforms (Terraform, dbt, schemachange, Git-based workflows).
- Proven ownership of platform governance and security, ideally including sensitive-data protection.
- Experience setting reference architecture and standards adopted across multiple teams.
- Deep experience running Snowflake on AWS (S3, storage integrations, networking) and familiarity with core AWS services and cloud cost management.
- Preferred Qualifications (these are separate but we can include as part of Requirements? The instruction: Use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have Requirements for mandatory, Qualifications for preferred. But we prefer few substantive sections; we could combine both into Requirements (or Qualifications). However we need to not create thin sections. Could have Requirements (mandatory) and Qualifications (preferred) as two sections. That's okay if both have content. Let's do that.
Thus:
- ... ...
Requirements
with the first six bullet points (mandatory). ThenQualifications
with the preferred qualifications list: - Healthcare data experience; strong grasp of HIPAA / PHI and DLP in a cloud data platform. - Experience preparing a platform for AI/ML and agentic (Cortex / Relational AI) workloads. - Familiarity with OpenFlow ingestion, medallion architecture, ontology / semantic layers, and Sigma. - Track record building durable platform teams and maturing platform capabilities. - SnowPro Advanced: Architect certification a plus. - Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future. (This is a note; maybe include as part of Qualifications? It's a constraint; we could include as a separate note but maybe better to include as a paragraph under Qualifications? It's not a qualification but a restriction. Could be placed as aafter the list. However instructions: remove boilerplate; this is not boilerplate but a constraint. Might keep as a
under Qualifications. Pay: Base Salary Range $169,000.00 - $213,750.00 plus description about total rewards. We'll put that in
under
Pay
. Include the sentence about base salary range and total rewards description. Benefits: The paragraph about benefits: "Zelis’ full-time associates are eligible for a highly competitive benefits package as well, which demonstrates our commitment to our employees’ health, well-being, and financial protection. The US-based benefits include a 401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, and health benefits including medical, dental, vision, and prescription drug coverage." We'll put that underBenefits
as. We should not include Location and Workplace Flexibility (generic). Also not include "A Little About Us", "A Little About You", EEO, Accessibility, Disclaimer. Now produce HTML fragment: only the HTML, no markdown fences. Let's craft. We need to ensure proper nesting:
About the role
...