Sr. Manager, Healthcare Providers West , Healthcare Providers West
- .
- Requirements: Basic Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: maybe not explicit; could combine with qualifications? But we can include Skills if there is content. The posting mentions skills like "Executive presence and communication skills", "Experience working in matrixed sales organizations", etc. Those are in Preferred Qualifications. Could put under Skills.
- Benefits: The posting mentions benefits: comprehensive benefits including health insurance, 401(k) matching, paid time off, parental leave, etc. Also sign-on payments, RSUs, sales incentives. So we have Benefits content.
- Pay: The posting includes base salary ranges per location. So we have Pay.
- Schedule: Travel willingness up to 50% across West region. That's schedule/travel. Could be Schedule section.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, equal opportunity, legal, etc. Also remove application instructions, etc. Remove duplicated lines.
We must preserve all substantive information; do not invent or summarize away detail. Must not include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
We need to ensure we only include sections with real content. Let's extract content. About the role: The first paragraph after description: "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 substantive. Responsibilities: The list under "Key job responsibilities". It includes bullet points (though not formatted as bullet). We need to extract each responsibility. Let's parse: - 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. That's responsibilities. Requirements (Basic Qualifications): - 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 Qualifications (Preferred Qualifications): - 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 Skills: Could be extracted from Preferred Qualifications that are skill-based: Executive presence and communication skills, Experience working in matrixed sales organizations, Understanding of health IT landscape, etc. But we already have Qualifications section; maybe we can combine Skills with Qualifications? The instruction says use headings for sections like Skills. We can create a Skills section if there is specific skill content not covered elsewhere. However, the Preferred Qualifications already includes skills. To avoid duplication, we could put Skills as a subsection of Qualifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Skills (e.g., "Executive presence and communication skills", "Experience working in matrixed sales organizations", "Understanding of health IT landscape", "Familiarity with AWS services"). So we can create Skills section with those items. But we must not duplicate content; we need to preserve ALL substantive information. If we split Preferred Qualifications into Qualifications and Skills, we need to ensure we don't lose any. We could put all Preferred Qualifications under Qualifications, and then Skills could be empty -> not allowed. Better to put Preferred Qualifications under Qualifications, and then maybe Skills could be omitted. However, the instruction says we can have sections like Skills; but we are not required to include all possible headings. So we can omit Skills if we don't have distinct skill content beyond what's in Qualifications. But we do have skill content; but we could still put them under Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine Qualifications and Skills into one Qualifications section. So we will not create a separate Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for Benefits: yes. Pay: base salary ranges per location. Schedule: Travel willingness up to 50% across West region. Now we need to format. We must not include any boilerplate like "Amazon is an equal opportunity employer", "Los Angeles County applicants", etc. Also remove "Application deadline: Sep 29, 2026". That's metadata; we can fold into a short p or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So we could include a short p at top for Application deadline? It's minor metadata; we could drop it. Probably drop it. We also need to remove "A day in the life About The Team Diverse Experiences..." etc. That's boilerplate about culture; we should remove as it's not substantive to role? It's about AWS culture; could be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" etc is likely boilerplate; we should drop. Also remove "Why AWS?" etc. Thus we keep only role description, responsibilities, qualifications, benefits, pay, schedule. Now craft HTML. We need to ensure proper escaping? Not needed. Let's write:
About the role
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.
Responsibilities
- 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