HCLS Principal Account Executive, US HCLS Payors , Global HCLS

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. The posting includes description, responsibilities, basic qualifications, preferred qualifications, benefits, pay range, schedule? Travel up to 40% mentioned. That's schedule? Travel is not schedule but could be part of schedule? Probably schedule not given. Benefits: they list comprehensive benefits. Pay: base salary range given. So include sections: About the role (maybe from description), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Skills (maybe combine?), Benefits, Pay. Schedule not present (no specific schedule like full-time, part-time). Travel up to 40% could be considered schedule? But schedule usually refers to work hours, remote, etc. Not given. So omit Schedule. We must not repeat job title as heading. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO, accommodation links, etc. Also remove duplicated lines (like "Serve as the single-threaded leader accountable for revenue, consumption growth, and customer satisfaction across the full account portfolio." appears twice; we should keep only once? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines are duplicated content; we should not repeat them? It says remove duplicated lines. So we should deduplicate. We need to extract sections. Let's parse the posting. Description: first paragraph about AWS seeking Principal Account Executive, role description. Then "Key job responsibilities" with subheadings: Account Team Leadership, Strategic Account Management, Cross-Functional Orchestration, Travel up to 40%..., A day in the life, About The Team, Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. But many of those are fluff; we need to keep substantive info. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Also "Prefer a few substantive sections over many thin ones." So we may combine some. We need sections: About the role (maybe from first paragraph and "About The Team" etc). Responsibilities (list of duties). Requirements (basic qualifications). Qualifications (preferred qualifications). Skills (maybe combine some skill statements). Benefits (list of benefits). Pay (salary range). Schedule (none). We'll omit Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract substantive content. First paragraph: "Amazon Web Services (AWS) is seeking an experienced Principal Account Executive to lead the strategic relationship with one of the world's largest managed care and health services enterprises. This is not a standard individual contributor role — it is an account team leadership position accountable for orchestrating a multi-AE pod, driving executive-level engagement across the C-suite, and building a multi-year transformation roadmap spanning cloud migration, data modernization, and AI/ML adoption. The Account Lead serves as the single-threaded owner for one of AWS's largest and most strategic Payor relationships. You will lead, mentor, and coordinate a team of account executives and cross-functional specialists, ensuring unified execution across the customer's business units. The ideal candidate combines deep healthcare industry knowledge with complex enterprise sales leadership, a track record of managing large-scale revenue relationships, and the ability to develop and retain top talent on a high-performing account team." That's About the role. Next: "Key job responsibilities" with subsections. Account Team Leadership: - Lead and develop a pod of 2-3 account executives covering multiple business units within a large managed care enterprise. - Set priorities, remove blockers, and ensure consistent execution across the team. - Serve as the single-threaded leader accountable for revenue, consumption growth, and customer satisfaction across the full UHG portfolio. - Establish team operating rhythm: pipeline reviews, deal strategy sessions, forecast calls, and weekly syncs to maintain accountability and momentum. - Coach and mentor AEs on executive engagement, deal strategy, and career development. - Build a succession-ready team. - Serve as the single-threaded leader accountable for revenue, consumption growth, and customer satisfaction across the full account portfolio. (duplicate of earlier line; we should deduplicate; keep one.) Strategic Account Management: - Develop and execute a comprehensive account plan that aligns AWS capabilities to the customer's strategic priorities including claims modernization, member experience, provider engagement, and population health analytics. - Build and maintain executive relationships at the CIO, CTO, CDO, CISO, and business unit president level. - Establish regular cadence of strategic business reviews and innovation sessions. - Own the strategic commercial relationship end-to-end: ramp compliance, consumption tracking, renewal strategy, and executive governance. - Identify and qualify large-scale transformation opportunities ($10M+) across infrastructure modernization, data lake/analytics, AI/ML, and generative AI use cases. Cross-Functional Orchestration: - Orchestrate cross-functional AWS teams (Solutions Architects, Specialist Sales, Professional Services, Partners, Support) to deliver against customer outcomes and drive workload migration. - Navigate complex procurement environments including Enterprise Agreements, Private Pricing commitments, and multi-year strategic opportunities. - Own forecasting accuracy and pipeline hygiene across the team. - Partner with the customer to define cloud governance, security, and compliance frameworks aligned to HIPAA, HITRUST, and state regulatory requirements. - Represent the voice of the customer back into AWS Product and Engineering teams through PFRs and executive escalation paths. - Travel up to 40% to customer sites (Minneapolis metro area) and AWS events as needed. "A day in the life" is narrative; could be omitted as not a list; but we could incorporate into About the role? Probably not needed. "About The Team": description of Payor subsegment; could be part of About the role. "Diverse Experiences": encouragement to apply; could be omitted as boilerplate? It's not EEO but still generic; maybe we can keep as part of About the role? It's not substantive detail about role; maybe omit. "Why AWS?" etc are generic; could be omitted. "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance": generic benefits; but we have Benefits section later; we could incorporate some of those into Benefits? However the Benefits section later lists specific benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. The generic culture statements are boilerplate; we can omit. Now Basic Qualifications list: - 7+ years of enterprise technology sales or strategic account management experience, with at least 3 years managing complex, multi-stakeholder accounts with annual revenue exceeding $20M. - 5+ years of experience selling into the healthcare, health insurance, or managed care industry with demonstrated knowledge of Payor business models, regulatory landscape, and technology priorities. - Demonstrated experience leading, coaching, or coordinating a team of account executives or sales professionals in a matrixed environment — formal management experience or pod/team lead accountability. - Proven track record of building and maintaining C-level relationships (CIO, CTO, CDO, CFO) and influencing enterprise technology strategy at Fortune 500 organizations. - Experience leading complex, multi-year enterprise agreements and consumption-based commercial models. - Demonstrated ability to develop and execute strategic account plans that drive year-over-year revenue growth. - Experience orchestrating cross-functional teams (Technical, Sales Specialists, Professional Services, Partners) to deliver customer outcomes. - Bachelor's degree or equivalent professional experience. Preferred Qualifications: - 10+ years of Healthcare account experience with progressively increasing scope and team responsibility. - Direct experience with large, diversified managed care organizations and their technology organizations. - Track record of developing and retaining high-performing sales talent — mentoring AEs, running pipeline reviews, and driving team accountability. - Experience positioning cloud-native architectures, data platforms, and AI/ML solutions to address healthcare Payor challenges (care management, utilization management, network optimization, member engagement). - Knowledge of healthcare compliance and security frameworks including HIPAA, HITRUST, SOC 2, and FedRAMP (for government programs). - Experience with Private Pricing programs, committed spend agreements, and multi-year cloud financial planning. - Track record of landing and expanding AI and advanced analytics initiatives within large healthcare enterprises. - Experience navigating M&A-driven IT integration scenarios and positioning cloud as an accelerant for post-merger technology consolidation. - Strong operational rigor: pipeline management, forecasting accuracy, CRM discipline, and written communication skills aligned to a high-accountability sales culture. Benefits: after "The base salary range for this position is listed below. Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives. Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits." Pay: "USA, MN, Minneapolis - 170,000.00 - 230,000.00 USD annually" Thus we have Pay. Now we need to output HTML fragment with sections. We'll create:

  About the role

  ... (combined description)

  Responsibilities

  • ... list items (deduplicated)

  Requirements

  • ... basic qualifications

  Qualifications

  • ... preferred qualifications

  Skills

  Maybe we can combine some skill statements from preferred qualifications like "Strong operational rigor: pipeline management, forecasting accuracy, CRM discipline, and written communication skills". But we already have those in qualifications. Could create Skills section with those skill items. However we might avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." Could combine Skills into Qualifications? But they asked to use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include Skills if there is content. We can extract skill statements from responsibilities or qualifications that are skill-based. For example: "Coach and mentor AEs on executive engagement, deal strategy, and career development." That's a skill. "Build and maintain executive relationships at the CIO, CTO, CDO, CISO, and business unit president level." That's a skill. "Experience positioning cloud-native architectures, data platforms, and AI/ML solutions..." etc. Could list them. But we must not invent or summarize away detail. We can list skill statements as
• items. We need to ensure we don't duplicate content already in Requirements or Qualifications. But it's okay if some overlap? Might be considered duplication. Better to extract distinct skill statements not already captured as qualifications. However the qualifications already include many skill-like items. To avoid thin sections, maybe we can omit Skills section if no distinct skill content beyond what's already in Requirements/Qualifications. But the instruction says to include a section ONLY when the posting has real, specific content for it. If we consider that the posting does not have a separate "Skills" section distinct from qualifications, we could omit Skills. However they listed Skills as a possible heading; we can omit if no specific content. Let's see if there are explicit skill statements not covered: "Strong operational rigor: pipeline management, forecasting accuracy, CRM discipline, and written communication skills" is a skill but also appears in preferred qualifications. Could be considered part of Qualifications. So we could omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits,