Director, Business Development - Security

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. No Job ID. Remove boilerplate like EEO, legal, etc. Must preserve substantive info. We need to parse the posting: It includes description about Cohesity, role description, responsibilities (list of bullet points), qualifications (minimum of 5 years experience etc), "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" that's qualifications/requirements. Then "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" maybe additional preferred qualifications. Then "HOW YOU WILL BE MEASURED:" maybe performance metrics, could be part of Responsibilities or Qualifications? Could be separate but not required. Then Pay range: $269,280.00-$336,600.00. Benefits: mention comprehensive benefits framework, health and wellness, vacation, paid holidays, refresh days, 401(k), life and disability insurance, etc. Schedule: In-Office Expectations: 2-3 days a week in office for those within commute. Also mention travel as required. We need sections: About the role (maybe introductory paragraph about Cohesity and role purpose). Responsibilities (list of duties). Requirements (minimum experience etc). Qualifications (maybe same as requirements? Could combine). But we need to follow instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We have content for About the role: first paragraph describing Cohesity and mission, plus description of Security specialist organization and role purpose. Could be About the role. Responsibilities: the list under "HOW YOU’LL SPEND YOUR TIME HERE:" bullet points. Requirements: the "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list (minimum 5 years experience etc). That's requirements. Qualifications: maybe the "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list (experience supporting newly formed specialist org, etc). Could be qualifications or preferred qualifications. Skills: maybe cross-functional operating skills, data fluency, communication skills, AI tools, etc. Could be extracted from requirements list. But we already have those in requirements. Could create Skills section for things like strong written and visual communication, data fluency, program-management discipline, etc. But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all info; we can distribute across sections but must not lose any. Could combine some. Better: Use sections: About the role (intro). Responsibilities (the bullet list). Requirements (minimum 5 years experience etc). Qualifications (extra excited if you have). Skills (maybe cross-functional operating skills, data fluency, program-management discipline, strong written/visual communication, AI tools). Benefits (benefits framework). Pay (pay range). Schedule (In-Office Expectations and travel). Ensure we don't create sections with filler. Let's extract details. About the role: Could be first two paragraphs: "Cohesity is a leader in AI-powered data security and management.... Join us on our mission to shape the future of our industry. The Security specialist organization is a founding team: a lean group of Security Sales Specialists and Solutions Architects covering the highest-priority markets first, with more markets earning dedicated coverage over time. A team this size can't put a dedicated person in every territory on day one, and it can't afford every rep independently rebuilding enablement or waiting on operational support that doesn't exist yet. This role is both things a lean specialist team needs and doesn't yet have: the scale mechanism that generates coverage in markets without a dedicated rep, and the connective tissue that keeps a fast-growing, globally distributed team operating as one function instead of independent pods. You have two jobs that reinforce each other. First, you own go-to-market motion and pipeline generation for every market without a dedicated Security Sales Specialist or Security Solutions Architect — through targeted campaigns, partner-sourced pipeline, and programs that reach accounts the core team can't cover directly. Second, you are the operational hub for the specialist organization itself — enablement, reporting, cross-functional coordination, and the infrastructure that lets the VP, the Solutions Architecture leader, and the field spend their time selling and coaching instead of building decks and chasing status updates. At the center of this role is one standing responsibility: helping structure and maintain a cohesive, impactful operating model for the Security specialist organization as it scales." That's good. Responsibilities: bullet list under "HOW YOU’LL SPEND YOUR TIME HERE:": - Own an assigned quota for markets without dedicated coverage — build and run targeted campaigns, plays, and programs that generate and convert pipeline. - Own the data model that signals when a market is ready for dedicated coverage, and manage joint go-to-market programs with technology and channel partners. - Build direct executive relationships between Cohesity and customer security leadership — briefing programs, roundtables, and a consistent point of view. - Be the cross-functional connective tissue for the specialist organization — the single point of coordination with Marketing, Sales/Revenue Operations, Product, and the broader delivery ecosystem. - Own and maintain the team's enablement and positioning library, and scale what works into repeatable sales plays, programs, and campaigns. - Design and run internal sales incentives, and own territory data hygiene and the reporting infrastructure that gives leadership a single source of truth. - Build and maintain the recurring leadership narrative, run the team's operating cadence, and partner with recruiting on hiring pipeline and ramp logistics. We'll put each as

. Requirements: "WE’D LOVE TO TALK TO YOU IF YOU HAVE MANY OF THE FOLLOWING:" list: - Minimum of 5 years of experience in the cybersecurity industry, with a focus on business development and strategic partnerships. - Demonstrated success building and scaling partner-driven growth initiatives in a global environment. - Demonstrable experience driving scale in a global environment. - Experience building demand-generation or scale-coverage programs, and managing partner/channel go-to-market programs — co-marketing, deal registration, joint pipeline. - Strong cross-functional operating skills — comfortable being the connective tissue among Sales, Marketing, Product, and Operations without formal authority. - Data fluency and program-management discipline — able to run multiple concurrent workstreams without dropping any of them. - Strong written and visual communication skills, and experience designing sales incentive programs that turn a one-off win into a repeatable play. - Demonstrated ability to leverage AI tools to enhance productivity, streamline workflows, and support decision making. - Professional English language proficiency for customer and internal communication. - The ability to travel as required for the role. We'll put these as

. Qualifications: "WE ARE EXTRA EXCITED IF YOU HAVE ANY OF THE FOLLOWING:" list: - Experience supporting a newly formed or fast-scaling specialist / overlay sales organization, with background in cybersecurity, data protection, or cyber-resilience markets. - Experience with territory or trigger-based coverage models, and building recruiting pipeline or onboarding programs with a hiring manager or Talent team. We'll put as

. Skills: Might be redundant but we could extract specific skill items not covered elsewhere: maybe "Strong cross-functional operating skills", "Data fluency and program-management discipline", "Strong written and visual communication skills", "Experience designing sales incentive programs", "Demonstrated ability to leverage AI tools". However these are already in requirements. To avoid duplication, we could either not include Skills section, or we could include only those not already captured. But instruction: Preserve ALL substantive information; we can keep them in Requirements and not duplicate. If we omit Skills section, we are not losing info because it's already in Requirements. That's acceptable. However we need to decide if we should include Skills heading only if there is real specific content not already elsewhere. Since we have skill-like content in Requirements, we could still create Skills section but would duplicate. Better to omit Skills section to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills. Benefits: from "Additionally, full-time employees are eligible to participate in our comprehensive benefits framework, including health and wellness benefits, vacation, paid holidays and refresh days, 401(k) retirement plan, life and disability insurance coverages, and other benefits the Company may offer from time to time." We'll put as

• ... each benefit maybe separate? Could be one
• with list. But better to split: health and wellness benefits, vacation, paid holidays and refresh days, 401(k) retirement plan, life and disability insurance coverages, other benefits. Pay: Pay Range: $269,280.00-$336,600.00. Also mention that compensation noted above is based on an annualized hourly rate assuming normal full-time employment. Current pay transparency shows the OTE (On-Target Earnings) for commission-based roles. Also mention may be eligible for bonus compensation, commission (if in a sales function), and/or equity grants. We'll include that. Schedule: 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. 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." Also mention travel as required for the role (already in requirements). We'll include schedule: expected 2-3 days in office per week for local candidates, relocation expectation, travel as required. We must not include boilerplate like EEO, legal, Data Privacy Notice, etc. Now produce HTML fragment with headings

  for each section. Use

  • for lists. Use

    for prose. We'll structure:

    About the role

    ... (the paragraph(s) )

    Responsibilities

    • ...
    ...

    Requirements

    ...

    Qualifications

    ...

    Benefits

    ...

    Pay

    ...

    Schedule

    ...

    Make sure not to include empty sections. Now craft the prose. About the role paragraph: combine the initial description and role purpose into maybe two paragraphs but okay. Let's write:

    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.

    The Security specialist organization is a founding team: a lean group of Security Sales Specialists and Solutions Architects covering the highest-priority markets first, with more markets earning dedicated coverage over time. A team this size can't put a dedicated person in every territory on day one, and it can't afford every rep independently rebuilding enablement or waiting on operational support that doesn't exist yet. This role is both things a lean specialist team needs and doesn't yet have: the scale mechanism that generates coverage in markets without a dedicated rep, and the connective tissue that keeps a fast-growing, globally distributed team operating as one function instead of independent pods. You have two jobs that reinforce each other. First, you own