Lead Analytics Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting: It includes sections: About Vasion (company description), About The Role (role description), What You'll Do (detailed responsibilities), Qualifications, Preferred Qualifications, Benefits, Our Core Values, More About Vasion, Additional Information (EEO). We need to remove boilerplate: Additional Information (EEO) is boilerplate; also "More About Vasion" maybe not needed? It's a link; but we can keep as maybe a short paragraph? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "More About Vasion" is not exactly legal but maybe it's just a link; but it's not substantive content about the role. Could be considered navigation? It's a link to learn more. Might be considered boilerplate? Not sure. Safer to drop it. Also "Our Core Values" maybe considered substantive? It's about company values; could be kept? The instruction: Prefer a few substantive sections over many thin ones. Could include "About Vasion" and "About The Role" and "What You'll Do" and "Qualifications" and "Benefits". "Our Core Values" maybe thin but could be kept as a section? It's not filler; it's specific values. Could include. But we need to avoid too many sections. Maybe combine "About Vasion" and "Our Core Values" into one? But they are distinct. The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About Vasion (company description), About The Role (role overview), Responsibilities (What You'll Do), Qualifications (including Preferred Qualifications maybe combined), Benefits. That's 5 sections. Could also include Core Values as part of About Vasion? Might be okay to keep separate but that adds another section. Let's see if we can combine Core Values into About Vasion as a paragraph. That would reduce sections.
We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from the sections we include. For responsibilities, we need to keep each bullet as list items. For qualifications, we need to keep each bullet. For benefits, we need to keep each bullet.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we can include Benefits section.
We must not repeat job title as heading. The job title is "Lead Analytics Engineer". We must not put that as heading. So we won't.
We must not put Job ID/requisition numbers as headings; none present.
We must remove duplicated lines. Need to check for duplicates: The posting includes "About Vasion" and later "More About Vasion". We'll drop the latter.
We need to remove EEO boilerplate: "Additional Information Vasion is an equal opportunity employer..." We'll drop that.
Now we need to format.
Let's extract content:
About Vasion:
"For more than a decade, Vasion has been helping companies simplify their print infrastructure, automate business processes, and integrate their technology in a more secure environment. Our mission, to make digital transformation attainable for everyone, drives a culture of innovation and exploration. We have one simple goal: help organizations simplify processes through automation and integration. So we created simple, cost-effective, and easy-to-implement digital tools that work together, removing bottlenecks and improving efficiency. And we’re always on the lookout for new people who can help us innovate, grow, and reach our goal."
About The Role:
"Vasion is looking for a Lead Analytics Engineer to serve as the primary technical architect of our data platform. This is a high-ownership, hands-on role where you will design and govern the systems that power our analytics; from ingestion through transformation to the semantic layer feeding our reporting. Beyond the technical work, you will lead project prioritization for the Analytics Engineering team, drive AI-powered analytics initiatives, and mentor 1–2 Analytics Engineers to help elevate their craft. This role does not carry formal people management responsibilities, but your technical leadership will directly shape how the team operates and grows."
What You'll Do: includes several subheadings: Data Architecture & Platform Ownership, Development & Governance, Project Management & Prioritization, AI Analytics Initiatives, Data Quality & Governance, Technical Mentorship. Each has bullet points (some are sentences). We need to turn each bullet into
- . The subheadings themselves could be maybe
? But instruction only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the rule: use for section headings. It doesn't say we cannot use other headings, but to be safe we could treat each subheading as a ? That would create many sections. But we could also keep them as plain text within
or maybe . However we need to preserve ALL substantive information; we can keep subheadings as plain text within or maybe as
but not required. The instruction only mandates for section headings; it doesn't forbid other headings. But to be safe, we can keep them as as separate sections? That would increase sections drastically. The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. So we should not turn each subheading into its own . Instead we can keep the subheadings as plain text (maybe bold) inside a
or as
but not count as section? The instruction only mentions using for section headings (list). It doesn't say we cannot use other heading levels, but to be safe we can just treat the whole "What You'll Do" as a section with heading Responsibilities
and then inside we can have paragraphs with subheadings as or just plain text. That would satisfy.
Similarly Qualifications: we have Qualifications and Preferred Qualifications. Could combine into one section Qualifications
and list both sets as list items, maybe differentiate with a note? But we need to preserve all info; we can just list all qualifications (both required and preferred) as list items, maybe with a note "Preferred:" but that adds text. Could also split into Required and Preferred subheadings inside the section. That's okay.
Benefits: list.
Thus final sections: About Vasion (maybe as About Vasion
), About The Role (maybe as About The Role
), Responsibilities (Responsibilities
), Qualifications (Qualifications
), Benefits (Benefits
). That's 5 sections.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now extract details.
About Vasion paragraph: as above.
About The Role paragraph: as above.
Responsibilities: need to capture all bullet points under each subheading.
Let's list them:
Data Architecture & Platform Ownership:
- Serve as the primary architect of our Snowflake data warehouse — schema design, performance optimization, and cost management
- Own and maintain ELT pipelines via Airbyte Cloud and Fivetran, ensuring reliable, timely data delivery
- Design and maintain the semantic layer and metrics definitions consumed by our AI agents, visualization layer, and other downstream tools
- Establish and enforce standards for data modeling, pipeline design, testing, and documentation
Development & Governance:
- Lead the design and development of dbt models, tests, and documentation in a production environment
- Define best practices for project structure, naming conventions, and incremental strategies
- Own dbt DAG health, model performance, and overall project quality
Project Management & Prioritization:
- Own the Analytics Engineering roadmap — track work, manage priorities, and align delivery with business needs
- Partner with the BI Manager and stakeholders to triage incoming requests and sequence work effectively
- Facilitate planning rituals (sprint planning, backlog grooming) to keep the team focused and unblocked
- Communicate project status, risks, and timelines clearly to both technical and non-technical audiences
AI Analytics Initiatives:
- Lead Vasion's analytics AI strategy — identify, evaluate, and implement AI tools and workflows that enhance data delivery and insights
- Explore and prototype the use of LLMs and AI-assisted tooling within the data stack (e.g., natural language querying, AI-assisted dbt development, anomaly detection)
- Champion a culture of AI curiosity within the BI and Analytics Engineering team
- Stay current on emerging AI/ML capabilities relevant to analytics engineering and bring practical recommendations to the team
Data Quality & Governance:
- Implement and maintain data quality frameworks and alerting across the stack
- Document data lineage, definitions, and ownership in a centralized catalog
- Partner with data consumers to build and maintain trust in the data
Technical Mentorship:
- Guide and mentor 1–2 Analytics Engineers through code reviews, pairing, and technical feedback
- Translate business requirements into clear technical specs the team can execute on
- Help junior team members grow their skills in SQL, dbt, and data modeling best practices
Now Qualifications:
Required Qualifications (under "Qualifications"):
- 5+ years of experience in analytics engineering, data engineering, or a closely related role
- Expert-level SQL and strong data modeling skills (Kimball, OBT, or similar)
- Deep hands-on experience with dbt Core or dbt Cloud in a production environment
- Strong Snowflake expertise — warehouse configuration, query optimization, cost controls, and RBAC
- Experience managing ELT pipelines with tools such as Airbyte or Fivetran
- Ability to manage and prioritize a project backlog, balancing technical debt with new feature delivery
- Strong communicator who can align stakeholders and keep projects moving
- Experience deploying agentic AI tools and building the infrastructure to deliver consistent metrics using AI using Cortex, Claude, or other AI platform
Preferred Qualifications:
- Hands-on experience with LLMs, AI-assisted tooling, or ML pipelines in an analytics context
- Familiarity with Domo or similar BI platforms from a data-delivery perspective
- Experience with data governance frameworks and metadata/catalog tooling
- Python proficiency for pipeline or transformation work
Benefits:
- Flexible work environment
- Vacation Bonus
- Flexible paid time off
- Paid parental leave
- Competitive pay
- A full suite of traditional benefits
- Training/Advancement opportunities
- 401k with company match and immediate vesting
- Financial wellness education
- Company-contributed HSA
- On-site perks include gym, pickleball, snacks & drinks, arcade, theater room, etc.
Now
for prose. Do NOT repeat job title as heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting: It includes sections: About Vasion (company description), About The Role (role description), What You'll Do (detailed responsibilities), Qualifications, Preferred Qualifications, Benefits, Our Core Values, More About Vasion, Additional Information (EEO). We need to remove boilerplate: Additional Information (EEO) is boilerplate; also "More About Vasion" maybe not needed? It's a link; but we can keep as maybe a short paragraph? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "More About Vasion" is not exactly legal but maybe it's just a link; but it's not substantive content about the role. Could be considered navigation? It's a link to learn more. Might be considered boilerplate? Not sure. Safer to drop it. Also "Our Core Values" maybe considered substantive? It's about company values; could be kept? The instruction: Prefer a few substantive sections over many thin ones. Could include "About Vasion" and "About The Role" and "What You'll Do" and "Qualifications" and "Benefits". "Our Core Values" maybe thin but could be kept as a section? It's not filler; it's specific values. Could include. But we need to avoid too many sections. Maybe combine "About Vasion" and "Our Core Values" into one? But they are distinct. The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About Vasion (company description), About The Role (role overview), Responsibilities (What You'll Do), Qualifications (including Preferred Qualifications maybe combined), Benefits. That's 5 sections. Could also include Core Values as part of About Vasion? Might be okay to keep separate but that adds another section. Let's see if we can combine Core Values into About Vasion as a paragraph. That would reduce sections. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from the sections we include. For responsibilities, we need to keep each bullet as list items. For qualifications, we need to keep each bullet. For benefits, we need to keep each bullet.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we can include Benefits section.
We must not repeat job title as heading. The job title is "Lead Analytics Engineer". We must not put that as heading. So we won't.
We must not put Job ID/requisition numbers as headings; none present.
We must remove duplicated lines. Need to check for duplicates: The posting includes "About Vasion" and later "More About Vasion". We'll drop the latter.
We need to remove EEO boilerplate: "Additional Information Vasion is an equal opportunity employer..." We'll drop that.
Now we need to format.
Let's extract content:
About Vasion:
"For more than a decade, Vasion has been helping companies simplify their print infrastructure, automate business processes, and integrate their technology in a more secure environment. Our mission, to make digital transformation attainable for everyone, drives a culture of innovation and exploration. We have one simple goal: help organizations simplify processes through automation and integration. So we created simple, cost-effective, and easy-to-implement digital tools that work together, removing bottlenecks and improving efficiency. And we’re always on the lookout for new people who can help us innovate, grow, and reach our goal."
About The Role:
"Vasion is looking for a Lead Analytics Engineer to serve as the primary technical architect of our data platform. This is a high-ownership, hands-on role where you will design and govern the systems that power our analytics; from ingestion through transformation to the semantic layer feeding our reporting. Beyond the technical work, you will lead project prioritization for the Analytics Engineering team, drive AI-powered analytics initiatives, and mentor 1–2 Analytics Engineers to help elevate their craft. This role does not carry formal people management responsibilities, but your technical leadership will directly shape how the team operates and grows."
What You'll Do: includes several subheadings: Data Architecture & Platform Ownership, Development & Governance, Project Management & Prioritization, AI Analytics Initiatives, Data Quality & Governance, Technical Mentorship. Each has bullet points (some are sentences). We need to turn each bullet into
- . The subheadings themselves could be maybe
? But instruction only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the rule: use for section headings. It doesn't say we cannot use other headings, but to be safe we could treat each subheading as a ? That would create many sections. But we could also keep them as plain text within
or maybe . However we need to preserve ALL substantive information; we can keep subheadings as plain text within or maybe as
but not required. The instruction only mandates for section headings; it doesn't forbid other headings. But to be safe, we can keep them as as separate sections? That would increase sections drastically. The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. So we should not turn each subheading into its own . Instead we can keep the subheadings as plain text (maybe bold) inside a
or as
but not count as section? The instruction only mentions using for section headings (list). It doesn't say we cannot use other heading levels, but to be safe we can just treat the whole "What You'll Do" as a section with heading Responsibilities
and then inside we can have paragraphs with subheadings as or just plain text. That would satisfy.
Similarly Qualifications: we have Qualifications and Preferred Qualifications. Could combine into one section Qualifications
and list both sets as list items, maybe differentiate with a note? But we need to preserve all info; we can just list all qualifications (both required and preferred) as list items, maybe with a note "Preferred:" but that adds text. Could also split into Required and Preferred subheadings inside the section. That's okay.
Benefits: list.
Thus final sections: About Vasion (maybe as About Vasion
), About The Role (maybe as About The Role
), Responsibilities (Responsibilities
), Qualifications (Qualifications
), Benefits (Benefits
). That's 5 sections.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now extract details.
About Vasion paragraph: as above.
About The Role paragraph: as above.
Responsibilities: need to capture all bullet points under each subheading.
Let's list them:
Data Architecture & Platform Ownership:
- Serve as the primary architect of our Snowflake data warehouse — schema design, performance optimization, and cost management
- Own and maintain ELT pipelines via Airbyte Cloud and Fivetran, ensuring reliable, timely data delivery
- Design and maintain the semantic layer and metrics definitions consumed by our AI agents, visualization layer, and other downstream tools
- Establish and enforce standards for data modeling, pipeline design, testing, and documentation
Development & Governance:
- Lead the design and development of dbt models, tests, and documentation in a production environment
- Define best practices for project structure, naming conventions, and incremental strategies
- Own dbt DAG health, model performance, and overall project quality
Project Management & Prioritization:
- Own the Analytics Engineering roadmap — track work, manage priorities, and align delivery with business needs
- Partner with the BI Manager and stakeholders to triage incoming requests and sequence work effectively
- Facilitate planning rituals (sprint planning, backlog grooming) to keep the team focused and unblocked
- Communicate project status, risks, and timelines clearly to both technical and non-technical audiences
AI Analytics Initiatives:
- Lead Vasion's analytics AI strategy — identify, evaluate, and implement AI tools and workflows that enhance data delivery and insights
- Explore and prototype the use of LLMs and AI-assisted tooling within the data stack (e.g., natural language querying, AI-assisted dbt development, anomaly detection)
- Champion a culture of AI curiosity within the BI and Analytics Engineering team
- Stay current on emerging AI/ML capabilities relevant to analytics engineering and bring practical recommendations to the team
Data Quality & Governance:
- Implement and maintain data quality frameworks and alerting across the stack
- Document data lineage, definitions, and ownership in a centralized catalog
- Partner with data consumers to build and maintain trust in the data
Technical Mentorship:
- Guide and mentor 1–2 Analytics Engineers through code reviews, pairing, and technical feedback
- Translate business requirements into clear technical specs the team can execute on
- Help junior team members grow their skills in SQL, dbt, and data modeling best practices
Now Qualifications:
Required Qualifications (under "Qualifications"):
- 5+ years of experience in analytics engineering, data engineering, or a closely related role
- Expert-level SQL and strong data modeling skills (Kimball, OBT, or similar)
- Deep hands-on experience with dbt Core or dbt Cloud in a production environment
- Strong Snowflake expertise — warehouse configuration, query optimization, cost controls, and RBAC
- Experience managing ELT pipelines with tools such as Airbyte or Fivetran
- Ability to manage and prioritize a project backlog, balancing technical debt with new feature delivery
- Strong communicator who can align stakeholders and keep projects moving
- Experience deploying agentic AI tools and building the infrastructure to deliver consistent metrics using AI using Cortex, Claude, or other AI platform
Preferred Qualifications:
- Hands-on experience with LLMs, AI-assisted tooling, or ML pipelines in an analytics context
- Familiarity with Domo or similar BI platforms from a data-delivery perspective
- Experience with data governance frameworks and metadata/catalog tooling
- Python proficiency for pipeline or transformation work
Benefits:
- Flexible work environment
- Vacation Bonus
- Flexible paid time off
- Paid parental leave
- Competitive pay
- A full suite of traditional benefits
- Training/Advancement opportunities
- 401k with company match and immediate vesting
- Financial wellness education
- Company-contributed HSA
- On-site perks include gym, pickleball, snacks & drinks, arcade, theater room, etc.
Now
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from the sections we include. For responsibilities, we need to keep each bullet as list items. For qualifications, we need to keep each bullet. For benefits, we need to keep each bullet. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we can include Benefits section. We must not repeat job title as heading. The job title is "Lead Analytics Engineer". We must not put that as heading. So we won't. We must not put Job ID/requisition numbers as headings; none present. We must remove duplicated lines. Need to check for duplicates: The posting includes "About Vasion" and later "More About Vasion". We'll drop the latter. We need to remove EEO boilerplate: "Additional Information Vasion is an equal opportunity employer..." We'll drop that. Now we need to format. Let's extract content: About Vasion: "For more than a decade, Vasion has been helping companies simplify their print infrastructure, automate business processes, and integrate their technology in a more secure environment. Our mission, to make digital transformation attainable for everyone, drives a culture of innovation and exploration. We have one simple goal: help organizations simplify processes through automation and integration. So we created simple, cost-effective, and easy-to-implement digital tools that work together, removing bottlenecks and improving efficiency. And we’re always on the lookout for new people who can help us innovate, grow, and reach our goal." About The Role: "Vasion is looking for a Lead Analytics Engineer to serve as the primary technical architect of our data platform. This is a high-ownership, hands-on role where you will design and govern the systems that power our analytics; from ingestion through transformation to the semantic layer feeding our reporting. Beyond the technical work, you will lead project prioritization for the Analytics Engineering team, drive AI-powered analytics initiatives, and mentor 1–2 Analytics Engineers to help elevate their craft. This role does not carry formal people management responsibilities, but your technical leadership will directly shape how the team operates and grows." What You'll Do: includes several subheadings: Data Architecture & Platform Ownership, Development & Governance, Project Management & Prioritization, AI Analytics Initiatives, Data Quality & Governance, Technical Mentorship. Each has bullet points (some are sentences). We need to turn each bullet into
? But instruction only says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the rule: use for section headings. It doesn't say we cannot use other headings, but to be safe we could treat each subheading as a ? That would create many sections. But we could also keep them as plain text within
for section headings. It doesn't say we cannot use other headings, but to be safe we could treat each subheading as a ? That would create many sections. But we could also keep them as plain text within
or maybe . However we need to preserve ALL substantive information; we can keep subheadings as plain text within or maybe as or as but not required. The instruction only mandates
for section headings; it doesn't forbid other headings. But to be safe, we can keep them as
as separate sections? That would increase sections drastically. The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. So we should not turn each subheading into its own
. Instead we can keep the subheadings as plain text (maybe bold) inside a
but not count as section? The instruction only mentions using
for section headings (list). It doesn't say we cannot use other heading levels, but to be safe we can just treat the whole "What You'll Do" as a section with heading
Responsibilities
and then inside we can have paragraphs with subheadings as or just plain text. That would satisfy.
Similarly Qualifications: we have Qualifications and Preferred Qualifications. Could combine into one section Qualifications
and list both sets as list items, maybe differentiate with a note? But we need to preserve all info; we can just list all qualifications (both required and preferred) as list items, maybe with a note "Preferred:" but that adds text. Could also split into Required and Preferred subheadings inside the section. That's okay.
Benefits: list.
Thus final sections: About Vasion (maybe as About Vasion
), About The Role (maybe as About The Role
), Responsibilities (Responsibilities
), Qualifications (Qualifications
), Benefits (Benefits
). That's 5 sections.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now extract details.
About Vasion paragraph: as above.
About The Role paragraph: as above.
Responsibilities: need to capture all bullet points under each subheading.
Let's list them:
Data Architecture & Platform Ownership:
- Serve as the primary architect of our Snowflake data warehouse — schema design, performance optimization, and cost management
- Own and maintain ELT pipelines via Airbyte Cloud and Fivetran, ensuring reliable, timely data delivery
- Design and maintain the semantic layer and metrics definitions consumed by our AI agents, visualization layer, and other downstream tools
- Establish and enforce standards for data modeling, pipeline design, testing, and documentation
Development & Governance:
- Lead the design and development of dbt models, tests, and documentation in a production environment
- Define best practices for project structure, naming conventions, and incremental strategies
- Own dbt DAG health, model performance, and overall project quality
Project Management & Prioritization:
- Own the Analytics Engineering roadmap — track work, manage priorities, and align delivery with business needs
- Partner with the BI Manager and stakeholders to triage incoming requests and sequence work effectively
- Facilitate planning rituals (sprint planning, backlog grooming) to keep the team focused and unblocked
- Communicate project status, risks, and timelines clearly to both technical and non-technical audiences
AI Analytics Initiatives:
- Lead Vasion's analytics AI strategy — identify, evaluate, and implement AI tools and workflows that enhance data delivery and insights
- Explore and prototype the use of LLMs and AI-assisted tooling within the data stack (e.g., natural language querying, AI-assisted dbt development, anomaly detection)
- Champion a culture of AI curiosity within the BI and Analytics Engineering team
- Stay current on emerging AI/ML capabilities relevant to analytics engineering and bring practical recommendations to the team
Data Quality & Governance:
- Implement and maintain data quality frameworks and alerting across the stack
- Document data lineage, definitions, and ownership in a centralized catalog
- Partner with data consumers to build and maintain trust in the data
Technical Mentorship:
- Guide and mentor 1–2 Analytics Engineers through code reviews, pairing, and technical feedback
- Translate business requirements into clear technical specs the team can execute on
- Help junior team members grow their skills in SQL, dbt, and data modeling best practices
Now Qualifications:
Required Qualifications (under "Qualifications"):
- 5+ years of experience in analytics engineering, data engineering, or a closely related role
- Expert-level SQL and strong data modeling skills (Kimball, OBT, or similar)
- Deep hands-on experience with dbt Core or dbt Cloud in a production environment
- Strong Snowflake expertise — warehouse configuration, query optimization, cost controls, and RBAC
- Experience managing ELT pipelines with tools such as Airbyte or Fivetran
- Ability to manage and prioritize a project backlog, balancing technical debt with new feature delivery
- Strong communicator who can align stakeholders and keep projects moving
- Experience deploying agentic AI tools and building the infrastructure to deliver consistent metrics using AI using Cortex, Claude, or other AI platform
Preferred Qualifications:
- Hands-on experience with LLMs, AI-assisted tooling, or ML pipelines in an analytics context
- Familiarity with Domo or similar BI platforms from a data-delivery perspective
- Experience with data governance frameworks and metadata/catalog tooling
- Python proficiency for pipeline or transformation work
Benefits:
- Flexible work environment
- Vacation Bonus
- Flexible paid time off
- Paid parental leave
- Competitive pay
- A full suite of traditional benefits
- Training/Advancement opportunities
- 401k with company match and immediate vesting
- Financial wellness education
- Company-contributed HSA
- On-site perks include gym, pickleball, snacks & drinks, arcade, theater room, etc.
Now