Principal Healthcare Solutions Architect, AI Solutions

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 content. We need to parse the description. First, job title is Healthcare Solutions Architect. Not to repeat as heading. We need to extract sections: - About the role: The description starts with "At Amazon Web Services (AWS), we are seeking a Healthcare Solutions Architect...". That's about the role. Could be "About the role". We'll include that. - Responsibilities: "Key job responsibilities" bullet list. We'll list each bullet. - Requirements: Basic Qualifications and Preferred Qualifications? Could be "Qualifications" or "Requirements". The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings. We have Basic Qualifications and Preferred Qualifications. Could combine into "Qualifications". Or separate "Requirements" and "Preferred Qualifications". But we need to avoid filler. We'll include "Qualifications" heading with both basic and preferred maybe as sublists? But we need

• for any list. Could have two lists under Qualifications: Basic Qualifications and Preferred Qualifications as subheadings? But subheadings not allowed? Only h3 for section headings. Could embed as paragraphs with bold? Probably better to have two sections: "Basic Qualifications" and "Preferred Qualifications". Both are valid headings from list? The list includes Requirements, Qualifications, Skills. Not Basic Qualifications. But we can use "Qualifications" as heading and then separate paragraphs for basic and preferred. Or we could have "Requirements" for basic qualifications and "Preferred Qualifications" as separate heading (though not in list). The instruction says use headings for sections like those examples, but not limited to exactly those? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings; we shouldn't invent others like "Basic Qualifications". So we should map content to those headings. Thus: - About the role: intro paragraph. - Responsibilities: list of responsibilities. - Requirements: maybe basic qualifications. - Qualifications: maybe preferred qualifications? Or we could combine both under Qualifications and note basic vs preferred in paragraphs. But we need to preserve all info. Could do:

  Requirements

  list of basic qualifications.

  Qualifications

  list of preferred qualifications. That seems okay: both headings are from the list. - Skills: maybe we can extract skills from responsibilities? Not explicit. Could omit if no specific skills section. - Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance...". Also mentions sign-on payments and RSUs. So we have benefits content. - Pay: The posting includes salary ranges for various locations. So we have Pay section. - Schedule: Not mentioned (travel ~30% but that's not schedule). No explicit schedule like full-time, etc. Could omit. We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. Also remove "About The Team" sections like Diverse Experiences, Why AWS?, Mentorship & Career Growth, Work/Life Balance. Those are boilerplate? They are about company culture; maybe we should keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About The Team" sections are not explicitly listed as boilerplate, but they are generic marketing. However they contain substantive info about AWS culture. The instruction says "Prefer a few substantive sections over many thin ones." Might be okay to include them under "About the role" or separate? But we already have About the role. Could incorporate some of that into About the role? But we must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info somewhere. Could create a section "About AWS" or "Company Overview". But not in allowed headings. Could we put under "About the role"? That section already includes role description; adding AWS culture might be okay as part of About the role. But we need to preserve all detail; we can add paragraphs about AWS culture under About the role. Similarly, "About The Team" includes Diverse Experiences, Why AWS?, Mentorship & Career Growth, Work/Life Balance. We'll incorporate those as paragraphs under About the role. We must not repeat job title as heading. We must not include Job ID / requisition numbers as headings; we can drop them. We must not include Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits and pay, so include. Schedule: not stated; we omit. Now craft HTML. We'll need to escape any special characters? Not needed. Structure:

  About the role

  ... combined intro and AWS culture paragraphs.

  Responsibilities

  • ...
  ...

  Requirements

  • 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

  Qualifications

  • 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

  Benefits

  Amazon 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. Additionally, the position includes sign-on payments and restricted stock units (RSUs).

  Pay

  The base salary range for this position varies by 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
  Actually need
  • inside

    ? Better to have

    then

    . We'll do:

    Pay

    The base salary range for this position varies by location:

    • USA, CA, San Francisco: $210,200.00 - $284,300.00 USD annually
    ...
    We must not include any extra sections like Schedule. Now ensure we removed boilerplate: EEO statements, Los Angeles County applicants text, San Francisco Fair Chance, accommodation link, etc. Also removed "About The Team" headings but we incorporated content into About the role. We need to check that we preserved all substantive information from the original description. Let's list original substantive pieces: - Intro paragraph about role at AWS, Applied AI Solutions GTM, shape GTM strategy, help customers succeed using AWS technologies, linking tech with business value for healthcare and life sciences. - Vision of AWS Applied AI Solutions: provide business applications leveraging Amazon's experience, used by millions, blend vision with curiosity, build opinionated turnkey solutions. - Work closely with Business Development, Sales Specialists, Product leadership to develop, accelerate, sell current and new healthcare products. - Engage directly with customers to understand challenges, design/propose technical solutions, guide implementation. - Establish/grow business and technical relationships with customers/internal stakeholders, drive adoption/value realization. - Use knowledge to work with Product org to develop new features/capabilities and influence product roadmap. - Key job responsibilities list (we captured). - About The Team: Diverse Experiences (encourage apply even if not meet all qualifications), Why AWS? (cloud platform, pioneering, customers trust), Inclusive Team Culture (affinity groups, inclusion events), Mentorship & Career Growth (knowledge-sharing, mentorship), Work/Life Balance (flexibility). - Basic Qualifications list. - Preferred Qualifications list. - Equal opportunity employer statement (boilerplate to remove). - Los Angeles County applicants details (boilerplate to remove). - San Francisco Fair Chance (boilerplate). - Inclusive culture empowers Amazonians (boilerplate? maybe keep? It's similar to inclusive team culture but we already have that. Could be considered boilerplate; but it's a statement about inclusive culture. Might be safe to remove as it's generic. However we already captured inclusive team culture earlier. We'll remove duplicate. - Accommodation link (boilerplate to remove). - If country/region not listed contact recruiting partner (boilerplate). - 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..., 401(k) matching, paid time off, parental leave. Learn more about our benefits at link. (We captured benefits and pay, but we removed the link.) - Salary ranges per location (we captured). - Company - Amazon Web Services, Inc. (maybe we can include as part of About the role? Not needed but could be considered metadata. Could drop as it's not substantive about role. Probably safe to drop. - Job ID: A10553958 (drop). Now check if we missed any substantive info: The "About AWS" paragraph about being world's most comprehensive cloud platform, pioneered cloud computing, never stopped innovating, customers trust. That's part of Why AWS? we included. Inclusive Team Culture: affinity groups, inclusion events, foster stronger teams, continual innovation fueled by bold ideas, fresh perspectives, passionate voices. We included. Mentorship & Career Growth: endless knowledge-sharing, mentorship, career-advancing resources to develop into better-rounded professional. We included. Work/Life Balance: value work-life harmony, flexibility as part of working culture. We included. Now ensure we didn't inadvertently include any boilerplate like "Amazon is an equal opportunity employer..." etc. We removed. Now check that we didn't include any placeholder text like "commensurate with experience". Not present. Now produce final HTML. Be careful to close tags properly. Let's craft:

    About the role