Sr. Manager, Healthcare Providers West , Healthcare Providers West
Amazon Web Services (AWS) · Salt Lake City, UT · 1 mo ago
Business DevelopmentFull-time
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 must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Description: Application deadline: Sep 29, 2026 (maybe minor metadata, could be 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.
- Key job responsibilities (duplicate heading). Then bullet list of responsibilities.
- A day in the life (maybe not needed? It's a heading but no content? Actually after that heading there is "About The Team" etc. Might be filler. We should only include sections with real content. "A day in the life" has no content after it? Actually after that heading there is "About The Team". So "A day in the life" is likely a placeholder heading with no content; we should not include it.
- About The Team: then paragraphs about Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are subheadings but not in our allowed list; we could treat them as part of About the role? But we have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "About The Team" content to "About the role". Or we could create a section "About the role" and put that content there. The instructions: use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Description: Application deadline: Sep 29, 2026 (maybe minor metadata, could be 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.
- Key job responsibilities (duplicate heading). Then bullet list of responsibilities.
- A day in the life (maybe not needed? It's a heading but no content? Actually after that heading there is "About The Team" etc. Might be filler. We should only include sections with real content. "A day in the life" has no content after it? Actually after that heading there is "About The Team". So "A day in the life" is likely a placeholder heading with no content; we should not include it.
- About The Team: then paragraphs about Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are subheadings but not in our allowed list; we could treat them as part of About the role? But we have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "About The Team" content to "About the role". Or we could create a section "About the role" and put that content there. The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when we have content. So we need to decide which sections we have content for.
We have content for:
- About the role: includes overview of role, mission, etc. Could combine the initial description and About The Team sections.
- Responsibilities: the bullet list under Key job responsibilities.
- Requirements: Basic Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: maybe not explicitly listed; but we could infer from qualifications? Might be better to not create Skills if no explicit list.
- Benefits: The paragraph about benefits: "Amazon also offers comprehensive benefits including health insurance ... 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 mention of base salary range later. So we have benefits content.
- Pay: The base salary range for various locations. That is specific pay info. So we should include Pay section.
- Schedule: Travel - willingness to travel up to 50% across the West region. That's schedule/content about travel. Could be considered Schedule. Also maybe work-life balance but that's more benefits. We'll include Schedule with travel expectation.
We must not include filler like "commensurate with experience". We have specific numbers.
We must not repeat job title as heading.
We must not include Job ID etc.
We must remove boilerplate: EEO statements, equal opportunity, etc. Also remove "Los Angeles County applicants:" etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Company - Amazon Web Services, Inc." etc.
We must preserve all substantive information. So we need to keep the details about responsibilities, qualifications, etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
About the role
... combined overview ...
Responsibilities
- ... each responsibility ...
Requirements
- ... each basic qualification ...
Qualifications
- ... each preferred qualification ...
Benefits
... benefits description ...
Pay
... salary ranges per location ...
Schedule
... travel expectation ...
We need to ensure we don't include filler like "not specified". All content is specific. Now we need to extract the substantive content. Let's extract About the role content: From 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." Then About The Team section includes: "Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." "Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses." "Inclusive Team Culture AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do." "Mentorship & Career Growth We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional." "Work/Life Balance We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve." These are all substantive and could be part of About the role. We'll combine them into a few paragraphs. Now Responsibilities: list from "Key job responsibilities" bullet points. Let's extract each bullet: - 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. Note: Travel appears also in responsibilities but we might move to Schedule. However it's listed under responsibilities. We'll keep it in responsibilities? But we also have a Schedule section. To avoid duplication, we could keep travel in Schedule and not duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move travel to Schedule, we still preserve it. It's okay to not duplicate. We'll include travel in Schedule. Thus responsibilities list will exclude the Travel bullet. Now 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 Now Qualifications (Preferred Qualifications): - Understanding of health IT landscape — EHR platforms (Epic, Oracle Health/Cerner, MEDITECH), clinical systems, data