Senior Solution Architect, US-Healthcare

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the description. Key sections: - Description: introductory paragraph about role. Could be "About the role". Use

About the role

then

with that paragraph. - Responsibilities: list of key job responsibilities bullet points. Use

• . - A day in the life: could be part of responsibilities or separate? Might be considered responsibilities but we can include as part of responsibilities or separate "Day-to-day". But we only have allowed headings; we could put under Responsibilities as part of list? Better to keep responsibilities as list; day in life could be separate paragraph under About the role? But we can include as part of responsibilities as additional bullet? However we must not invent sections; we can include a separate "Day in the life" but not in allowed headings. So we must map to allowed headings. Could treat day in life as part of responsibilities (more detail). Or we could include as a paragraph under About the role. - About The Team: could be part of About the role or separate "About the team" not allowed. Could be part of About the role. - Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance: these are generic company info; could be considered Benefits? But they are not specific benefits like health insurance etc. The instruction: include a section ONLY when posting has real, specific content for it. For Benefits, we have specific benefits listed later: health insurance, 401(k) matching, paid time off, parental leave. So we can create Benefits section with those. - Pay: we have salary ranges for multiple locations. That is specific content. So include Pay section. - Schedule: not mentioned; no schedule info. So omit Schedule. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe we can extract skills from responsibilities? Could be technical skills: HIPAA, HL7/FHIR, EHR, generative AI, etc. But we have separate Requirements and Qualifications; Skills could be derived but we might not have explicit skills list. Could omit Skills if no explicit list. However we could include skills like "HIPAA-compliant architecture design", "generative AI", "AWS services", etc. But better to only include if posting explicitly lists skills. It does not have a separate "Skills" heading; but we could infer from responsibilities. However instruction: Prefer a few substantive sections over many thin ones. Might combine Skills into Requirements/Qualifications. Safer to omit Skills section if no explicit list. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now we need to extract content. About the role: combine introductory paragraph and maybe About The Team and Diverse Experiences etc? But we should keep substantive info. Let's craft a paragraph summarizing role: "Are you passionate about transforming healthcare through cloud technology? AWS is seeking a Senior Solutions Architect to serve as a trusted technical advisor to healthcare providers, helping them modernize infrastructure, adopt generative AI, and improve patient outcomes. You'll design HIPAA-compliant architectures that integrate with EHR systems like Epic and Cerner while enabling AI-powered clinical workflows. In this role, you'll partner with CIOs, CTOs, and Chief Medical Information Officers at health systems to lead technical engagements. You'll architect solutions for complex healthcare challenges, including data center migrations and deploying generative AI applications using Amazon Bedrock. This role offers the opportunity to shape how healthcare organizations adopt cloud technology while working across the full breadth of the AWS platform." That's from first paragraph. We could also add About The Team info: "The HCLS Providers Solutions Architecture team is one of the few dedicated SA teams at AWS focused exclusively on healthcare provider organizations. We sit within the AWS Worldwide Public Sector US Healthcare organization alongside Account Executives, Specialist SAs, Professional Services, and healthcare ecosystem partners. Our account-aligned model lets us build long-term trusted advisor relationships with IT and clinical leadership at provider organizations. We develop healthcare-specific cloud and AI solutions, share best practices through knowledge forums, and maintain an inclusive team culture where every architect deepens their healthcare expertise while improving patient care." That is substantive; could be part of About the role. Diverse Experiences etc are generic; could be omitted. Thus About the role paragraph(s) can include both. Now Responsibilities: list from "Key job responsibilities" bullet points. We need to capture each bullet: - Lead customer-facing architecture discussions, whiteboarding sessions, and proof-of-concept builds with healthcare IT and clinical leadership, translating complex technical concepts into solutions that address their business and patient care objectives - Design and implement HIPAA-compliant cloud architectures that integrate with healthcare ecosystems including EHR platforms (Epic, Cerner), health data interoperability standards (HL7/FHIR), and medical imaging systems, ensuring security, compliance, and operational excellence - Drive adoption of generative AI and machine learning services (Amazon Bedrock, SageMaker, HealthLake) within regulated clinical environments, balancing innovation with strict data governance and patient safety requirements - Develop reusable reference architectures, technical proposals, and cost optimization strategies for healthcare-specific workloads including data lake designs, clinical analytics platforms, and infrastructure modernization initiatives - Build and own strategic relationships with senior healthcare executives across 30+ accounts, directly influencing pipeline creation, accelerating deal velocity, and activating under-penetrated accounts to drive territory revenue growth Also "A day in the life" details could be added as responsibilities but we can incorporate as extra bullet points: leading Well-Architected Reviews, running discovery sessions for cloud migrations, designing GenAI architectures for clinical workflows, building HIPAA-compliant reference architectures, drafting technical proposals, creating demo environments using Amazon Bedrock integrated with healthcare systems, collaborating with specialist Solutions Architects on security reviews, contribute reusable healthcare patterns to the SA community, travel roughly 30% of the time for on-site workshops and executive briefings. We could add those as responsibilities as well. Now Requirements: Basic Qualifications list: - 10+ years of IT development or implementation/consulting in the software or Internet industries experience - 8+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - 3+ years of design, implementation, or consulting in applications and infrastructures experience - Prior experience in the Healthcare industry / Experience with one or more of the following: HIPAA/HITRUST; HL7; FHIR; PACS; EHR System We need to keep as list. Qualifications: Preferred Qualifications list: - Experience in a technical role within a sales organization - Cloud Technology Certification (such as Solutions Architecture, Cloud Security Professional or Cloud DevOps Engineering) - Experience working with Electronic Health Records, Medical Imaging, or Data Migration Now Benefits: from paragraph: "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 and restricted stock units (RSUs)." That's compensation but could be part of Pay? It's part of compensation package. Could include in Benefits? Might be part of Pay. But we have Pay section for salary ranges. We could include sign-on payments and RSUs under Benefits or Pay. Since they are compensation components, maybe include in Pay? But Pay section is for salary range. Could add note about sign-on payments and RSUs in Benefits or Pay. The instruction: include Pay section only if posting actually states them. It does state base salary range. It also mentions sign-on payments and RSUs. Could include them in Pay section as additional details. We'll include in Pay: base salary ranges per location, plus note that package includes sign-on payments and RSUs. Now Pay: list salary ranges for each location: - USA, GA, Atlanta - 153,600.00 - 207,800.00 USD annually - USA, NY, New York - 169,000.00 - 228,600.00 USD annually - USA, TN, Nashville - 145,900.00 - 197,400.00 USD annually - USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually We'll output as
  • each. Now Benefits: list health insurance details, 401(k) matching, paid time off, parental leave, sign-on payments and RSUs? Might be duplication. Let's keep Benefits: 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, parental leave. Also mention sign-on payments and RSUs as part of compensation but could be in Pay. We'll include sign-on payments and RSUs in Pay section note. Now we must not include boilerplate like EEO, accommodation link, etc. Now produce HTML fragment:

    About the role

    ... paragraphs ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    • ...
    ...
    Make sure no extra whitespace? It's fine. Now craft the About the role paragraph(s). Could be two paragraphs: first intro, second about team. We'll combine into one

    maybe with line breaks? Better to keep as separate

    tags? The instruction: use

    for prose. Could have multiple

    under same heading. We'll do:

    About the role

    Are you passionate about transforming healthcare through cloud technology? AWS is seeking a Senior Solutions Architect to serve as a trusted technical advisor to healthcare providers, helping them modernize infrastructure, adopt generative AI, and improve patient outcomes. You'll design HIPAA-compliant architectures that integrate with EHR systems like Epic and Cerner while enabling AI-powered clinical workflows. In this role, you'll partner with CIOs, CTOs, and Chief Medical Information Officers at health systems to lead technical engagements. You'll architect solutions for complex healthcare challenges, including data center migrations and deploying generative AI applications using Amazon Bedrock. This role offers the opportunity to shape how healthcare organizations adopt cloud technology while working across the full breadth of the AWS platform.

    The HCLS Providers Solutions Architecture team is one of the few dedicated SA teams at AWS focused exclusively on healthcare provider organizations. We sit within the AWS Worldwide Public Sector US Healthcare organization alongside Account Executives, Specialist SAs, Professional Services, and healthcare ecosystem partners. Our account-aligned model lets us build long-term trusted advisor relationships with IT and clinical leadership at provider organizations. We develop healthcare-specific cloud and AI solutions, share best practices through knowledge forums, and maintain an inclusive team culture where every architect deepens their healthcare expertise while improving patient care.

    Now Responsibilities: combine key job responsibilities and day in the life bullets. List: - Lead customer-facing architecture discussions, whiteboarding sessions, and proof-of-concept builds with healthcare IT and clinical leadership, translating complex technical concepts into solutions that address their business and patient