Jobs · Consulting · Texas

Sr. Solutions Architect HCLS, HCLS HealthTechs

Amazon Web Services (AWS) · Houston, TX · 3 wk ago
ConsultingFull-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 if posting has real specific content. We need to parse the description. We have description paragraphs: "Description The AWS WWPS HCLS team is committed..." etc. Then "Key job responsibilities" list bullet points. Then "About The Team" with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Then "Basic Qualifications", "Preferred Qualifications". Then EEO etc. Then salary ranges per location. Then benefits description. Then location list. Then Company and Job ID. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove the EEO paragraph, accommodation link, etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." maybe keep benefits content but not the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? Probably remove it. Keep the benefits description text. We need to preserve all substantive information. So we need to include sections: About the role (maybe from description paragraph?), Responsibilities (Key job responsibilities), Requirements (maybe Basic Qualifications?), Qualifications (Preferred Qualifications?), Skills (maybe not explicit), Benefits (benefits description), Pay (salary ranges), Schedule (maybe not present). Work/Life Balance is part of About The Team but could be considered a section? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. If content doesn't fit exactly, we may still create those headings if there is substantive content. We have "About The Team" which includes Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. This could be considered "About the role"? Actually "About the role" is more about the job itself. The description paragraph at start describes role. So we can put that under

About the role

. Then responsibilities list under

Responsibilities

. Then Basic Qualifications under

Requirements

(or Qualifications?). The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications separate. Likely Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. Skills maybe not present; we could omit if no specific skills list. Benefits: we have benefits description. Pay: we have salary ranges per location. Schedule: not present; we should not create a Schedule section if no specific content. We also have "About The Team" content; maybe we could incorporate into About the role or maybe treat as part of About the role? The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have "About The Team" with subpoints. But our allowed headings list does not include "About The Team". However we could treat that as part of "About the role" or maybe we could create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map About The Team content into About the role or maybe omit if not fitting. But we could include it under About the role as additional paragraphs. Thus final HTML:

About the role

with paragraphs combining the initial description and About The Team bullet points (maybe as
  • ). Then

    Responsibilities

    with
    • list of responsibilities. Then

      Requirements

      with
      • list of Basic Qualifications. Then

        Qualifications

        with
        • list of Preferred Qualifications. Then

          Benefits

          with

          benefits description. Then

          Pay

          with

          salary ranges (maybe list). Ensure we preserve all substantive info: we need to include the location-based salary ranges exactly as given. Also include benefits description: "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 maybe mention sign-on payments and RSUs from earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's part of compensation; could be included in Pay section. We need to remove duplicated lines: there may be duplicate sentences? Not seeing many. We must not repeat the job title as a heading. The job title is "AWS Solutions Architect". Not to be used as heading. We must not put Job ID/requisition numbers as headings; we can drop them. We must not include boilerplate like EEO, accommodation link, etc. We must not include application instructions. We must not create sections with filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's extract content. About the role: The initial paragraph: "Description 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." Then "Here Are Some Other Qualities We Are Looking For At AWS, we have a credo of "Work hard. Have fun. Make history" In this role, 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." Then "About The Team 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." We can combine these into About the role section. Responsibilities: "Key job responsibilities Ensure success in building and migrating applications, software and services on the AWS platform In partnership with the account management team, formulate and execute a strategy Educate customers of all sizes on the value proposition of AWS, and participate in deep architectural discussions to ensure solutions are designed for successful deployment in the cloud Conduct one-to-few and one-to-many training sessions to transfer knowledge to customers considering or already using AWS Capture and share best-practice knowledge amongst the AWS solutions architect community Author or otherwise contribute to AWS customer-facing publications such as whitepapers Build deep relationships with senior technical individuals within customers to enable them to be cloud advocates Act as a technical liaison between customers, service engineering teams and support" We need to split into list items. Requirements (Basic Qualifications): "Basic Qualifications 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" We need to parse each bullet: maybe each line is a qualification. We'll make

          • for each. Qualifications (Preferred Qualifications): "Preferred 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)" Make list. 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 earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Also maybe mention base salary range? That's Pay. Pay: We have salary ranges per location:

Similar jobs