Principal Account Executive - Healthcare Enterprise

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat no job title heading. Remove boilerplate like EEO, etc. Also remove application instructions (none). Need to preserve all substantive info. We need to parse description: It includes description paragraphs, then "WhatYouWillDo:" list of responsibilities. Then "What We ExpectofYou" list of requirements/qualifications. Then "Pay range: $ 69,000 - $94,000, depending on experience and skill set Annual bonus target of 300% subject to terms and conditions of plan Benefits overview: https://cdw.benefit-info.com/ Salary ranges may be subject to geographic differentials". Then some AI-fluent organization statements (maybe part of About Us). Then "About Us" paragraph. Then EEO boilerplate (remove). Also "We’re looking for people..." etc. We need sections: About the role (maybe from description paragraph before WhatYouWillDo). Responsibilities (WhatYouWillDo list). Requirements (maybe from "What We ExpectofYou" includes experience, degree, etc). Qualifications (maybe overlapping; but we can combine? The instruction says use headings for those categories if content exists. We have both Requirements and Qualifications; we could treat "What We ExpectofYou" as Requirements (experience, degree, skills). Qualifications maybe not separate; but we could still include if there is content like "Proven sales expertise..." etc. Might be considered Skills. Let's map: - About the role: initial paragraph(s) describing role: "The Principal Account Executive (PAE)will overseelarge, strategic enterpriseand majoraccounts,driving high-value solutions and services across the organization. The Principal Account Executive is expected to be a subject matter expert,leveragingdeep technical knowledge and business acumen to designand executecomprehensive solutions for complex customer needs. Recognized asapeermentor to junior talent andnewCoworkers. This role involves working closely with senior leadership both within CDW and with client organizations to shape long-term strategies and ensure consistent, high-impact growth.Leveraging advanced technical fluency, market insight, and executive-level relationship managementtoidentifyunderserved customers and deliver transformative business outcomes." We can clean up spacing. - Responsibilities: list items from "WhatYouWillDo:" each sentence maybe separate bullet. Need to extract each duty. Let's list them: 1. Navigate highly complex, multi-location enterprise deals, aligning stakeholders with divergent objectives toward a unified vision and solution strategy. 2. Articulate CDW’s full technology ecosystem and services portfolio with confidence, adapting messaging to influence C-level buyers and IT decision-makers. 3. Maximize sales efficiency through mastery of CDW’s suite of selling tools and platforms, optimizing pipeline velocity and minimizing administrative overhead. 4. Translate executive-level strategic objectives into executable programs that measurably improve seller effectiveness and account performance. 5. Partner with Sales leadership to identify high-potential initiatives, define KPIs, and align programs with broader go-to-market strategy. 6. Analyze program data, customer insights, and seller feedback to refine go-to-market approaches, enhance engagement, and accelerate adoption. 7. Design and sustain a scalable enablement framework that supports continuous learning, strategic upskilling, and onboarding for new and tenured sellers alike. 8. Lead cross-functional collaboration across Sales, Marketing, Solutions Architects, Digital, and Operations teams to execute growth plans. 9. Influence senior leadership and client executives through data-driven insights, contributing to strategic account planning and enterprise-level forecasting. 10. Consistently achieves or exceeds 100% to goal through a blend of new books acquisition, upsells, and retention across the largest and most strategic accounts. 11. Supports the development and execution of account prioritization framework, incorporating customer lifecycle stage, relationship maturity, competitive positioning, whitespace opportunity, and long-term revenue potential. 12. Balances between short-term wins and multi-year growth strategies across assigned accounts. 13. Creates and implements comprehensive account strategies, articulating a long-term vision for success, defining measurable business outcomes, and designing contingency pathways. 14. Aligns internal and external stakeholders to shared goals while continuously identifying expansion opportunities. 15. Expertly navigates complex buying cycles, understanding internal client constraints and timing, mapping influence chains, and ensuring forward movement across decision stages. 16. Enables the client to maintain momentum while minimizing friction in the procurement process. 17. Builds lasting client partnerships through credibility and consultative engagement. 18. Establishes shared success criteria, communicates value realization, and continuously aligns offerings to evolving business priorities and establishes clear impact measurement metrics. 19. Leads advanced stakeholder management by conducting multidimensional stakeholder mapping, customizing value propositions, managing conflicting interests, and co-creating solutions that reflect both business objectives and personal motivations. That's many. - Requirements: from "What We ExpectofYou": list: - A minimum of ten (10) years of direct selling experience in a high-tech, customer-facing sales environment. - Bachelor’s degree in a STEM-related field, Business Administration, or equivalent practical experience. - In-depth understanding of key technologies, including but not limited to Cisco, Microsoft, IBM, EMC, and HP, as well as competitive equivalents. - Exceptional verbal and written communication skills, with the ability to engage effectively with stakeholders at all levels. - Proven sales expertise, with a demonstrated ability to meet targets and inspire enthusiasm in the sales process. - Strong strategic planning, time management, and organizational skills, with a keen attention to detail. - Qualifications: maybe not separate; but we could treat the above as Requirements and Qualifications maybe same. However we need to decide if we should output both headings if content exists. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can include those headings if there is content. We have content for Requirements (the list). For Qualifications maybe we could include things like "Proven sales expertise..." but that's already in Requirements. Could also include "In-depth understanding of key technologies" as Qualifications. But to avoid duplication, maybe we put Requirements as the list of experience/degree, and Qualifications as the list of skills/knowledge. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But they ask to use those headings if content exists. We could have Requirements (experience/degree) and Qualifications (skills/technologies). Let's split: Requirements: - Minimum 10 years direct selling experience in high-tech customer-facing sales. - Bachelor’s degree in STEM-related field, Business Administration, or equivalent practical experience. Qualifications: - In-depth understanding of key technologies (Cisco, Microsoft, IBM, EMC, HP, competitive equivalents). - Exceptional verbal and written communication skills. - Proven sales expertise, ability to meet targets and inspire enthusiasm. - Strong strategic planning, time management, organizational skills, keen attention to detail. That seems reasonable. Skills: maybe we could extract any explicit skills list; but we already covered communication, strategic planning, etc. Could treat Skills as same as Qualifications? But we already used Qualifications for those. Might be redundant. Better to not include Skills if no distinct content beyond what we already placed. However we have "Exceptional verbal and written communication skills" etc. That's a skill. Could put under Skills. But we already used Qualifications for technical knowledge. Let's decide: We'll have Requirements (experience, degree), Qualifications (technical understanding), Skills (communication, sales expertise, planning). That yields three sections. Benefits: we have "Benefits overview: https://cdw.benefit-info.com/" plus maybe mention of annual bonus target 300% subject to terms. That's a benefit? Bonus is compensation. Benefits overview link. We'll include Benefits section with that link and mention of annual bonus target? The bonus is compensation, but could be under Benefits. We'll include: Annual bonus target of 300% subject to terms and conditions of plan. Benefits overview: https://cdw.benefit-info.com/ Pay: we have Pay range: $69,000 - $94,000, depending on experience and skill set. Salary ranges may be subject to geographic differentials. Also mention AI-fluent organization statements maybe not pay. So Pay section includes that. Schedule: no info about schedule (full-time, etc). Not present, so omit. About Us: we have a paragraph about CDW. That could be "About the role"? Actually we already have About the role from description. There's also "About Us" paragraph describing CDW. Could be a section "About Us" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About Us. So we should not create About Us heading. Instead we could incorporate that info into About the role? But About the role already describes role; About Us is company description. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, etc). It doesn't forbid other headings? 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 not add About Us. We could incorporate CDW description into About the role? Might be okay but risk of misrepresenting. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Us paragraph somewhere. If we cannot create a heading for it, we could put it as a

without a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but they gave examples. Safer to include About Us as a

without heading? But they said use

for section headings (e.g. About the role, Responsibilities...). It implies we should use h3 for those headings if we have them. For other content we can just use

. So we can put About Us paragraph as a

after the sections, without heading. That preserves info. Similarly, the AI-fluent organization statements and "We’re looking for people..." etc are also substantive; we need to preserve them. Where to put? Could be part of About Us or separate

. We'll include them as

after About Us. We must remove boilerplate: EEO, equal opportunity, etc. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation/legal etc. Now craft HTML. Structure:

About the role

... (cleaned description)

Responsibilities

• ... each bullet
...

Requirements

• ... 10 years experience
• ... Bachelor’s degree...

Qualifications

• ... In-depth understanding of key technologies...
• ... Exceptional verbal and written communication skills...
• ... Proven sales expertise...
• ... Strong strategic planning, time management, organizational skills...

Maybe Skills not needed; but we already put communication etc under Qualifications. Could rename Qualifications to Skills? But we need both headings if content. Let's keep Qualifications as technical knowledge, and Skills as interpersonal/planning. Actually we already put communication under Qualifications; maybe better to move communication to Skills. Let's restructure: Requirements: experience, degree. Qualifications: technical understanding (Cisco etc). Skills: communication, sales expertise, strategic planning, etc. Thus:

Qualifications