Sr. Solutions Architect HCLS, HCLS HealthTechs

We need to output HTML fragment with headings

for sections: 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. Preserve all substantive info. We need to parse the description. Let's extract sections: - About the role: The description starts with "Description The AWS WWPS HCLS team is committed...". This is about the role. So we can put that in

About the role

with paragraphs. - Responsibilities: There's a section "Key job responsibilities" with bullet list. So we can put

Responsibilities

with

• items. - Requirements: There's "Basic Qualifications" and "Preferred Qualifications". Could combine into Requirements? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "Basic Qualifications" and "Preferred Qualifications" likely go under Requirements or Qualifications. Since we have both Requirements and Qualifications headings, we need to split content appropriately. Maybe Requirements = basic qualifications (must-have). Qualifications = preferred qualifications (nice-to-have). Skills could be extracted from the description about skills: technical depth, business aptitude, communication, etc. Could also be part of responsibilities. But we need to create a Skills section only if there is real specific content. The posting mentions: "You have technical depth, business aptitude, and the ability to lead in-depth technology discussions, articulating the business value of the AWS platform and services. Effective communication and interpersonal skills are required...". Also later: "You should also have a demonstrated ability to think strategically about business, products, and technical challenges." Also "Have a strong understanding of large-scale computing solutions." etc. So we can put those under Skills. Benefits: The posting mentions benefits: "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 mentions sign-on payments and RSUs. So we can include Benefits section. Pay: The posting includes salary ranges for various locations. So we can include Pay section with those ranges. Schedule: No mention of schedule (e.g., full-time, remote). Not present, so we should not include Schedule section. We must not include placeholder text like "commensurate with experience". The salary ranges are specific. We must not include boilerplate like EEO, accommodations, etc. Remove those. We must not repeat job title as heading. We must not include Job ID. We must preserve all substantive information. Now we need to format. We'll produce something like:

  About the role

  ... paragraphs ...

  Responsibilities

  • ...
  ...

  Requirements

  • 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
  • 10+ years of IT development or implementation/consulting in the software or Internet industries experience

  Qualifications

  • 5+ years of infrastructure architecture, database architecture and networking experience
  • Experience working with end user or developer communities
  • 5+ years of design, implementation, or consulting in applications and infrastructures experience
  • 3+ years experience working with software development or architecture in the healthcare industry
  • Strong knowledge of healthcare privacy regulatory frameworks (e.g. HIPAA, HITRUST)

  Skills

  • Technical depth and business aptitude
  • Ability to lead in-depth technology discussions and articulate business value of AWS platform and services
  • Effective communication and interpersonal skills
  • Ability to think strategically about business, products, and technical challenges
  • Strong understanding of large-scale computing solutions
  • Passion for educating, training, designing, and building cloud solutions for enterprise customers
  • Enjoy keeping technical skills honed and developing new ones

  Benefits

  • Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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
  • Sign-on payments and restricted stock units (RSUs)

  Pay

  • USA, GA, Atlanta: $153,600.00 – $207,800.00 USD annually
  • USA, IL, Chicago: $153,600.00 – $207,800.00 USD annually
  • USA, MA, Boston: $153,600.00 – $207,800.00 USD annually
  • USA, NY, New York: $169,000.00 – $228,600.00 USD annually
  • USA, TX, Austin: $153,600.00 – $207,800.00 USD annually
  • USA, TX, Dallas: $153,600.00 – $207,800.00 USD annually
  • USA, VA, Arlington: $153,600.00 – $207,800.00 USD annually
  • USA, VA, Herndon: $153,600.00 – $207,800.00 USD annually
  We need to ensure we didn't include schedule. Now we need to ensure we didn't include any boilerplate like "Amazon is an equal opportunity employer..." etc. We removed that. We also removed "Why AWS?" section? That is substantive but not under any heading we have. Could be part of About the role? It's about AWS culture. Might be considered part of About the role or maybe we could add a section "About AWS" but not in allowed headings. The instruction says use headings for those specific ones; we can include other content under About the role or maybe we can add a paragraph under About the role that includes the "Why AWS?" and "Inclusive Team Culture" etc. However we must preserve all substantive information. So we need to incorporate that content somewhere. We have About the role section currently only containing the initial description. We can expand it to include the "Why AWS?" and subsequent paragraphs about inclusive team culture, mentorship, work/life balance. That seems appropriate. Thus About the role paragraph(s) will include: - The AWS WWPS HCLS team description. - Why AWS? (world’s most comprehensive cloud platform, etc.) - Inclusive Team Culture (affinity groups, inclusion events, etc.) - Mentorship & Career Growth (knowledge-sharing, mentorship, etc.) - Work/Life Balance (flexibility, etc.) We should not include the "Basic Qualifications" etc there. Now we need to ensure we didn't duplicate content. Let's craft About the role: Paragraph 1: The AWS WWPS HCLS team is committed to helping Healthtech & ISV customers enable their digital transformation journeys. Our primary goal is to meet customers in their cloud journeys and work backwards from their industry-specific needs to transform their businesses and industries. Our team focuses on business outcomes and industry use cases on behalf of our customers, whether that is how we build products and solutions, how we sell, how we deliver, or how we partner. As an Amazon Web Services (AWS) Solutions Architect in AWS WWPS HCLS segment, you are responsible for partnering with our most valuable customers to design cloud architectures utilizing AWS services. You have technical depth, business aptitude, and the ability to lead in-depth technology discussions, articulating the business value of the AWS platform and services. Effective communication and interpersonal skills are required for engaging and influence Enterprise Architects, Technical Architects, Cloud Architects, Directors, VP's and CXOs. You will partner some of the worlds largest companies, to craft highly scalable, flexible and resilient cloud architectures that address customer business problems and accelerate the adoption of AWS services. In collaboration with account managers, you will assist in driving growth across a small set of global customers in your defined country. As a trusted customer advocate, the solutions architect will help organizations understand best practices around advanced cloud-based solutions, and how to migrate existing workloads to the cloud. You will have the opportunity to help shape and execute a strategy to build mind-share and broad use of AWS within enterprise customers. The ability to connect technology with measurable business value is critical to a solutions architect. You should also have a demonstrated ability to think strategically about business, products, and technical challenges. Paragraph 2: 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. Paragraph 3: 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. Paragraph 4: 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. Paragraph 5: 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. That covers all substantive info except the "Here Are Some Other Qualities We Are Looking For At AWS..." section which includes things like "Work hard. Have fun. Make history", "You will love what you do and instinctively know how to make work fun.", "You will be dynamic and creative, and willing to take on any challenge and make a big impact.", "Enjoy working with large, global customers as an active contributor to a diverse team.", "You will have a passion for educating, training, designing, and building cloud solutions for a diverse and challenging set of enterprise customers.", "Have a strong understanding of large-scale computing solutions.", "You will enjoy keeping your existing technical skills honed and developing new ones, so you can make strong contributions to deep architecture discussions.", "You will regularly take part in deep-dive education and design exercises to create world-class solutions built on AWS." Some of these overlap with Skills and Responsibilities. We already captured many in Skills. The "Work hard. Have fun. Make history" is a credo; could be included in About the role maybe as a note. But we can incorporate into About the