Sr. Manager, Healthcare Providers West , Healthcare Providers West

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Key parts: - Description: Application deadline: Sep 29, 2026 (metadata, maybe include in a short p). Not a heading. - "This is not an individual contributor sales role. You will lead a team of enterprise Account Executives (sellers) who own named healthcare providers, academic medical centers, and integrated delivery networks across the Western United States. You'll be responsible for setting the strategic direction, coaching sellers through complex deal cycles, and ensuring your team consistently delivers against quarterly and annual revenue targets. You will own key relationships at our top customers and connect the dots between a health system's biggest challenges and AWS's broadest set of cloud, AI, and purpose-built healthcare capabilities. Healthcare Providers are navigating an unprecedented environment: margin compression, workforce shortages, regulatory complexity, and rapidly rising patient expectations. At the same time, AI is moving from pilot to production across clinical documentation, operational automation, clinical decision support, and patient engagement. AWS is uniquely positioned with purpose-built services like Amazon Connect Health, Amazon HealthLake, and Amazon Bedrock to help health systems modernize and innovate at the pace their patients and clinicians demand. You'll build and lead a team that serves as the tip of the spear for that transformation across the West region." That's about the role. Then "Key job responsibilities" repeated: "Key Job Responsibilities". Then bullet list of responsibilities. We need to extract responsibilities as list items. Responsibilities list: - Lead, develop, and scale a team of enterprise Account Executives - Recruit, hire, coach, and retain top sales talent. Set clear expectations, provide ongoing deal coaching, and create a high-performance culture that balances accountability with career development. Coach your team on provider industry challenges and how to address them in support of meeting your customer objectives. - Set and execute the regional go-to-market strategy - Define regional approach, structure territory plans, account segmentation, and opportunity prioritization across AI/Agentic AI, cloud migration, application modernization, data & analytics, and operational efficiency for West region health systems. Translate org-level sales plays into actionable plans your team can execute. - Drive revenue attainment and pipeline discipline – Own and drive the West region number. Ensure accurate forecasting, pipeline coverage, SFDC hygiene, stage progression, and early risk identification across your team's book of business. Deliver against quarterly and annual revenue targets consistently. - Build and maintain healthcare executive customer relationships - Serve as a trusted senior advisor to CIOs, CMIOs, CDOs, CFOs, and COOs at your region's most strategic accounts. Engage directly in key deals, executive briefings, and escalations. Understand health system priorities, from EHR optimization to AI-driven clinical workflows, and connect them to AWS capabilities that deliver measurable business and clinical outcomes. - Coach sellers through complex, multi-stakeholder deals - Guide your team through full-cycle enterprise sales motions from discovery through negotiation and close. Help them structure multi-year, multi-service engagements with clear business cases, navigating procurement, legal, compliance, and clinical stakeholders. - Orchestrate cross-functional resources for your team - Ensure your AEs are effectively quarterbacking Solutions Architecture, Specialist Sales, Professional Services, Partner Development, and Marketing resources to deliver comprehensive solutions for their customers. - Develop talent and build succession - Identify skill gaps, create individual development plans, and provide regular feedback. Mentor high-potential sellers toward increased responsibility. Build a bench of future leaders within the West region. - Represent AWS in the healthcare ecosystem - Engage at industry events (HIMSS, HLTH, ViVE, Becker's), sponsor customer-facing thought leadership, and build AWS's brand as a trusted partner in health IT innovation across the West. - Travel - Willingness to travel up to 50% across the West region to support customer engagements, team meetings, and industry events. Then "A day in the life" maybe not needed. Then "About The Team" with subpoints: Diverse Experiences, Why AWS? etc. Those are more about company culture; could be considered "About the team" but not required sections. We could include as "About the Team" maybe under a heading? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but we should stick to those. However we can include "About the Team" as maybe part of "About the role"? Not sure. Safer to include only those sections that have content. We have responsibilities (clear). Next: Basic Qualifications and Preferred Qualifications. Those could go under Requirements or Qualifications. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (basic qualifications) and Qualifications (preferred). Or combine. We need to preserve all substantive info. So we need to list basic qualifications and preferred qualifications as list items under appropriate sections. Basic Qualifications list: - Proven track record of consistently meeting or exceeding $10M+ annual revenue targets in complex, consultative enterprise sales environments - Experience managing full sales cycles — from pipeline generation and qualification through negotiation and close — with deal sizes of $1M+ - Demonstrated ability to build and maintain executive-level relationships (CIO, CMIO, CFO) at large, complex organizations - Strong operational discipline — pipeline management, forecasting accuracy, CRM (Salesforce) - Bachelor's degree or equivalent experience - 10+ Years Experience managing a sales team - Deep knowledge of healthcare provider business models, financial dynamics (margin pressure, value-based care, payer mix), and regulatory environment - Experience with cloud technologies, AI/ML, and digital transformation programs in healthcare — ability to articulate how technology drives clinical and operational outcomes Preferred Qualifications list: - Understanding of health IT landscape — EHR platforms (Epic, Oracle Health/Cerner, MEDITECH), clinical systems, data interoperability (FHIR/HL7), and infrastructure modernization patterns - Track record selling into complex, matrixed healthcare organizations with long sales cycles and multiple decision-makers - Executive presence and communication skills — comfortable presenting to boards, clinical leadership teams, and technical audiences alike - Experience working in matrixed sales organizations with cross-functional GTM motions (SAs, specialists, partners, ProServe) - MBA, MHA, or advanced degree in a relevant field - Familiarity with AWS services or competing cloud platforms Then Benefits: The posting mentions benefits: "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." Also earlier: "Your Amazon package will include sign-on payments, restricted stock units (RSUs), and sales incentives." Also "Learn more about our benefits at https://amazon.jobs/en/benefits." Thus we have benefits content. Pay: The posting includes salary ranges per location: multiple lines with ranges. So we have pay info. Schedule: Not explicitly mentioned besides travel up to 50% (maybe schedule). No explicit schedule like full-time, etc. Could infer full-time but not stated. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated (salary ranges). Benefits is stated. Schedule is not explicitly stated (no mention of hours, remote, etc). Travel is mentioned but that's not schedule. So we should not create a Schedule section. Thus sections: About the role (intro paragraph), Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Benefits, Pay. We need to output HTML fragment only, no /. Use

for each section heading. Use

• for lists. Use

  for prose. We need to preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, etc. Also remove duplicated lines like "Key job responsibilities Key Job Responsibilities". Also remove "Application deadline: Sep 29, 2026" maybe keep as metadata in a short p? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include application deadline in a short p at top maybe. Also Job ID etc can be dropped. We also need to remove "A day in the life About The Team" etc? That's not boilerplate but maybe not needed for sections; we could include as part of About the role? But it's not about the role; it's about team culture. Could be omitted as not required heading; but we must preserve ALL substantive information. Does "About The Team" count as substantive? It's about team diversity, why AWS, etc. It's not directly about the role but still part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Could be placed under a heading like "About the Team" but that's not one of the prescribed headings. However we could embed it under "About the role" as a paragraph? Might be okay but risk missing detail. Perhaps we can create a section "About the Team" using

  even though not listed; the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can use other headings as needed. Safer to include a heading for About the Team. Similarly we have "A day in the life" maybe not needed. Thus sections: About the role (intro paragraph), Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Benefits, Pay, About the Team (maybe includes Diverse Experiences, Why AWS?, Mentorship & Career Growth, Work/Life Balance). Also maybe include "A day in the life" but not needed. We need to avoid filler like "commensurate with experience". Not present. Now craft HTML. Start with maybe a p for application deadline:

  Application deadline: Sep 29, 2026

  Then

  About the role

  then paragraph(s) containing the intro description. We need to keep the description exactly as given but we can split into paragraphs. Use

  for prose. The intro description includes multiple sentences; we can put all in one

  . Then responsibilities:

  Responsibilities

  then
  with each responsibility as
  • . Need to keep the content exactly as given, but we can keep the dash and sub-bullets? The responsibilities each have a leading bold phrase then description. We'll keep as is. We need to ensure we don't lose any detail. Let's copy responsibilities list exactly as in text: - Lead, develop, and scale a team of enterprise Account Executives - Recruit, hire, coach, and retain top sales talent. Set clear expectations, provide ongoing deal coaching, and create a high-performance culture that balances accountability with career development. Coach your team on provider industry challenges and how to address them in support of meeting your customer objectives. - Set and execute the regional go-to-market strategy - Define regional approach, structure territory plans, account segmentation, and opportunity prioritization across AI/Agentic AI, cloud migration, application modernization, data & analytics, and operational efficiency for West region health systems. Translate org-level sales plays into actionable plans your team can execute. - Drive revenue attainment and pipeline discipline – Own and drive the West region number. Ensure accurate forecasting, pipeline coverage, SFDC hygiene, stage progression, and early risk identification across your team's book of business. Deliver against quarterly and annual revenue targets consistently