Principal Healthcare Solutions Architect, AI Solutions

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, etc. Use

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

  for prose. Do not repeat job title as heading. Do not put Job ID as heading. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits sections only if posting actually states them. The posting includes salary ranges for various locations, and benefits description. So we can include a Benefits section (maybe also Pay). The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits? But they said use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Pay and Benefits if present. The posting includes salary ranges (Pay) and benefits description. So we can have both Pay and Benefits sections. Schedule not present (no mention). So omit Schedule. We need to preserve all substantive information. So we need to capture description paragraphs, responsibilities list, qualifications, preferred qualifications, etc. Also include "About The Team" maybe as About the role? Actually there is "About The Team" section with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are more about company culture; could be part of About the role or maybe we treat as About the role. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (including description and team info). Responsibilities (list). Requirements (basic qualifications). Qualifications (preferred qualifications). Skills maybe not separate; we could omit if not explicit. Benefits and Pay sections. We must not invent or summarize away detail. Must preserve all substantive info. So we need to include each bullet point from responsibilities, each qualification, each preferred qualification, each benefit detail, each salary range per location. We need to format as HTML fragment only, no /, no markdown fences. Let's extract content. Description paragraphs: "At Amazon Web Services (AWS), we are seeking a Healthcare Solutions Architect to join our Applied AI Solutions (AAIS) Go to Market (GTM) organization. In this role, you will help shape and deliver on our GTM strategy for global healthcare customers and partners. As a solutions architect, you will be at the forefront of helping customers succeed using AWS technologies, linking technology with measurable business value for healthcare and life sciences organizations. As part of the AWS Applied AI Solutions organization, we have a vision to provide business applications, leveraging Amazon's unique experience and expertise, that are used by millions of companies worldwide to manage day-to-day operations. We blend vision with curiosity and Amazon's real-world experience to build opinionated, turnkey solutions. In this role, you will work closely with Business Development, Sales Specialists, and Product leadership to develop, accelerate, and sell current and new healthcare products. You will engage directly with customers to understand their business challenges, design and propose technical solutions, and guide successful implementation. By establishing and growing business and technical relationships with customers and internal stakeholders, you will drive customer adoption and value realization of AWS solutions in the healthcare and life sciences industry. You will use this knowledge to work with the Product organization to develop new features and capabilities and influence the product roadmap." That's the description. Then "Key job responsibilities" bullet list: - Work with Business Development (BD) and Sales leaders to lead technical engagement with customers to understand requirements, propose solutions, and address technical concerns - Build and deliver technical presentations, demonstrations, and proofs of concept to showcase AWS capabilities to Healthcare customers - Partner with Sales, Business Development, and Marketing teams to develop and execute go-to-market strategies for healthcare solutions - Collaborate with Product teams to develop new features, products, and services that delight healthcare customers, providing technical expertise and customer feedback - Capture and share best practices and technical knowledge within the AWS solutions architect community - Develop customer-facing technical content such as reference architectures, whitepapers, and implementation guides for healthcare use cases - Stay current on industry trends, regulations, and emerging technologies in the healthcare and life sciences space - Travel ~30% of the time to support customer engagements Then "About The Team" subpoints: - 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 more about company culture; we can incorporate into About the role section. Then "Basic Qualifications" list: - 12+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - Bachelor's degree in computer science, engineering, mathematics or equivalent - Experience developing technology solutions and evangelising end-to-end technology roadmaps that guide IT transformations toward cloud computing - Experience communicating across technical and non-technical audiences and at C-level, including training, workshops, publications Then "Preferred Qualifications" list: - Knowledge of large scale automation and workflow management or equivalent - Knowledge of distributed systems design and implementation or equivalent - Knowledge of database design and implementation or equivalent - Knowledge of presentations and whiteboarding skills with a high degree of comfort speaking with internal and external executives, IT management, and developers - Experience architecting, migrating, transforming or modernizing customer requirements to the cloud Then there is EEO boilerplate etc which we must remove. Then Los Angeles County applicants etc (legal boilerplate) remove. Then San Francisco Fair Chance etc remove. Then inclusive culture etc maybe duplicate; we already captured some but there is also "Our inclusive culture empowers Amazonians to deliver the best results for our customers." plus accommodation link etc. That's boilerplate; remove. Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." remove. Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). 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." Then salary ranges per location: - USA, CA, San Francisco - 210,200.00 - 284,300.00 USD annually - USA, IL, Chicago - 182,800.00 - 247,300.00 USD annually - USA, MA, Boston - 182,800.00 - 247,300.00 USD annually - USA, NY, New York - 201,000.00 - 272,000.00 USD annually - USA, TX, Dallas - 182,800.00 - 247,300.00 USD annually - USA, WA, Seattle - 182,800.00 - 247,300.00 USD annually Then "Company - Amazon Web Services, Inc. Job ID: A10553958" remove Job ID. We need to keep the salary ranges and benefits description. We need to avoid filler like "commensurate with experience" etc. Not present. We need to output HTML. Structure:

  About the role

  ... description paragraphs + maybe About The Team content integrated.

  We could split About the role into two paragraphs: first description, second about team (maybe as

  with bullet list? But About the team is list of items; we could treat as

  • but heading is About the role; we could embed as

    with sentences. However the instruction: Use

    • for any list of duties/requirements/benefits. For About the team, it's not duties/requirements/benefits; it's more descriptive; we can keep as

      paragraphs. Thus:

      About the role

      At Amazon Web Services (AWS), we are seeking a Healthcare Solutions Architect to join our Applied AI Solutions (AAIS) Go to Market (GTM) organization. In this role, you will help shape and deliver on our GTM strategy for global healthcare customers and partners. As a solutions architect, you will be at the forefront of helping customers succeed using AWS technologies, linking technology with measurable business value for healthcare and life sciences organizations. As part of the AWS Applied AI Solutions organization, we have a vision to provide business applications, leveraging Amazon's unique experience and expertise, that are used by millions of companies worldwide to manage day-to-day operations. We blend vision with curiosity and Amazon's real-world experience to build opinionated, turnkey solutions. In this role, you will work closely with Business Development, Sales Specialists, and Product leadership to develop, accelerate, and sell current and new healthcare products. You will engage directly with customers to understand their business challenges, design and propose technical solutions, and guide successful implementation. By establishing and growing business and technical relationships with customers and internal stakeholders, you will drive customer adoption and value realization of AWS solutions in the healthcare and life sciences industry. You will use this knowledge to work with the Product organization to develop new features and capabilities and influence the product roadmap.

      Then maybe another

      for About The Team bullet points? Could be

      • but it's not duties/requirements/benefits; but we could still use
        • for list; instruction says use
          • for any list of duties/requirements/benefits. It doesn't forbid using for other lists, but better to follow. We'll just put as

            with sentences separated by line breaks? Could use
            but not ideal. Maybe we can keep as

            and separate with
            . But we can also make separate

            for each bullet. That would be many thin sections; but they said prefer few substantive sections over many thin ones. So maybe combine into one

            with semicolons. We'll include as a single paragraph summarizing the team culture points.