Sr. Solutions Architect HCLS, HCLS HealthTechs
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists or paragraphs.
We need to be careful not to include boilerplate like "Amazon is an equal opportunity employer..." etc. Also remove duplicated lines, navigation, legal, EEO, etc.
We need to include the team description, "About The Team" maybe part of About the role? The posting includes "About The Team" with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are substantive. Should we include them? They are under "About The Team". Could be part of About the role or separate section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list About The Team. But we could incorporate that content into About the role section. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should prefer those headings. Likely we should stick to those headings only. So we should map content accordingly.
Thus:
- About the role: include description of role, team commitment, primary goal, etc. Also include "About The Team" content maybe as part of About the role.
- Responsibilities: list from "Key job responsibilities".
- Requirements: Basic Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: maybe the "Here Are Some Other Qualities We Are Looking For" and other qualities like dynamic, creative, etc. Also "Have a strong understanding of large-scale computing solutions." etc. We'll put those in Skills.
- Benefits: list benefits described.
- Pay: list salary ranges per location.
We must not include any placeholder like "commensurate with experience". Not present.
We must not repeat job title.
We must not include Job ID.
We must not include application instructions.
We must not include EEO etc.
Now craft HTML.
We'll produce something like:
About the role
... paragraphs ...
Then Responsibilities
- ... each responsibility ...
Similarly for Requirements, Qualifications, Skills, Benefits, Pay.
We need to preserve all substantive info. Let's extract.
From 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 "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"
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."
Then "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"
Then "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)"
Then 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."
Pay: list ranges per location.
We need to include all that.
Now produce HTML.
We must not include any markdown fences.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
About the role
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 influencing Enterprise Architects, Technical Architects, Cloud Architects, Directors, VPs and CXOs. You will partner with some of the world's 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 Responsibilities list.
We need to split each responsibility as separate - .
Responsibilities list:
- 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
Now Requirements (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,
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists or paragraphs. We need to be careful not to include boilerplate like "Amazon is an equal opportunity employer..." etc. Also remove duplicated lines, navigation, legal, EEO, etc. We need to include the team description, "About The Team" maybe part of About the role? The posting includes "About The Team" with subpoints: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are substantive. Should we include them? They are under "About The Team". Could be part of About the role or separate section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list About The Team. But we could incorporate that content into About the role section. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should prefer those headings. Likely we should stick to those headings only. So we should map content accordingly.
Thus:
- About the role: include description of role, team commitment, primary goal, etc. Also include "About The Team" content maybe as part of About the role.
- Responsibilities: list from "Key job responsibilities".
- Requirements: Basic Qualifications.
- Qualifications: Preferred Qualifications.
- Skills: maybe the "Here Are Some Other Qualities We Are Looking For" and other qualities like dynamic, creative, etc. Also "Have a strong understanding of large-scale computing solutions." etc. We'll put those in Skills.
- Benefits: list benefits described.
- Pay: list salary ranges per location.
We must not include any placeholder like "commensurate with experience". Not present.
We must not repeat job title.
We must not include Job ID.
We must not include application instructions.
We must not include EEO etc.
Now craft HTML.
We'll produce something like:
About the role
... paragraphs ...
ThenResponsibilities
- ... each responsibility ...
About the role
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 influencing Enterprise Architects, Technical Architects, Cloud Architects, Directors, VPs and CXOs. You will partner with some of the world's 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 Responsibilities list. We need to split each responsibility as separate