Jobs · Engineering · New York

Senior Solution Engineer, Financial Services

Snowflake · New York, NY · 1 mo ago
Engineering$220k–$289k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The initial paragraph: "At Snowflake, we are powering the era of the agentic enterprise..." up to "You are equally comfortable in both a business and technical context, interacting with executives and talking shop with technical audiences." That's about the role. - Responsibilities: "IN THIS ROLE YOU WILL GET TO:" bullet list: Present Snowflake technology... Work hands-on... Immerse yourself... Collaborate with Product Management... So responsibilities. - Requirements: "ON DAY ONE WE WILL EXPECT YOU TO HAVE:" list: 5-7+ years industry experience with min 5 years pre-sales; Outstanding presenting skills; 5+ years experience building and deploying ML and generative AI solutions in the cloud; Proactive curiosity for AI landscape; Proven ability to leverage AI code generation tools; Broad range of experience within large-scale Database and/or Data Warehouse technology, ETL, analytics and cloud technologies; 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; Expect approximately 30% travel. - Qualifications: Might overlap with requirements. But we can treat "Qualifications" as education and experience? The posting includes "University degree..." etc. Could be under Qualifications. But we already have Requirements covering many. We need to decide sections: maybe combine Requirements and Qualifications? But instructions: Use sections only when posting has real specific content. We can have both if distinct. Let's see: The posting includes "ON DAY ONE WE WILL EXPECT YOU TO HAVE:" which is requirements. Then later "University degree..." etc is also part of that list. So it's all requirements. There's no separate qualifications section distinct from requirements. However there is "About Our Team" which is not a required section heading per list; but we could treat as "About the team" but not in allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have: - About the role: initial paragraph. - Responsibilities: bullet list after "IN THIS ROLE YOU WILL GET TO:". - Requirements: the list after "ON DAY ONE WE WILL EXPECT YOU TO HAVE:" (includes experience, skills, education, etc.) - Skills: maybe we can extract specific skills: presenting skills, AI/ML experience, AI code generation tools, SQL, SQL analytics, Python, etc. But those are already in requirements. Could create Skills section for technical skills: presenting, SQL, Python, AI/ML, etc. But we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections, but better to avoid redundancy. However we could split: Requirements for experience/years, Qualifications for education, Skills for specific abilities. Let's see if we can distinct. Qualifications: 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. Skills: Outstanding presenting skills to both technical and executive audiences; 5+ years of experience building and deploying machine learning and generative AI solutions in the cloud; Possesses a proactive curiosity for the AI landscape; 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; 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. But many of those overlap with requirements. However we can still include them; duplication may be okay but we risk violating "do NOT invent or summarize away detail" but duplication is not inventing. It's okay. Benefits: The posting includes: "This role is also eligible for a 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." Pay: "The following represents the expected range of compensation for this role: 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 plan." Schedule: Travel expectation: "Expect approximately 30% travel". That's schedule? Could be under Schedule section. Also maybe remote? Not mentioned. So we can put travel under Schedule. Now we need to output HTML fragment with headings

for each section, and
  • for any list of duties/requirements/benefits, and

    for prose. We must not include markdown fences. We need to ensure we only include sections with real content. Let's craft:

    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. 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.

    Responsibilities

    • 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

    Requirements

    • 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 (e.g., 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

    Qualifications

    • University degree in computer science, engineering, mathematics or related fields, or equivalent experience preferred
    • Master’s in Data Science or Business Administration is a plus
    • Experience with GSIs (EY, Deloitte, Accenture, etc.) would be beneficial, but not required

    Skills

    • Outstanding presenting skills to both technical and executive audiences
    • 5+ years of experience building and deploying machine learning and generative AI solutions in the cloud
    • Proactive curiosity for the AI landscape
    • Ability to leverage AI code generation tools to accelerate productivity and efficiency
    • Broad experience with large‑scale database/data warehouse technologies, ETL, analytics, and cloud platforms
    • Hands‑on expertise with SQL, SQL analytics, and Python
    • Ability to connect customer business problems with Snowflake solutions
    • Ability to perform deep discovery of customer architecture and map to Snowflake Data Architecture

    Benefits

    • 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

    Pay

    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 plan.

    Schedule

    Expect approximately 30% travel.

    Check for any boilerplate removed: We removed EEO, legal, confidentiality, etc. Also removed "How do you want to make your impact?" and link to careers site. Also removed "About Our Team" paragraph (we omitted). That's okay because not a required heading; but we might lose some substantive info about team values. However the instruction says preserve ALL substantive information. The "About Our Team" paragraph contains substantive info about team values, confidentiality, etc. Should we include it? It could go under About the role maybe? But we already have About the role covering role description. The team paragraph is about team culture, values, confidentiality, security standards. That is substantive. We could incorporate it into About the role as additional paragraph, or create a separate section like "About the team" but not allowed heading. Could we put it under About the role as extra paragraph? That would preserve info.

Similar jobs