Account Executive - South West

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule only if present. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal opportunity, etc. Also remove navigation/cookie/legal etc. The posting includes "About NiCE" which is company description; maybe we can include as "About NiCE" but not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if content exists. We have content for About the role (the paragraph after "So, what’s the role all about?" maybe). Responsibilities: list under "Key Responsibilities". Requirements: maybe "Required Experience & Skills". Qualifications: maybe education? Skills: maybe list of skills. Benefits, Pay, Schedule: not present, so we should NOT include those sections. We must preserve all substantive info, not invent. Remove duplicated lines. Remove EEO boilerplate. Also remove "About NiCE" maybe not needed but could be considered "About the role"? Actually "About NiCE" is company description, not role. Could be omitted? The instruction: "Prefer a few substantive sections over many thin ones." We could include About NiCE as a paragraph under About the role? But we have a heading "About the role". The content after "So, what’s the role all about?" is a description of role. That fits About the role. Then we have Responsibilities, Required Experience & Skills (which could be Requirements and Skills). Education could be Qualifications. Let's parse. We need to extract: About the role: "This role is responsible for driving net-new business, pipeline growth, and revenue within 911 Emergency Communications Centers and broader Public Safety agencies across a seven-state territory. The Account Executive will own the full sales cycle while acting as a trusted, consultative partner—positioning NiCE’s Public Safety solution portfolio through direct selling, partner collaboration, and solution expertise. Success in this role requires balancing high-activity territory execution with deep understanding of Public Safety workflows, including 911 and Criminal Justice digital evidence processes, to win complex public-sector opportunities." That's the paragraph after "So, what’s the role all about?" We'll put that in

. Responsibilities: list under "Key Responsibilities". There are bullet points grouped under headings: Sales & Territory Execution, Public Safety & Customer Engagement, Solution & Technical Collaboration, Partner & Internal Collaboration. Each has multiple bullet points. We need to output a

• for any list of duties/requirements/benefits. So we can combine all responsibilities into a single list? Or we could keep subheadings? The instruction only says use

  for section headings,

  • for any list,

    for prose. It doesn't forbid additional headings inside sections, but we should follow the given headings. Probably we can just make a single

    with all responsibility items. Let's extract each bullet: Sales & Territory Execution: - Build and execute a strategic territory plan to drive meeting creation, pipeline growth, and revenue. - Conduct consistent outbound prospecting and account-based outreach to generate first meetings and new opportunities. - Manage the full sales cycle, including discovery, solution positioning, procurement navigation, and deal close. - Deliver accurate weekly reporting on activity, pipeline creation, and forecasting. - Achieve quarterly and annual pipeline and revenue targets. Public Safety & Customer Engagement: - Develop strong relationships with 911 directors, supervisors, procurement teams, IT leadership, and executive stakeholders. - Interview and engage multiple user groups within Public Safety agencies to understand operational workflows and challenges. - Maintain and grow existing customer relationships to maximize long-term revenue and generate referral opportunities. - Operate with a mission-driven mindset focused on improving staff well-being and operational performance within 911 centers. Solution & Technical Collaboration: - Act as a solution expert, demonstrating NiCE capabilities and articulating differentiated value versus competitors. - Conduct needs assessments and solution alignment in collaboration with Presales/Solutions Engineering. - Support technical responses to RFPs, RFIs, and bids, including development of Scopes of Work (SOWs). - Collect customer feedback on solution requirements and interface with Product Management on market needs and trends. - Develop and deliver compelling presentations to end users, partners, consultants, and executive decision-makers. Partner & Internal Collaboration: - Manage and co-sell with reseller and channel partners to expand territory coverage and accelerate opportunities. - Collaborate cross-functionally with Marketing, Product Management, Business Development, Project Management, Legal, Professional Services, and Customer Support. - Participate in marketing campaigns, demos, and demand-generation initiatives. Requirements: maybe "Required Experience & Skills" includes experience requirements. We'll treat that as Requirements. Also there is "Education BA/BS..." which could be Qualifications. Let's extract Required Experience & Skills bullet list: - 3–5+ years of technology sales and/or sales engineering experience within Public Safety, 911/PSAP, or Government sectors. - Strong understanding of Public Safety and Criminal Justice workflows, including digital evidence processes. - Proven success generating pipeline and closing deals in complex public-sector procurement environments. - Experience working with government purchasing personnel, RFPs, bids, and state/federal contracts. - Consultative selling approach with strong discovery, demonstration, and presentation skills. - High-activity, disciplined sales execution with exceptional work ethic. - Strong communication, technical aptitude, and creative problem-solving skills. - Ability to influence senior decision-makers and build trust across multiple stakeholder groups. Education: "BA/BS in Computer Science, Information Systems, or a related field (or equivalent experience)." That's Qualifications. Skills: maybe we could separate skills from requirements, but we already have many skill-like items in Required Experience & Skills. Could create a Skills section listing soft/technical skills: Strong communication, technical aptitude, creative problem-solving, consultative selling, discovery, demonstration, presentation, ability to influence, etc. But we might duplicate. Better to treat Required Experience & Skills as Requirements, and Education as Qualifications. Skills maybe not needed separately; we could omit Skills section if no distinct skills list beyond those already captured. But we could still create a Skills section pulling out skill items: "Strong communication, technical aptitude, and creative problem-solving skills. Consultative selling approach with strong discovery, demonstration, and presentation skills. Ability to influence senior decision-makers and build trust across multiple stakeholder groups." However that would duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Skills into one section? But headings list includes both Requirements and Skills; we could include both if we have content. We have content for Requirements (experience, understanding, proven success, experience with govt purchasing, consultative selling, high-activity execution, communication/technical aptitude/problem-solving, ability to influence). For Skills we could list: "Strong communication, technical aptitude, creative problem-solving, consultative selling, discovery, demonstration, presentation, influencing senior decision-makers, building trust." That's essentially same as above. Might be redundant. Given the instruction to preserve all substantive information, we need to not lose any detail. If we put all those bullet points under Requirements, we keep all details. Then we could omit Skills section (since no extra distinct skills). That's acceptable: we only include sections when posting has real, specific content for it. If we don't have distinct skills beyond those already captured, we could omit Skills. But we might still include Skills with same list? That would be duplicative. Better to omit Skills. Qualifications: Education BA/BS... We'll put that. Benefits, Pay, Schedule: not present, omit. Also we have a brief intro about NiCE's mission etc. That could be considered "About the role"? Already we used that for role description. The "About NiCE" paragraph is company description; could be omitted as not required heading. But we could include as a short paragraph under About the role? Might be considered extra but not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description too. Where to put it? Could be a separate section like "About NiCE" but not in allowed headings. However we could incorporate it into About the role as extra paragraph? Might be okay but it's not about the role. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It didn't say we cannot have other headings, but we should follow the pattern. Safer to include only those headings if we have content. The company description is substantive; we could put it under About the role as an additional paragraph before role specifics. That would preserve it. Let's do that: About the role section includes two paragraphs: first about NiCE company (maybe summarizing), second about role specifics. But the company description includes EEO statement at end which we must remove. So we need to strip that. Company description paragraph: "NICE Ltd. (NASDAQ: NICE) software products are used by 25,000+ global businesses, including 85 of the Fortune 100 corporations, to deliver extraordinary customer experiences, fight financial crime and ensure public safety. Every day, NiCE software manages more than 120 million customer interactions and monitors 3+ billion financial transactions. Known as an innovation powerhouse that excels in AI, cloud and digital, NiCE is consistently recognized as the market leader in its domains, with over 8,500 employees across 30+ countries." We must remove the EEO line: "NiCE is proud to be an equal opportunity employer..." etc. Thus About the role section will have that paragraph then the role description paragraph. Now Responsibilities section:

    with all bullets. Requirements section:
    with the experience bullets. Qualifications section:

    with education line. We must not include any boilerplate like "About NiCE" heading; we just have About the role. Check for duplicated lines: Ensure we didn't repeat any. Now produce HTML fragment. Let's craft.

    About the role

    NICE Ltd. (NASDAQ: NICE) software products are used by 25,000+ global businesses, including 85 of the Fortune 100 corporations, to deliver extraordinary customer experiences, fight financial crime and ensure public safety. Every day, NiCE software manages more than 120 million customer interactions and monitors 3+ billion financial transactions. Known as an innovation powerhouse that excels in AI, cloud and digital, NiCE is consistently recognized as the market leader in its domains, with over 8,500 employees across 30+ countries.

    This role is responsible for driving net-new business, pipeline growth, and revenue within 911 Emergency Communications Centers and broader Public Safety agencies across a seven-state territory. The Account Executive will own the full sales cycle while acting as a trusted, consultative partner—positioning NiCE’s Public Safety solution portfolio through direct selling, partner collaboration, and solution expertise. Success in this role requires balancing high-activity territory execution with deep understanding of Public Safety workflows, including 911 and Criminal Justice digital evidence processes, to win complex public-sector opportunities.

    Responsibilities

    • Build and execute a strategic territory plan to drive meeting creation, pipeline growth, and revenue.
    • Conduct consistent outbound prospecting and account-based outreach to generate first meetings and new opportunities.
    • Manage the full sales cycle, including discovery, solution positioning, procurement navigation, and deal close.
    • Deliver accurate weekly reporting on activity, pipeline creation, and forecasting.
    • Achieve quarterly