Senior Solution Architect (Presales)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. We must not include Job ID etc. Remove boilerplate like EEO, navigation, etc. Must preserve all substantive info. We need to parse the posting. Content: - About Starburst (company description) - maybe not needed as section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. The posting includes "About The Role" (that's about the role). So we can have

About the role

with content. - Responsibilities: There's a list: "Responsibilities include demonstrations of Starburst capabilities, technical sales presentations, delivery of educational sessions and/or technical workshops, running proofs of value, providing guidance for migration from legacy platforms, and assistance with customers moving to production." Also later bullet list under "As a Senior Solution Architect At Starburst You Will" includes many items. Those are responsibilities. So we can combine into a

. - Requirements: The posting includes "Some Of The Things We Look For Expertise or Experience in one or more of the following technical areas:" then a list: Analytical and problem-solving skills, ANSI SQL, UNIX/Linux CLI interactions, Data Warehouse usage and concepts, Private/Public Cloud Deployments, Big Data Technologies: Hadoop, distributed systems and storage, Experience in customer-facing technical roles, Experience in field sales/field consultant roles, Strong presentation skills and an ability to respond dynamically to questions in real-time, Excellent verbal and written communication skills, Desire to work in a fast-paced startup environment with cutting-edge technologies. That's requirements/qualifications/skills. We need to separate into Requirements, Qualifications, Skills as appropriate. The instruction says use those headings if there is real specific content. We can map: Requirements could be the technical expertise list; Qualifications could be experience in customer-facing technical roles, field sales/consultant roles; Skills could be presentation skills, communication, desire to work fast-paced. But we need to avoid thin sections. Perhaps combine into one "Requirements" section with all. However they ask to prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements (covering all). Then Benefits, Pay, Schedule if present. Benefits: The posting mentions: "All employees receive equity packages (ISOs) and have access to a comprehensive benefits offering." Also later: "Our global workforce is supported by a competitive Total Rewards program that reflects our commitment to a rewarding and supportive work environment. This includes a variety of benefits like competitive pay, attractive stock grants, flexible paid time off, and more." So we have benefits content. So we can include Benefits section. Pay: There's a Pay Range $230,000 - $260,000 USD. Also mention variable compensation, equity, etc. So we include Pay section. Schedule: There's travel requirement: "Ability to Travel: This role will require 25% in-person travel..." Also maybe schedule not specified beyond travel. Could we treat travel as schedule? The instruction: include Schedule section only if posting actually states them. The posting mentions travel expectations. That's somewhat schedule-related. Could include Schedule section with travel info. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. Travel is stated, so we can include Schedule. We must not include filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement at end: "Starburst provides equal employment opportunities..." That's boilerplate; remove. Also "Learn more at starburst.ai." maybe not needed but it's about company; could be part of About Starburst but not needed for sections. We can keep company description? Not required for sections; but we might keep it as part of About the role? Probably not needed. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all substantive info from posting, but we can omit boilerplate. The company description "About Starburst" is substantive? It describes the company; might be considered substantive. However the instruction about sections only for certain headings; we could include it as a paragraph before sections? The instruction says output ONLY the HTML fragment; we can include

for prose. So we could include a paragraph about Starburst as intro. But they didn't give a heading for that; we can just put it as a

before sections. That's okay. Similarly "About The Role" heading we will convert to

About the role

and then prose. We must not duplicate lines. Let's extract substantive content: Company description: "About Starburst Starburst delivers enterprise intelligence at scale by giving organizations secure, governed access to all their data, wherever it lives. Built for distributed data environments, Starburst helps enterprises power AI and analytics without the cost and complexity of traditional data consolidation. With open standards including Trino and Apache Iceberg, Starburst enables trusted access to complete enterprise context while helping organizations avoid vendor lock-in. Leading global enterprises trust Starburst to fuel AI, analytics, and enterprise intelligence. Learn more at starburst.ai." We could keep that as a paragraph. About the role: "About The Role Starburst Solution Architects will partner with field sales representatives to own the technical aspects of the sales cycle, customer evangelization, and qualification process, from discovery calls to closure. Responsibilities include demonstrations of Starburst capabilities, technical sales presentations, delivery of educational sessions and/or technical workshops, running proofs of value, providing guidance for migration from legacy platforms, and assistance with customers moving to production. Solutions Architects are Starburst experts who will provide technical leadership, data management, and analytics experience and consultation. In this customer-facing and highly technical role, you will work directly with our customers to ensure their overall success with Starburst’s product offering in a pre sales capacity." Then the list under "As a Senior Solution Architect At Starburst You Will" includes many items. Those are responsibilities as well. We'll combine. Responsibilities list: - Grow and retain accounts - Own the technical aspects of the sales cycle and work closely with sales representatives to drive customer projects to closure - Shape prospect evaluation requirements, define success criteria, educate customers, and participate in the qualification process - Define, scope, and execute customer proof of concept studies - Be an expert in our products and services - Design and build demos, presentations, reference architectures, and custom integrations - Perform overall system and SQL performance tuning and migrations from legacy systems - Act as the consultant and expert on architecture, deployment, and design discussions - Act as the primary customer-facing technical resource during technology evaluations - Act as the voice of the customer during internal product engineering discussions - Collaborate with Engineering and Support teams for critical customer operational issues and questions - Develop field best practices, how-to documents, and contribute to our internal knowledge base - Ability to Travel: This role will require 25% in-person travel for purposes including but not limited to new hire onboarding, team and department offsites, customer engagements, and other company events. Actual travel expectations may vary by role and business needs. We could keep travel as separate schedule section. Requirements/Qualifications/Skills list: "Some Of The Things We Look For Expertise or Experience in one or more of the following technical areas: - Analytical and problem-solving skills - ANSI SQL - UNIX/Linux CLI interactions - Data Warehouse usage and concepts - Private/Public Cloud Deployments - Big Data Technologies: Hadoop, distributed systems and storage - Experience in customer-facing technical roles - Experience in field sales/field consultant roles - Strong presentation skills and an ability to respond dynamically to questions in real-time - Excellent verbal and written communication skills - Desire to work in a fast-paced startup environment with cutting-edge technologies" We could split: Requirements: technical expertise list (first six). Qualifications: experience in customer-facing technical roles, field sales/field consultant roles. Skills: presentation skills, communication, desire to work fast-paced. But to avoid thin sections, maybe combine all into Requirements. However the instruction says prefer a few substantive sections over many thin ones. Having three sections each with a few items might be okay if they are substantive. But we risk creating thin sections if each only has a couple items. Let's see: Requirements (technical expertise) would have 6 items; Qualifications (experience) 2 items; Skills (presentation, communication, desire) 3 items. That's not too thin. Could be okay. But we need to decide headings: Requirements, Qualifications, Skills. Use

for each. Benefits: "All employees receive equity packages (ISOs) and have access to a comprehensive benefits offering." plus later: "Our global workforce is supported by a competitive Total Rewards program that reflects our commitment to a rewarding and supportive work environment. This includes a variety of benefits like competitive pay, attractive stock grants, flexible paid time off, and more." We'll combine. Pay: "Pay Range $230,000 - $260,000 USD" plus mention variable compensation, equity, etc. Also "All employees receive equity packages (ISOs)" already in benefits but could be mentioned. We'll keep Pay section with salary range and note variable compensation/commission/bonus. Schedule: Travel requirement: "Ability to Travel: This role will require 25% in-person travel for purposes including but not limited to new hire onboarding, team and department offsites, customer engagements, and other company events. Actual travel expectations may vary by role and business needs." We'll put that. We must not include duplicated lines. Ensure we don't repeat the same info. Now produce HTML fragment. Structure:

About Starburst ...

About the role

Starburst Solution Architects will partner with field sales representatives to own the technical aspects of the sales cycle, customer evangelization, and qualification process, from discovery calls to closure. Responsibilities include demonstrations of Starburst capabilities, technical sales presentations, delivery of educational sessions and/or technical workshops, running proofs of value, providing guidance for migration from legacy platforms, and assistance with customers moving to production. Solutions Architects are Starburst experts who will provide technical leadership, data management, and analytics experience and consultation. In this customer-facing and highly technical role, you will work directly with our customers to ensure their overall success with Starburst’s product offering in a pre sales capacity.

• Grow and retain accounts
• Own the technical aspects of the sales cycle and work closely with sales representatives to drive customer projects to closure
• Shape prospect evaluation requirements, define success criteria, educate customers, and participate in the qualification process
• Define, scope, and execute customer proof of concept studies
• Be an expert in our products and services
• Design and build demos, presentations, reference architectures, and custom integrations
• Perform overall system and SQL performance tuning and migrations from legacy systems
• Act as the consultant and expert on architecture, deployment, and design discussions
• Act as the primary customer-facing technical resource during technology evaluations
• Act as the voice of the customer during internal product engineering discussions
• Collaborate with Engineering and Support teams for critical customer operational issues and questions
• Develop field best practices, how-to documents, and contribute to our internal knowledge base

Requirements

• Analytical and problem-solving skills
• ANSI SQL
• UNIX/Linux CLI interactions
• Data Warehouse usage and concepts
• Private/Public Cloud Deployments
• Big Data Technologies: H