Senior Solution Engineer, Retail & Consumer Goods
Snowflake · Chicago, IL · 1 mo ago
Engineering$220k–$289k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines 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" (application instruction). Also remove "To comply with pay transparency requirements..." etc. Also remove "Snowflake employees must abide by the company’s data security plan..." maybe that's not boilerplate? It's about confidentiality; might be considered boilerplate? It's not EEO but still generic policy. Probably remove as it's boilerplate. Also remove "Every Snowflake employee is expected to follow the company’s confidentiality and security standards for handling sensitive data." etc. Also remove "Snowflake is growing fast..." maybe keep as part of About the team? It's about team values; could be part of About the team section. But we only have headings predetermined; we could use About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
Let's extract substantive sections:
- About the role: description of role, mission, remote, travel 25% (later says approx 30% travel). Actually there are two travel mentions: "This is a remote role that requires about 25% travel." and later "Expect approximately 30% travel". Conflict; we need preserve both? Probably keep both statements as they appear. Could combine? But must preserve ALL substantive information; cannot invent or summarize away detail. We could keep both sentences as is.
- Responsibilities: list of duties: "Present Snowflake technology and vision to executives and technical contributors at prospects and customers", "Work hands-on with prospects and customers to demonstrate and communicate the value of Snowflake technology throughout the sales cycle, from demo to proof of concept to design and implementation", "Immerse yourself in the ever-evolving industry, maintaining a deep understanding of competitive and complementary technologies and vendors and how to position Snowflake in relation to them.", "Collaborate with Product Management, Engineering, and Marketing to continuously improve Snowflake’s products and marketing". Also earlier: "work directly with the sales team and channel partners to understand the needs of our customers, strategize on how to navigate winning sales cycles, provide compelling value-based demonstrations, support enterprise Proof of Concepts, and ultimately close business." That's also responsibilities.
- Requirements / Qualifications: "5-7+ years of industry experience with a minimum of 5 years within a pre-sales environment", "Outstanding presenting skills to both technical and executive audiences, whether impromptu on a whiteboard or using presentations and demos.", "5+ years of experience building and deploying machine learning and generative AI solutions in the cloud.", "Possesses a proactive curiosity for the AI landscape, striving to be a visionary and technical thought partner for customers navigating the space.", "A proven ability to leverage AI code generation tools to accelerate productivity and efficiency.", "Broad range of experience within large-scale Database and/or Data Warehouse technology, ETL, analytics and cloud technologies. For example, Data Lake, Data Mesh, Data Fabric", "Hands-on expertise with SQL, SQL analytics, and Python.", "Ability to connect a customer’s specific business problems and Snowflake’s solutions", "Ability to do deep discovery of customer’s architecture framework and connect those with Snowflake Data Architecture.", "University degree in computer science, engineering, mathematics or related fields, or equivalent experience preferred. Masters in DataScience or Business Administration is a plus.", "Experience with GSIs (EY, Deloitte, Accenture, etc), would be beneficial, but not required". Also maybe "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." That's more about culture; could be part of About the role or Requirements.
- Skills: maybe overlapping with requirements; but we can separate: Skills could be "Outstanding presenting skills", "Hands-on expertise with SQL, SQL analytics, and Python.", "Ability to connect...", "Ability to do deep discovery...". But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have "Qualifications" and "Skills". But we need to follow headings list; we can choose which to include. Probably include About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Skills maybe part of Requirements.
Benefits: described: "competitive benefits package that includes: 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." Also equity plan eligibility. Also commission plan.
Pay: compensation range: "total on-target earnings of $220,000 - $288,750. The estimated base salary for this role is $165,000 - $216,562." Also mention commission plan and equity.
Schedule: travel expectation: "This is a remote role that requires about 25% travel." and "Expect approximately 30% travel". Also remote role, candidates can sit anywhere in USA. So schedule includes remote and travel.
We must not include boilerplate like "Snowflake employees must abide by the company’s data security plan..." etc. Also remove "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". Also remove "To comply with pay transparency requirements..." etc. Also remove "Snowflake is growing fast, and we’re scaling our team..." maybe keep as part of About the team? But we don't have About the team heading; we could incorporate into About the role or Responsibilities? Might be considered boilerplate but it's about team culture; maybe keep as part of About the role? Safer to keep only substantive role-specific info. The team description may be considered generic but still part of posting. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The team description is not those; it's about team values. Could keep as part of About the role or a separate section like "About the team". But we don't have that heading; we could use About the role to include team description. However About the role already has content; we could add a paragraph about team.
We must not repeat job title as heading. So no heading for Senior Solution Engineer.
We must output only HTML fragment, no /, no markdown fences.
Let's structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines 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" (application instruction). Also remove "To comply with pay transparency requirements..." etc. Also remove "Snowflake employees must abide by the company’s data security plan..." maybe that's not boilerplate? It's about confidentiality; might be considered boilerplate? It's not EEO but still generic policy. Probably remove as it's boilerplate. Also remove "Every Snowflake employee is expected to follow the company’s confidentiality and security standards for handling sensitive data." etc. Also remove "Snowflake is growing fast..." maybe keep as part of About the team? It's about team values; could be part of About the team section. But we only have headings predetermined; we could use About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
Let's extract substantive sections:
- About the role: description of role, mission, remote, travel 25% (later says approx 30% travel). Actually there are two travel mentions: "This is a remote role that requires about 25% travel." and later "Expect approximately 30% travel". Conflict; we need preserve both? Probably keep both statements as they appear. Could combine? But must preserve ALL substantive information; cannot invent or summarize away detail. We could keep both sentences as is.
- Responsibilities: list of duties: "Present Snowflake technology and vision to executives and technical contributors at prospects and customers", "Work hands-on with prospects and customers to demonstrate and communicate the value of Snowflake technology throughout the sales cycle, from demo to proof of concept to design and implementation", "Immerse yourself in the ever-evolving industry, maintaining a deep understanding of competitive and complementary technologies and vendors and how to position Snowflake in relation to them.", "Collaborate with Product Management, Engineering, and Marketing to continuously improve Snowflake’s products and marketing". Also earlier: "work directly with the sales team and channel partners to understand the needs of our customers, strategize on how to navigate winning sales cycles, provide compelling value-based demonstrations, support enterprise Proof of Concepts, and ultimately close business." That's also responsibilities.
- Requirements / Qualifications: "5-7+ years of industry experience with a minimum of 5 years within a pre-sales environment", "Outstanding presenting skills to both technical and executive audiences, whether impromptu on a whiteboard or using presentations and demos.", "5+ years of experience building and deploying machine learning and generative AI solutions in the cloud.", "Possesses a proactive curiosity for the AI landscape, striving to be a visionary and technical thought partner for customers navigating the space.", "A proven ability to leverage AI code generation tools to accelerate productivity and efficiency.", "Broad range of experience within large-scale Database and/or Data Warehouse technology, ETL, analytics and cloud technologies. For example, Data Lake, Data Mesh, Data Fabric", "Hands-on expertise with SQL, SQL analytics, and Python.", "Ability to connect a customer’s specific business problems and Snowflake’s solutions", "Ability to do deep discovery of customer’s architecture framework and connect those with Snowflake Data Architecture.", "University degree in computer science, engineering, mathematics or related fields, or equivalent experience preferred. Masters in DataScience or Business Administration is a plus.", "Experience with GSIs (EY, Deloitte, Accenture, etc), would be beneficial, but not required". Also maybe "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." That's more about culture; could be part of About the role or Requirements.
- Skills: maybe overlapping with requirements; but we can separate: Skills could be "Outstanding presenting skills", "Hands-on expertise with SQL, SQL analytics, and Python.", "Ability to connect...", "Ability to do deep discovery...". But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have "Qualifications" and "Skills". But we need to follow headings list; we can choose which to include. Probably include About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Skills maybe part of Requirements.
Benefits: described: "competitive benefits package that includes: 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." Also equity plan eligibility. Also commission plan.
Pay: compensation range: "total on-target earnings of $220,000 - $288,750. The estimated base salary for this role is $165,000 - $216,562." Also mention commission plan and equity.
Schedule: travel expectation: "This is a remote role that requires about 25% travel." and "Expect approximately 30% travel". Also remote role, candidates can sit anywhere in USA. So schedule includes remote and travel.
We must not include boilerplate like "Snowflake employees must abide by the company’s data security plan..." etc. Also remove "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". Also remove "To comply with pay transparency requirements..." etc. Also remove "Snowflake is growing fast, and we’re scaling our team..." maybe keep as part of About the team? But we don't have About the team heading; we could incorporate into About the role or Responsibilities? Might be considered boilerplate but it's about team culture; maybe keep as part of About the role? Safer to keep only substantive role-specific info. The team description may be considered generic but still part of posting. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The team description is not those; it's about team values. Could keep as part of About the role or a separate section like "About the team". But we don't have that heading; we could use About the role to include team description. However About the role already has content; we could add a paragraph about team.
We must not repeat job title as heading. So no heading for Senior Solution Engineer.
We must output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
... compensation details ...
Schedule
... remote, travel ...
Check each section for real specific content. About the role: combine initial paragraphs: "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. We are looking for a Senior Solution Engineer who is accustomed to solving customer’s most complex problems and closing large deals. In this role you will work directly with the sales team and channel partners to understand the needs of our customers, strategize on how to navigate winning sales cycles, provide compelling value-based demonstrations, support enterprise Proof of Concepts, and ultimately close business. As a Snowflake Solution Engineer you must share our passion about reinventing the database space, thrive in a dynamic environment and have the flexibility and willingness to jump in and get things done. You are equally comfortable in both a business and technical context, interacting with executives and talking shop with technical audiences. This is a remote role that requires about 25% travel. Candidates can sit anywhere in the USA." Also include "IN THIS ROLE YOU WILL GET TO:" maybe part of responsibilities. But we can incorporate into responsibilities. Responsibilities: list items: - Present Snowflake technology and vision to executives and technical contributors at prospects and customers - Work hands-on with prospects and customers to demonstrate and communicate the value of Snowflake technology throughout the sales cycle, from demo to proof of concept to design and implementation - Immerse yourself in the ever-evolving industry, maintaining a deep understanding of competitive and complementary technologies and vendors and how to position Snowflake in relation to them. - Collaborate with Product Management, Engineering, and Marketing to continuously improve Snowflake’s products and marketing - Work directly with the sales team and channel partners to understand the needs of our customers, strategize on how to navigate winning sales cycles, provide compelling value-based demonstrations, support enterprise Proof of Concepts, and ultimately close business. Maybe combine duplicates. Requirements: list items: - 5-7+ years of industry experience with a minimum of 5 years within a pre-sales environment - Outstanding presenting skills to both technical and executive audiences, whether impromptu on a whiteboard or using presentations and demos. - 5+ years of experience building and deploying machine learning and generative AI solutions in the cloud. - Possesses a proactive curiosity for the AI landscape, striving to be a visionary and technical thought partner for customers navigating the space. - A proven ability to leverage AI code generation tools to accelerate productivity and efficiency. - Broad range of experience within large-scale Database and/or Data Warehouse technology, ETL, analytics and cloud technologies. For example, Data Lake, Data Mesh, Data Fabric - Hands-on expertise with SQL, SQL analytics, and Python. - Ability to connect a customer’s specific business problems and Snowflake’s solutions - Ability to do deep discovery of customer’s architecture framework and connect those with Snowflake Data Architecture. - University degree in computer science, engineering, mathematics or related fields, or equivalent experience preferred. Masters in DataScience or Business Administration is a plus. - Experience with GSIs (EY, Deloitte, Accenture, etc), would be beneficial, but not required. Benefits: list 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 - Eligibility to participate in Snowflake’s commission plan and equity plan Pay: paragraph: - This role is eligible to participate in Snowflake's commission plan and it is common for employees in this role to receive total on-target earnings of $220,000 - $288,750. The estimated base salary for this role is $165,000 - $216,562. Additionally, this role is eligible to participate in Snowflake’s equity