Senior Director, Analytics Engineering, Data Analytics & AI
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate, navigation, EEO, etc. Do not include sections with placeholder text. Must include sections only when posting has real specific content.
We need to parse content.
Key sections:
- About the role? Could be introductory paragraph describing Snowflake and role. Might be considered "About the role". We'll include a
About the role
with paragraphs.
- Responsibilities: list of duties (the bullet points under "In This Role You Will ...").
- Requirements/Qualifications: list of requirements under "What You Will Need". Could be combined as Requirements.
- Benefits: list of benefits described: medical, dental, vision, life, disability insurance; 401(k); flexible spending & health savings account; at least 12 paid holidays; paid time off; parental leave; employee assistance program; other company benefits.
- Pay: salary range $292,000 - $383,200 plus bonus and equity.
- Schedule: in-office requirement: must be able to work out of Menlo Park office a minimum of 3 days a week.
We must not include placeholder like "commensurate with experience". Not present.
We must not repeat job title as heading. Not include Job ID.
We must not include application instructions like "For jobs located in the United States, please visit the job posting on the Snowflake Careers Site for salary and benefits information: careers.snowflake.com". That's boilerplate; remove.
Also remove confidentiality/security standards paragraph? It's generic but maybe considered boilerplate? It's about confidentiality and security standards; could be considered boilerplate but it's specific to Snowflake. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Confidentiality and security standards might be considered legal boilerplate. Safer to remove that paragraph.
Also remove "Snowflake is growing fast..." paragraph maybe generic but could be considered fluff; but it's about culture. Might keep as part of About the role? Might be considered boilerplate. Safer to keep only substantive content.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details about responsibilities, requirements, benefits, pay, schedule.
We must not create sections with filler. So each section must have real content.
Let's craft HTML:
About the role
At Snowflake, we are powering the era of the agentic enterprise. To usher in this new era, we seek AI-native thinkers across every function who are energized by the opportunity to reinvent how they work. You don’t just use tools; you possess an innate curiosity, treating AI as a high-trust collaborator that is core to how you solve problems and accelerate your impact. We look for low-ego individuals who thrive in dynamic and fast-moving environments and move with an experimental mindset — who rapidly test emerging capabilities to discover simpler, more powerful ways to deliver results. At Snowflake, your role isn't just to execute a function, but to help redefine the future of how work gets done. Snowflake is about empowering enterprises to achieve their full potential with Data & AI. With a culture that's all in on impact, innovation, and collaboration, Snowflake is the sweet spot for building big, moving fast, and taking technology and careers to the next level. We're hiring for a Senior Director of Analytics Engineering to join our Data, Analytics, and AI organization (DAA), reporting directly to the Chief Data & Analytics Officer. You will lead a team of 20+ Analytics Engineers that build and operate the pipelines behind Snowflake's revenue, bookings, people analytics, and go-to-market reporting within our governed data platform. This role has an in-office requirement — you must be able to work out of our Menlo Park office a minimum of 3 days a week.
But schedule is separate; we could mention schedule later. However we included schedule in About the role; but we also need a Schedule section. The instruction: "Prefer a few substantive sections over many thin ones." Could combine schedule into About the role? But they said include a section ONLY when posting has real specific content for it. Schedule is specific: in-office requirement 3 days a week. Could be its own section. However we already mentioned it in About the role; but we could still have a Schedule section with that detail. It's okay to have duplicate? Better to avoid duplication. We could keep About the role without schedule, and then Schedule section with that detail. Let's adjust.
Thus About the role paragraph excludes schedule.
Then Responsibilities: list of duties.
We need to use - for any list of duties/requirements/benefits.
Thus Responsibilities:
Responsibilities
- ...
...
Similarly Requirements: Requirements
- ...
...
Benefits: Benefits
- ...
...
Pay: Pay
The estimated base salary range for this role is $292,000 - $383,200. Additionally, this role is eligible to participate in Snowflake’s bonus and equity plan.
Schedule: Schedule
This role has an in‑office requirement — you must be able to work out of the Menlo Park office a minimum of 3 days a week.
We must ensure we don't include any placeholder like "not specified". Good.
Now check for any leftover boilerplate: The paragraph about confidentiality/security standards removed. The paragraph about Snowflake growing fast etc removed. The line about "Every Snowflake employee is expected to follow the company’s confidentiality and security standards..." removed. Also the line about "Snowflake is growing fast, and we’re scaling our team..." removed. Also the line about "How do you want to make your impact? For jobs located in the United States, please visit the job posting on the Snowflake Careers Site for salary and benefits information: careers.snowflake.com" removed. Also the line about "To comply with pay transparency requirements..." removed? That's legal boilerplate; remove.
Also the paragraph about "The following represents the expected range of compensation for this role:" we kept the salary range but we removed the introductory sentence? We could keep just the range sentence. The line "The following represents the expected range of compensation for this role:" is boilerplate; remove.
Now ensure we didn't miss any substantive info: The responsibilities list includes many items; we need to capture each bullet.
Let's extract responsibilities from text:
"In This Role You Will Lead and grow the Analytics Engineering organization: Manage through your direct reports (team leads/managers), setting priorities and technical strategy across the team.
Drive Snowflake’s internal data transformation: Lead your teams' ongoing work to create an AI ready data foundation, with an emphasis on documentation, contracts, context, and governance.
Own Snowflake’s internal analytics agents: Build, improve, and maintain general purpose analytics agents - and underlying context and semantic layers - that can be used across the organization including evals, orchestration instructions, and ground truth data sets
Champion AI-assisted engineering: Drive adoption of Cortex Code-based agentic workflows and reusable skills across your teams to speed up typical Analytics Engineering jobs-to-be-done, including model development, PR review, and root-cause analysis.
Act as Snowflake’s customer zero: Be the first trusted tester of Snowflake’s own features across the data engineering and transformation stack, deeply engaging with Product and Engineering teams on product and feature roadmaps
Represent Snowflake: Support our GTM and Frontier Engineering teams by joining customer conversations, supporting speaking engagements, and publishing thought leadership, ultimately demonstrating the art of possible on Snowflake to all our customers and prospects
Continually push our stack forward: Push the boundaries of what we can accomplish on Snowflake, adopting the latest internal Data and AI capabilities.
Partner cross-functionally: Serve as the primary point of escalation for business stakeholders, driving towards a common roadmap and transforming upstream processes and workflows with data in mind
Represent your teams upward and cross-org: Contribute your teams' patterns and learnings to the Data, Analytics, and AI org's broader technical initiatives"
We need to turn each into - . Ensure we keep details.
Now requirements list:
"10+ years of experience in analytics engineering, data engineering, or data architecture, including second line leadership experience managing managers or senior individual contributors across multiple teams.
A systems thinker at your core: You naturally see how individual data models, pipelines, and architectural decisions connect — and you design for second-order effects, not just the immediate problem.
Deep expertise in Snowflake, including data modeling, data governance (e.g., RBAC design, row access policies and masking policies), and the broader Snowflake feature set (Dynamic Tables, Streams, Tasks, Horizon, Cortex)
Expert-level dbt skills, including macro development, testing and CI/CD frameworks, and large-scale multi-team project management.
Hands-on experience with Airflow or similar orchestration platforms
A track record owning finance- or revenue-critical, deadline-driven data pipelines where accuracy and auditability are non-negotiable.
Familiarity with GTM and sales analytics domains: master data management, consumption & attainment pipelines, quota/territory data.
Advanced adoption of AI-assisted engineering tools — Cortex Code, Claude Code, or similar agent frameworks — including agentic skill development and prompt engineering for data workflows.
A record of driving large scale data transformation initiatives across complex organizations
Experience with downstream BI/consumption layers such as Streamlit, Sigma, Tableau, etc.
Comfort working in a Jira/Confluence-based agile delivery model.
Excellent written and verbal communication skills, with a track record of writing clear technical specs and stakeholder-facing materials for non-technical audiences"
Make each a
- .
Benefits list:
"medical, dental, vision, life, and disability insurance; 401(k) retirement plan; flexible spending & health savings account; at least 12 paid holidays; paid time off; parental leave; employee assistance program; and other company benefits."
We could split into items: medical, dental, vision, life, and disability insurance; 401(k) retirement plan; flexible spending & health savings account; at least 12 paid holidays; paid time off; parental leave; employee assistance program; other company benefits.
We'll make each as
- .
Pay: we have salary range and bonus/equity.
Schedule: in-office requirement.
Now ensure we didn't include any duplicate content. The About the role paragraph we wrote earlier includes some of the responsibilities description; but we must avoid duplication. Better to keep About the role as a brief overview without repeating the bullet list. Let's craft About the role paragraph that captures the high-level description but not the bullet list.
From the posting: "At Snowflake, we are powering the era of the agentic enterprise. To usher in this new era, we seek AI-native thinkers across every function who are energized by the opportunity to reinvent how they work. You don’t just use tools; you possess an innate curiosity, treating AI as a high-trust collaborator that is core to how you solve problems and accelerate your impact. We look for low-ego individuals who thrive in dynamic and fast-moving environments and move with an experimental mindset — who rapidly test emerging capabilities to discover simpler, more powerful ways to deliver results. At Snowflake, your role isn't just to execute a function, but to help redefine the future of how work gets done. Snowflake is about empowering enterprises to achieve their full potential with Data & AI. With a culture that's all in on impact, innovation, and collaboration,
for prose. Remove boilerplate, navigation, EEO, etc. Do not include sections with placeholder text. Must include sections only when posting has real specific content. We need to parse content. Key sections: - About the role? Could be introductory paragraph describing Snowflake and role. Might be considered "About the role". We'll include a
About the role
with paragraphs. - Responsibilities: list of duties (the bullet points under "In This Role You Will ..."). - Requirements/Qualifications: list of requirements under "What You Will Need". Could be combined as Requirements. - Benefits: list of benefits described: medical, dental, vision, life, disability insurance; 401(k); flexible spending & health savings account; at least 12 paid holidays; paid time off; parental leave; employee assistance program; other company benefits. - Pay: salary range $292,000 - $383,200 plus bonus and equity. - Schedule: in-office requirement: must be able to work out of Menlo Park office a minimum of 3 days a week. We must not include placeholder like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID. We must not include application instructions like "For jobs located in the United States, please visit the job posting on the Snowflake Careers Site for salary and benefits information: careers.snowflake.com". That's boilerplate; remove. Also remove confidentiality/security standards paragraph? It's generic but maybe considered boilerplate? It's about confidentiality and security standards; could be considered boilerplate but it's specific to Snowflake. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Confidentiality and security standards might be considered legal boilerplate. Safer to remove that paragraph. Also remove "Snowflake is growing fast..." paragraph maybe generic but could be considered fluff; but it's about culture. Might keep as part of About the role? Might be considered boilerplate. Safer to keep only substantive content. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details about responsibilities, requirements, benefits, pay, schedule. We must not create sections with filler. So each section must have real content. Let's craft HTML:About the role
At Snowflake, we are powering the era of the agentic enterprise. To usher in this new era, we seek AI-native thinkers across every function who are energized by the opportunity to reinvent how they work. You don’t just use tools; you possess an innate curiosity, treating AI as a high-trust collaborator that is core to how you solve problems and accelerate your impact. We look for low-ego individuals who thrive in dynamic and fast-moving environments and move with an experimental mindset — who rapidly test emerging capabilities to discover simpler, more powerful ways to deliver results. At Snowflake, your role isn't just to execute a function, but to help redefine the future of how work gets done. Snowflake is about empowering enterprises to achieve their full potential with Data & AI. With a culture that's all in on impact, innovation, and collaboration, Snowflake is the sweet spot for building big, moving fast, and taking technology and careers to the next level. We're hiring for a Senior Director of Analytics Engineering to join our Data, Analytics, and AI organization (DAA), reporting directly to the Chief Data & Analytics Officer. You will lead a team of 20+ Analytics Engineers that build and operate the pipelines behind Snowflake's revenue, bookings, people analytics, and go-to-market reporting within our governed data platform. This role has an in-office requirement — you must be able to work out of our Menlo Park office a minimum of 3 days a week.
But schedule is separate; we could mention schedule later. However we included schedule in About the role; but we also need a Schedule section. The instruction: "Prefer a few substantive sections over many thin ones." Could combine schedule into About the role? But they said include a section ONLY when posting has real specific content for it. Schedule is specific: in-office requirement 3 days a week. Could be its own section. However we already mentioned it in About the role; but we could still have a Schedule section with that detail. It's okay to have duplicate? Better to avoid duplication. We could keep About the role without schedule, and then Schedule section with that detail. Let's adjust. Thus About the role paragraph excludes schedule. Then Responsibilities: list of duties. We need to use- for any list of duties/requirements/benefits.
Thus Responsibilities:
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
The estimated base salary range for this role is $292,000 - $383,200. Additionally, this role is eligible to participate in Snowflake’s bonus and equity plan.
Schedule:Schedule
This role has an in‑office requirement — you must be able to work out of the Menlo Park office a minimum of 3 days a week.
We must ensure we don't include any placeholder like "not specified". Good. Now check for any leftover boilerplate: The paragraph about confidentiality/security standards removed. The paragraph about Snowflake growing fast etc removed. The line about "Every Snowflake employee is expected to follow the company’s confidentiality and security standards..." removed. Also the line about "Snowflake is growing fast, and we’re scaling our team..." removed. Also the line about "How do you want to make your impact? For jobs located in the United States, please visit the job posting on the Snowflake Careers Site for salary and benefits information: careers.snowflake.com" removed. Also the line about "To comply with pay transparency requirements..." removed? That's legal boilerplate; remove. Also the paragraph about "The following represents the expected range of compensation for this role:" we kept the salary range but we removed the introductory sentence? We could keep just the range sentence. The line "The following represents the expected range of compensation for this role:" is boilerplate; remove. Now ensure we didn't miss any substantive info: The responsibilities list includes many items; we need to capture each bullet. Let's extract responsibilities from text: "In This Role You Will Lead and grow the Analytics Engineering organization: Manage through your direct reports (team leads/managers), setting priorities and technical strategy across the team. Drive Snowflake’s internal data transformation: Lead your teams' ongoing work to create an AI ready data foundation, with an emphasis on documentation, contracts, context, and governance. Own Snowflake’s internal analytics agents: Build, improve, and maintain general purpose analytics agents - and underlying context and semantic layers - that can be used across the organization including evals, orchestration instructions, and ground truth data sets Champion AI-assisted engineering: Drive adoption of Cortex Code-based agentic workflows and reusable skills across your teams to speed up typical Analytics Engineering jobs-to-be-done, including model development, PR review, and root-cause analysis. Act as Snowflake’s customer zero: Be the first trusted tester of Snowflake’s own features across the data engineering and transformation stack, deeply engaging with Product and Engineering teams on product and feature roadmaps Represent Snowflake: Support our GTM and Frontier Engineering teams by joining customer conversations, supporting speaking engagements, and publishing thought leadership, ultimately demonstrating the art of possible on Snowflake to all our customers and prospects Continually push our stack forward: Push the boundaries of what we can accomplish on Snowflake, adopting the latest internal Data and AI capabilities. Partner cross-functionally: Serve as the primary point of escalation for business stakeholders, driving towards a common roadmap and transforming upstream processes and workflows with data in mind Represent your teams upward and cross-org: Contribute your teams' patterns and learnings to the Data, Analytics, and AI org's broader technical initiatives" We need to turn each into - . Ensure we keep details. Now requirements list: "10+ years of experience in analytics engineering, data engineering, or data architecture, including second line leadership experience managing managers or senior individual contributors across multiple teams. A systems thinker at your core: You naturally see how individual data models, pipelines, and architectural decisions connect — and you design for second-order effects, not just the immediate problem. Deep expertise in Snowflake, including data modeling, data governance (e.g., RBAC design, row access policies and masking policies), and the broader Snowflake feature set (Dynamic Tables, Streams, Tasks, Horizon, Cortex) Expert-level dbt skills, including macro development, testing and CI/CD frameworks, and large-scale multi-team project management. Hands-on experience with Airflow or similar orchestration platforms A track record owning finance- or revenue-critical, deadline-driven data pipelines where accuracy and auditability are non-negotiable. Familiarity with GTM and sales analytics domains: master data management, consumption & attainment pipelines, quota/territory data. Advanced adoption of AI-assisted engineering tools — Cortex Code, Claude Code, or similar agent frameworks — including agentic skill development and prompt engineering for data workflows. A record of driving large scale data transformation initiatives across complex organizations Experience with downstream BI/consumption layers such as Streamlit, Sigma, Tableau, etc. Comfort working in a Jira/Confluence-based agile delivery model. Excellent written and verbal communication skills, with a track record of writing clear technical specs and stakeholder-facing materials for non-technical audiences" Make each a
- . Benefits list: "medical, dental, vision, life, and disability insurance; 401(k) retirement plan; flexible spending & health savings account; at least 12 paid holidays; paid time off; parental leave; employee assistance program; and other company benefits." We could split into items: medical, dental, vision, life, and disability insurance; 401(k) retirement plan; flexible spending & health savings account; at least 12 paid holidays; paid time off; parental leave; employee assistance program; other company benefits. We'll make each as
- . Pay: we have salary range and bonus/equity. Schedule: in-office requirement. Now ensure we didn't include any duplicate content. The About the role paragraph we wrote earlier includes some of the responsibilities description; but we must avoid duplication. Better to keep About the role as a brief overview without repeating the bullet list. Let's craft About the role paragraph that captures the high-level description but not the bullet list. From the posting: "At Snowflake, we are powering the era of the agentic enterprise. To usher in this new era, we seek AI-native thinkers across every function who are energized by the opportunity to reinvent how they work. You don’t just use tools; you possess an innate curiosity, treating AI as a high-trust collaborator that is core to how you solve problems and accelerate your impact. We look for low-ego individuals who thrive in dynamic and fast-moving environments and move with an experimental mindset — who rapidly test emerging capabilities to discover simpler, more powerful ways to deliver results. At Snowflake, your role isn't just to execute a function, but to help redefine the future of how work gets done. Snowflake is about empowering enterprises to achieve their full potential with Data & AI. With a culture that's all in on impact, innovation, and collaboration,