Director - Enterprise Sales

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. Need to parse the job posting. First, the intro: "When you join Verizon ..." is more about company culture. Could be "About the role"? Actually "About the role" maybe includes description of role. The posting includes description of responsibilities: "As part of Verizon Business, you will drive strategic revenue performance..." etc. So we can put that under Responsibilities. We need sections: About the role (maybe a brief overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive info, not invent. We need to remove boilerplate: EEO, etc. Also remove "Where you’ll be working" maybe part of Schedule? Actually schedule includes weekly hours 40. Also location info: mobile role, work from customer/field location(s), occasional visits to Verizon location. That's more about work location, not schedule. Could be part of "About the role" or maybe "Schedule". But schedule section only if posting actually states them. It says "Scheduled Weekly Hours 40". So we can include Schedule section with that. Pay: The posting includes salary ranges: $145,500 - $279,000, also location-specific ranges for Illinois and New York. So we can include Pay section with that info. Benefits: The posting includes a Benefits And Compensation paragraph describing benefits: health, dental, vision, etc., 401(k), holidays, personal days, parental leave, etc. So we include Benefits. Qualifications: The posting includes "What we’re looking for..." and "You’ll Need To Have" etc. That's qualifications. Also "Even better if you have one or more of the following:" which are preferred qualifications. So we can put under Qualifications (maybe separate Required and Preferred). But we need to follow instruction: Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. So we need to decide what goes where. We have responsibilities list: many bullet-like sentences but not explicitly bulleted. We can convert to

  • . The responsibilities include: Direct, develop, inspire... etc. Actually the responsibilities are listed after "Strategic Account Leadership:" etc. Those are bullet-like but each preceded by a bold heading. We can treat each as a list item. Requirements: The "You’ll Need To Have" list: Bachelor’s degree or four or more years of relevant work experience; Ten or more years of total professional experience, with demonstrated executive leadership experience...; Direct experience leading enterprise sales teams...; Demonstrated experience with consultative, outcomes-focused selling methodologies... That's required qualifications. Qualifications: Could be same as Requirements? Actually they said "What we’re looking for..." then "You’ll Need To Have..." then "Even better if you have one or more of the following:" So we could have Requirements (mandatory) and Qualifications (preferred). Or we could combine. But instruction: Use sections only when posting has real specific content. We have both. Skills: Could be derived from "Even better if you have..." includes advanced degree, proven track record, history of managing large strategic accounts, expertise across wireless/wireline, mastery in framing technology solutions, high proficiency in revenue forecasting, account planning, data-driven pipeline operations (preferably using Salesforce). Those are skills/qualifications. Could put under Skills. But we already have Qualifications for preferred. Might be redundant. Perhaps better: Requirements = mandatory; Qualifications = preferred; Skills = maybe not needed. However we need to decide. Let's map: - About the role: Could be the introductory paragraph about Verizon culture and the role's purpose: "When you join Verizon... As part of Verizon Business, you will drive strategic revenue performance..." Actually that's more responsibilities. Maybe About the role could be a short summary: "As part of Verizon Business, you will drive strategic revenue performance and lead a high-performing team of Senior Account Directors focused on protecting, growing, and acquiring our largest, most complex strategic enterprise accounts." That's from the posting. We'll put that as About the role. - Responsibilities: The detailed list of responsibilities: Strategic Account Leadership, Integrated Portfolio Execution, Pipeline & Revenue Execution, Executive Relationship & Outcome Alignment, Capability & Talent Development, Executive Sponsorship & Deal Strategy. We'll turn each into
  • . - Requirements: The "You’ll Need To Have" bullet points (4 items). We'll list as
    • . - Qualifications: The "Even better if you have one or more of the following:" list (7 items). We'll list as
      • . - Skills: Could be omitted if we think Qualifications covers. But we need to decide if we should include Skills section. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one section called Qualifications (or Requirements). But we already have Requirements separate. Could we have Qualifications include both required and preferred? But they said Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those headings possibly. But we should only include sections when posting has real specific content. So we need to see if we have content for each. We have content for About the role (yes). Responsibilities (yes). Requirements (yes). Qualifications (yes, the "even better" list). Skills: maybe we could extract skills from the responsibilities or qualifications, but we already have qualifications covering skills. Could we treat the "Even better if you have..." as Skills? Actually those are qualifications/skills. But we already have Qualifications section for those. So Skills might be redundant. However we could still include Skills if we can extract specific skill statements like "Mastery in framing technology solutions around measurable client business outcomes, business case development, and ROI metrics." etc. Those are skills. But they are already in the "even better" list. So we could put them under Skills and keep Qualifications for something else? But we don't have other qualifications besides the required ones. The required ones are more about experience/education. So we could treat Requirements as mandatory experience/education, Qualifications as preferred qualifications/skills, and Skills maybe not needed. But to follow the instruction of preferring few substantive sections, we could omit Skills and just have Requirements and Qualifications. However the instruction list includes Skills as an example heading, but not mandatory. So we can omit if no specific content. Benefits: we have content. Pay: we have content. Schedule: we have "Scheduled Weekly Hours 40". Also maybe location info? But schedule section only if posting actually states them. So we include Schedule with weekly hours 40. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

        About the role

        ...

        Responsibilities

        • ...
        ...

        Requirements

        • ...
        ...

        Qualifications

        • ...
        ...

        Benefits

        ...

        Pay

        ...

        Schedule

        Scheduled Weekly Hours 40

        We need to ensure we preserve all substantive info. Let's extract exact sentences. About the role: Could combine first two paragraphs: "When you join Verizon You want more out of a career. A place to share your ideas freely — even if they’re daring or different. Where the true you can learn, grow, and thrive. At Verizon, we power and empower how people live, work and play by connecting them to what brings them joy. We do what we love — driving innovation, creativity, and impact in the world. Our V Team is a community of people who anticipate, lead, and believe that listening is where learning begins. In crisis and in celebration, we come together — lifting our communities and building trust in how we show up, everywhere & always. Want in? Join the #VTeamLife. As part of Verizon Business, you will drive strategic revenue performance and lead a high-performing team of Senior Account Directors focused on protecting, growing, and acquiring our largest, most complex strategic enterprise accounts." We could keep that as prose. Responsibilities: The bullet points after that: "Strategic Account Leadership: Direct, develop, and inspire an elite enterprise account team to consistently protect existing revenue bases, expand share of wallet, and deliver outcomes-based growth in our highest-tier accounts.Integrated Portfolio Execution: Guide your team in crafting hybrid wireless and wireline solution architectures that deliver tangible, business-impact metrics (ROI, operational efficiency, digital transformation) for client organizations.Pipeline & Revenue Execution: Drive rigorous sales forecasting, establish strategic quotas, optimize resource allocation, and ensure pipeline health across complex, multi-year account strategies.Executive Relationship & Outcome Alignment: Coach team members on executive presence, C-suite relationship building, and framing technical capability around concrete business outcomes.Capability & Talent Development: Cultivate top sales talent through continuous skill building, targeted professional development, and strategic account planning frameworks.Executive Sponsorship & Deal Strategy: Act as an executive sponsor in critical client interactions—advising on custom enterprise architectures, leading key contract renewals and expansions, and ensuring long-term strategic alignment." We need to split into list items. Each bold heading plus description. We'll make each as
      • Strategic Account Leadership: Direct, develop, and inspire ...
      etc. But we should not add extra formatting beyond HTML? It's okay to include inside
      • . The instruction didn't forbid. We'll keep the content. Requirements: The "You’ll Need To Have" list: - Bachelor’s degree or four or more years of relevant work experience. - Ten or more years of total professional experience, with demonstrated executive leadership experience in enterprise technology sales or strategic account management (through commercial, military, or specialized training backgrounds). - Direct experience leading enterprise sales teams selling complex technical solutions (combining wireless, wireline, networking, cloud, or security) to large market accounts. - Demonstrated experience with consultative, outcomes-focused selling methodologies tailored to C-suite priorities. We'll list each as
      • . Qualifications (preferred): "Even better if you have one or more of the following:" list: - Advanced degree (MBA or relevant graduate degree). - Proven track record of personally engaging, building relationships, and closing multi-year agreements at the C-suite level. - History of successfully managing large strategic accounts—balancing revenue retention/protection with ambitious growth targets. - Expertise across both enterprise wireless (5G, private mobile networks, IoT) and wireline capabilities (SD-WAN, MPLS, fiber, unified communications, cybersecurity). - Mastery in framing technology solutions around measurable client business outcomes, business case development, and ROI metrics. - High proficiency in revenue forecasting, account planning methodology, and data-driven pipeline operations (preferably using Salesforce). We'll list each as
      • . Benefits: The paragraph under "Benefits And Compensation". Let's extract: "Our benefits are designed to help you move forward in your career, and in areas of your life outside of Verizon. From health and wellness benefit options including: medical, dental, vision, short and long term disability, basic life insurance, supplemental life insurance, AD&D insurance, identity theft protection, pet insurance and group home & auto insurance. We also offer a matched 401(k) savings plan, up to 8 company paid holidays per year and up to 6 personal days per year, paid parental leave, adoption assistance and tuition assistance, plus other incentives, we’ve got you covered with our award-winning total rewards package. Depending on the role, employees have the opportunity to receive compensation in the form