Director, Strategic Sales - West

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "Role Overview" which is like about the role. Also "Key Responsibilities", "Requirements Qualifications" (maybe separate Requirements and Qualifications?), "Benefits". Also maybe "What Success Looks Like"? Could be considered part of overview but we can include as separate section? The instruction: Use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need to decide which sections have content. We have: - Role Overview: content present (description). So we can have

About the role

with paragraphs. - Key Responsibilities: content present (list). So

Responsibilities

with

• . - Requirements Qualifications: The posting has "Requirements Qualifications" heading then bullet list of qualifications. Could split into Requirements and Qualifications? The content includes both required qualifications and nice-to-have. Could treat as Requirements section (required) and maybe Skills? But we have no separate Skills section. Could combine into Requirements. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have Requirements and Qualifications separate if content distinguishes. The posting has "Requirements Qualifications" then bullet list of required qualifications, then "Nice to Have" list. So we could have

  Requirements

  for required qualifications, and

  Qualifications

  for nice-to-have? Or maybe Qualifications is for nice-to-have. We'll follow that. - Benefits: content present (Remote/flexible work model, Medical/Dental/Vision, 401(k), Unlimited PTO). So

  Benefits

  with list. - Pay and Schedule: not mentioned, so omit. - About the role: we have overview. - Possibly "What Success Looks Like" could be considered part of overview or separate but not in list of headings; we could incorporate into About the role. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as paragraphs/lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting doesn't seem to have those except maybe at end? Not present. We need to output only HTML fragment. Let's extract content. Role Overview paragraph(s): "1Kosmos is seeking a Strategic Sales Director – West to lead and accelerate commercial growth across a defined set of target verticals and the broader Western United States. This is a senior individual contributor and market development role for someone who can carry a complex, six- and seven-figure enterprise sales cycle from first conversation to signed contract, and who can operate credibly with CISO, CIO, and procurement stakeholders across industries where identity fraud and credential-based breaches carry direct financial and operational risk. 1Kosmos has built significant momentum across identity verification and passwordless authentication. On the identity verification side, deployments span patient and customer onboarding, account recovery, and step-up verification for high-risk transactions. On the authentication side, the platform delivers passwordless access for enterprise workforce users and shared/frontline workstations alike, using facial biometrics, FIDO2 hardware keys, and passkeys. This combination, verified identity carried into reusable, passwordless authentication, sits on top of a customer's existing identity infrastructure rather than replacing it. 1Kosmos was named a Leader in the 2026 Gartner Magic Quadrant for Identity Verification, holding the highest product score for workforce use cases for the second consecutive year, and is recognized as a leader in passwordless authentication for the enterprise by KuppingerCole. The platform holds a differentiated compliance profile, including NIST 800-63-3 certification at AAL2 and IAL2 (with an IAL3 step-up option), FedRAMP High authorization, Department of Defense IL4, and Kantara certification as a full Credential Service Provider, one of a small number of vendors globally at that level. This role will own go-to-market strategy and execution across 1-2 assigned target verticals plus the Western U.S. territory for opportunities outside the company's target vertical set, driving pipeline from initial engagement through close and working cross-functionally with Solutions Engineering, Product, Marketing, and Customer Success to deliver outcomes for enterprise customers." That's the overview. Key Responsibilities: there are subheadings: Territory and Market Development, Sales Execution and Deal Management, Customer and Stakeholder Engagement, Cross-Functional Collaboration, Reporting and Forecast Management. Each with bullet points. We need to output a
  • for any list of duties/requirements/benefits. So we can flatten all responsibilities into a list? Or we could keep subheadings as

    ? But instruction only mentions using h3 for section headings; we could still use

    for subheadings inside responsibilities? Not prohibited but maybe better to keep simple: just a list of responsibilities. However we need to preserve ALL substantive information; if we collapse subheadings we lose structure but still preserve the bullet points content. The instruction didn't forbid adding extra headings like h4, but said use h3 for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot use other headings. Safer to keep responsibilities as a list without subheadings; we can still include the substance. Let's extract each bullet: Territory and Market Development: - Own a combination territory: 1-2 assigned target verticals (drawn from Manufacturing, Financial Services, Retail, BPO, Distribution & Supply Chain, and Travel & Entertainment) plus the Western United States geography for opportunities outside the company-wide target vertical set. - Build and execute a territory plan that prioritizes account targeting, whitespace mapping, and partner coverage across the assigned verticals and geography. - Generate pipeline through direct outreach, partner co-sell motions, industry events, and referral networks across CISO, CIO, VP of Identity, and IT leadership audiences. - Develop and maintain a qualified pipeline sufficient to support consistent quarterly and annual revenue targets. - Identify and pursue whitespace opportunities across the full 1Kosmos use case portfolio, including identity verification (onboarding, account recovery, step-up authentication) and passwordless authentication (enterprise and shared/frontline workstation). Sales Execution and Deal Management: - Own the full sales cycle from discovery through contract execution on net-new and expansion opportunities. - Lead executive-level engagement with CISO, CIO, VP of Identity, Security, and Procurement stakeholders. - Articulate 1Kosmos' differentiated value across identity verification and passwordless authentication, connecting both to the specific fraud, compliance, and operational risks relevant to each account's industry. - Navigate complex, multi-stakeholder deal cycles including security reviews, legal, procurement, and compliance approvals common to enterprise purchasing environments. - Work with channel partners including Optiv, VARs, and GSIs on partner-assisted and partner-sourced deals. Customer and Stakeholder Engagement: - Act as the primary executive sponsor and relationship owner for strategic accounts throughout the sales cycle. - Translate identity security requirements into business outcomes, including reduced help desk volume, fraud loss prevention, and reduced risk of credential-based breaches. - Partner with Solutions Engineering on proof-of-concept design and execution, ensuring technical validation aligns with customer requirements. - Coordinate with Customer Success post-sale to support smooth onboarding and expansion planning. Cross-Functional Collaboration: - Work closely with the SVP of Americas Sales on territory planning, forecast accuracy, and executive account strategy. - Partner with Marketing on vertical-specific campaigns, event strategy, and collateral including case studies, use case briefs, and competitive positioning. - Provide structured feedback to Product on vertical-specific requirements, integration depth, and use case gaps. - Collaborate with the Partnerships team to activate and co-sell with systems integrators and technology alliance partners active in the assigned verticals and territory. Reporting and Forecast Management: - Maintain accurate pipeline, opportunity, and forecast data in CRM. - Provide regular updates to the SVP of Americas Sales on progress, risks, blockers, and competitive intelligence. - Track and report on key performance metrics including pipeline coverage, win rates, average contract value, and time to close. Now Requirements Qualifications: Required qualifications (under Requirements Qualifications): - 10 or more years of enterprise software sales experience, with a demonstrated track record of closing six- and seven-figure SaaS or software deals. - Experience owning a combination territory (named verticals plus a broader geography) and prioritizing effectively across both. - Deep familiarity with enterprise purchasing environments including CISO, CIO, Procurement, and Legal stakeholders, and typical 6- to 18-month enterprise deal cycles. - Prior experience selling into one or more of the following verticals strongly preferred: Manufacturing, Financial Services, Retail, BPO, Distribution & Supply Chain, or Travel & Entertainment. - Comfort operating in a high-growth, fast-moving environment with evolving processes and significant individual ownership. - Excellent communication and executive presence; able to operate credibly at the C-suite level. - Based in or able to travel regularly across the Western United States. Nice to Have: - Experience with identity, access management, digital identity, or cybersecurity platforms. - Prior sales experience at or against vendors such as Okta, Ping Identity, Microsoft, SailPoint, Saviynt, or CyberArk. - Existing relationships with CISO, CIO, or VP of Identity leaders within the assigned target verticals. - Background in channel or partner-assisted selling through resellers, systems integrators, or GSIs. Benefits: - Remote / flexible work model - Medical / Dental / Vision - 401(k) - Unlimited PTO Also there is a paragraph "Why 1Kosmos" before Benefits describing company. That could be part of About the role or maybe a separate section like "About the company". Not in allowed headings but we could incorporate into About the role. The instruction: Use h3 for section headings (e.g. About the role, Responsibilities...). It didn't forbid other headings but we should stick to those. We can include the "Why 1Kosmos" paragraph as part of About the role (maybe after overview). That preserves info. Now we need to output HTML fragment: sections with h3 and content. Structure:

    About the role

    ... overview paragraph(s) ... plus maybe the "Why 1Kosmos" paragraph.

    Responsibilities

    • ... each bullet ...

    Requirements

    • ... required qualifications ...

    Qualifications

    • ... nice-to-have ...

    Benefits

    • ... benefits ...
    We must not include Pay or Schedule. Check that we haven't omitted any substantive info: The overview includes details about product, certifications, etc. We included that. The "What Success Looks Like" section not included; we could incorporate into About the role as a paragraph. Let's add that after overview. "What Success Looks Like" content: - A qualified pipeline of opportunities across the assigned target verticals and Western U.S. territory is built and maintained with strong coverage ratios. - Net-new enterprise logos are closed on a consistent quarterly cadence. - 1Kosmos is recognized as a credible, differentiated vendor for identity verification and passwordless authentication within the assigned verticals. - Relationships with key CISO, CIO, and VP of Identity stakeholders are established and active across the territory. - Vertical-specific use case narratives, case studies, and reference customers are developed in partnership with Marketing. We can add as paragraph(s