Senior Sales Engineer - Public Healthcare - IL, WI, MN

We need to output HTML fragment with sections: About the role? Actually we have "Role Overview" and "Key Responsibilities", "We'd Love to Talk to You If You Have Many of the Following" (qualifications/requirements), "Compensation And Benefits Disclosure" includes pay range and benefits. Also "Job Location" paragraph at top. Also "In-Office Expectations". We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings appropriately. The posting includes: About Cohesity (company overview) maybe "About the role"? Actually "About Cohesity" is company description; could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections with those headings only if we have content. We need to decide which headings to use. We have: - Job Location paragraph: could be a short

maybe under no heading? Could be placed as a

before sections. - About Cohesity: could be under "About the role" heading? Or maybe we treat as "About the role" includes role overview and company description. The role overview is "Role Overview". So we can put that under "About the role". Include Cohesity description and role overview. - Responsibilities: "Key Responsibilities" list. - Requirements/Qualifications/Skills: The "We'd Love to Talk to You If You Have Many of the Following" includes many bullet points: experience, skills, qualifications. We could split into Requirements (experience), Qualifications (education/certifications), Skills (technical). But we can also combine into one section "Requirements" if we want fewer sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine into "Requirements" covering experience, qualifications, skills. Or we could have separate sections if they are substantive. Let's see: The bullet list includes many items: proven experience, experience supporting public healthcare, hands-on experience with backup..., working knowledge of data security concepts, familiarity with healthcare compliance frameworks, understanding of public sector procurement processes, experience supporting proofs of concept, ability to translate technical architecture..., experience partnering with Account Executives..., understanding of enterprise buying processes..., strong communication..., collaborative mindset, familiarity with enterprise data protection..., industry certifications..., Bachelor's degree..., demonstrated ability to leverage AI tools..., Must have English language proficiency..., Willingness to travel as required. That's a lot; could be split into Requirements (experience), Qualifications (education/certifications), Skills (technical/soft). But we can also put all under "Requirements". The instruction says use headings like Requirements, Qualifications, Skills. We could create three sections if each has substantive content. Let's see if we can allocate: - Requirements: Proven experience in pre-sales Sales Engineering..., Experience supporting Public Healthcare is strongly preferred., Hands-on experience with backup..., Working knowledge of data security concepts..., Familiarity with healthcare compliance frameworks..., Understanding of public sector procurement processes..., Experience supporting proofs of concept..., Ability to translate technical architecture..., Experience partnering with Account Executives..., Understanding of enterprise buying processes..., Strong communication..., Collaborative mindset..., Familiarity with enterprise data protection..., Willingness to travel as required. - Qualifications: Bachelor's degree in Computer Science, Engineering, Mathematics, or equivalent practical experience.; Industry certifications in cloud, security, data, or adjacent technologies (AWS, Azure, GCP, CISSP, Security+, etc.) are a plus.; Demonstrated ability to leverage AI tools to improve productivity, streamline workflows, and support technical decision-making.; Must have English language proficiency (able to interact fluently when speaking, reading, and writing in a professional setting). - Skills: maybe we could separate technical skills vs soft skills but we already have communication etc. Could keep skills under Requirements. But we need to follow instruction: Use headings only when posting has real, specific content for it. We have content for each. Also we have Compensation And Benefits Disclosure: includes pay range and benefits description. So we can have

Pay

with pay range, and

Benefits

with benefits description. Also maybe Schedule: we have In-Office Expectations: "Cohesity employees who are within a reasonable commute (e.g. within a forty-five (45) minute average travel time) work out of our core offices 2-3 days a week of their choosing." That's schedule info. So we can put that under

Schedule

. We also have Job Location paragraph at top; we can just put as

before sections. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Data Privacy Notice for Job Candidates", "Equal Employment Opportunity Employer (EEOE)", etc. Those should be removed. Also "Compensation And Benefits Disclosure Pursuant to Applicable State Equal Pay Transparency Laws" is part of compensation section; we can keep the pay range and benefits but remove the preamble about disclosure? The instruction: remove boilerplate, but we need to preserve substantive information. The sentence "Pursuant to Applicable State Equal Pay Transparency Laws This position has a starting pay range as listed below." is somewhat boilerplate but it's part of compensation disclosure; we could keep it as part of Pay section? Might be considered boilerplate but it's directly about pay. Safer to keep the pay range and benefits description; we can drop the introductory sentence if it's generic. However we need to preserve ALL substantive information; the pay range is substantive. The sentence about actual salary depends on many factors is also substantive? It's generic but still about compensation. Might be okay to keep. But we can keep it as part of Pay section. We also need to remove "In-Office Expectations" maybe not boilerplate; it's schedule. Now produce HTML fragment:

Job Location We strongly prefer candidates who are currently located in or near the designated job location. Candidates outside the area should apply only if they are committed to relocating prior to their start date and have the legal right to work in the job location.

Then sections:

About the role

Cohesity is a leader in AI-powered data security and management. Aided by an extensive ecosystem of partners, Cohesity makes it easy to secure, protect, manage, and get value from data — across the data center, edge, and cloud. Cohesity helps organizations defend against cybersecurity threats with comprehensive data security and management capabilities, including immutable backup snapshots, AI-based threat detection, monitoring for malicious behavior, and rapid recovery at scale. We’ve been named a Leader by multiple analyst firms and have been globally recognized for Innovation, Product Strength, and Simplicity in Design. Join us on our mission to shape the future of our industry.

We are seeking a driven and technically strong Sr. Sales Engineer – Public Healthcare to support enterprise sales engagements and help customers adopt Cohesity’s modern data security and management platform. This role is suited for a high-performing Sales Engineer who is building depth across security, data protection, cloud technologies, and regulated industry environments while expanding their ability to independently support complex customer engagements. As a Sr. Sales Engineer, you will partner closely with Account Executives to drive new customer opportunities and expansions by delivering tailored technical solutions. You will support opportunity execution end-to-end, engage a wide range of technical and business stakeholders, and develop credibility as a trusted technical advisor to customers, partners, and public sector organizations.

Responsibilities

• Drive new customer and expansion opportunities by articulating Cohesity's Data Cloud portfolio—including backup, recovery, cyber resilience, and data security management capabilities—to business and technical audiences across Public Healthcare organizations.
• Provide expert, tailored technical support throughout the sales cycle, including discovery, solution design, demonstrations, workshops, and proofs of concept.
• Support technical strategy for enterprise opportunities in partnership with the Account Executive, contributing to deal progression, technical validation, and win strategies.
• Engage with customer stakeholders including IT Infrastructure, Information Security, Compliance, CIO, CISO, and operational leadership teams to align solutions with business and regulatory requirements.
• Enable customers to integrate Cohesity products into existing production environments, responding to technical requests in a timely and professional manner.
• Lead and support technical engagements such as product demonstrations, technical workshops, white papers, proposals, evaluations, and executive presentations.
• Identify customer requirements and risk areas, helping shape proofs of concept that highlight Cohesity's value in cyber resilience, ransomware recovery, data security, and regulatory compliance.
• Support public healthcare sales motions, including technical contributions to RFPs, RFIs, procurement evaluations, contract vehicles, and purchasing frameworks commonly used within healthcare organizations.
• Collaborate with channel partners, systems integrators, and technology alliances to extend solution reach and support successful customer outcomes.
• Assist with competitive displacement conversations by understanding customer environments and positioning Cohesity effectively against legacy and next-generation solutions.
• Collaborate cross-functionally with Product Management, Engineering, Product Marketing, and Support to relay customer feedback and contribute to product improvements, particularly those relevant to healthcare requirements.
• Provide post-sales technical assistance or project support when needed to ensure successful deployment, customer satisfaction, and long-term adoption.

Requirements

• Proven experience in pre-sales Sales Engineering or Solutions Consulting supporting infrastructure, data protection, security, cloud, or cyber resilience solutions in enterprise environments.
• Experience supporting Public Healthcare is strongly preferred.
• Hands-on experience with backup, recovery, data protection, storage, cyber resilience, virtualization, or cloud technologies across on-premises, hybrid, and cloud architectures.
• Working knowledge of data security concepts, including ransomware resilience, immutable storage, encryption, identity and access management, and recovery orchestration.
• Familiarity with healthcare compliance frameworks, including HIPAA, CJIS, FERPA, NIST, StateRAMP, FedRAMP, or similar regulatory standards.
• Understanding of public sector procurement processes, contract vehicles, RFP/RFI response cycles, and purchasing frameworks.
• Experience supporting proofs of concept, evaluations, technical workshops, and decision-making processes involving multiple stakeholder groups.
• Ability to translate technical architecture and security capabilities into clear customer value, business outcomes, and risk reduction strategies.
• Experience partnering with Account Executives to support complex, long-cycle sales opportunities involving technical, operational, security, and executive stakeholders.
• Understanding of enterprise buying processes and deal dynamics within regulated environments.
• Strong communication and presentation skills with the ability to clearly convey technical concepts to business, technical, and executive audiences.
• Collaborative mindset with the ability to manage complex customer situations professionally and confidently.
• Familiarity with enterprise data protection, cybersecurity, or adjacent platforms such as Rubrik, Commvault, Veeam, Dell, Veritas/NetBackup, or similar technologies is a plus.
• Willingness to travel as required.

Qualifications

• Bachelor's degree in Computer Science, Engineering, Mathematics, or equivalent practical experience.
• Industry certifications in cloud, security, data, or adjacent technologies (AWS, Azure, GCP, CISSP, Security+, etc.) are a plus.
• Demonstrated ability to leverage AI tools to improve productivity, streamline workflows, and support technical decision-making.
• Must have English language proficiency (able to interact fluently when speaking, reading, and writing in a professional setting).

Pay

Pay Range $186,2