We need to produce HTML fragment with 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. Must preserve all substantive info, no invented details. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary ranges for various locations, and benefits description. So we can include Pay and Benefits sections. Schedule: mentions "approximately 50% co-location on site with customer, AWS and partner teams within the U.S." That's schedule info (co-location). So we can include Schedule.
We need to parse content:
Description: The AWS Professional Services (ProServe) team is seeking a skilled Delivery Consultant to serve as a technical builder for large-scale Healthcare and Life Sciences (HCLS) transformation programs. In this role as an individual contributor, you'll work closely with customers to design, implement, and manage AWS AI ML solutions that meet their technical requirements and business objectives. You'll be a key player in driving customer success through their cloud journey, providing hands-on technical builds and best practices throughout the project lifecycle. You will bring a "T-shaped" profile: proficiency across AI/ML, architecture modernization, and data engineering, paired with distinctive expertise in one of these technical areas. Possessing a deep understanding of AWS products and services, as a Delivery Consultant you will be proficient in architecting complex, scalable, and secure solutions tailored to meet the specific needs of each customer. You’ll work closely with stakeholders to gather requirements, assess current infrastructure, and propose effective migration strategies to AWS. As trusted advisors to our customers, providing guidance on industry trends, emerging technologies, and innovative solutions, you will be responsible for leading the implementation process, ensuring adherence to best practices, optimizing performance, and managing risks throughout the project. This role requires approximately 50% co-location on site with customer, AWS and partner teams within the U.S. The AWS Professional Services organization is a global team of experts that help customers realize their desired business outcomes when using the AWS Cloud. We work together with customer teams and the AWS Partner Network (APN) to execute enterprise cloud computing initiatives. Our team provides assistance through a collection of offerings which help customers achieve specific outcomes related to enterprise cloud adoption. We also deliver focused guidance through our global specialty practices, which cover a variety of solutions, technologies, and industries.
Key job responsibilities As an experienced technology professional, you will be responsible for: Designing, implementing, and engineering complex, scalable, and secure GenAI and ML applications and models built on AWS tailored to customer needs Providing technical guidance and implementation support throughout project delivery, with a focus on using AWS AI/ML services Collaborating with customer stakeholders to gather requirements and propose effective model training, building, and deployment strategies Acting as a trusted advisor to customers on industry trends and emerging technologies Sharing knowledge within the organization through mentoring, training, and creating reusable artifacts
About The Team About AWS: Diverse Experiences: AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job below, 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 pioneeredcloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companiestrust our robust suite of products and services to power their businesses. Inclusive Team Culture - Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (diversity) conferences, inspire us to never stop embracing our uniqueness. 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 in the cloud.
10044 Basic Qualifications 3+ years of cloud architecture and solution implementation experience Knowledge of the primary aws services (ec2, elb, rds, route53 & s3) Experience implementing AWS services in a variety of distributed computing environments Preferred Qualifications 5+ years of IT implementation experience degree in advanced technology, or AWS Professional level certification Knowledge of AWS services including compute, storage, networking, security, databases, machine learning, and serverless technologies Knowledge of security and compliance standards including HIPAA and GDPR Experience and technical expertise (design and implementation) in cloud computing technologies Experience leading the design, development and deployment of business software at scale or recent hands-on technology infrastructure, network, compute, storage, and virtualization experience Experience in performance optimization and cost management for cloud environments Experience presenting technical solutions to diverse audiences in pre-sales environments
Then benefits and pay: 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 list of locations with salary ranges.
We need to include Pay section with salary ranges. Should we list each location? Probably yes, preserve all substantive info. Could list as
- each location with range.
Schedule: "approximately 50% co-location on site with customer, AWS and partner teams within the U.S." So schedule: 50% on-site co-location.
Benefits: list as described.
Qualifications: Basic Qualifications and Preferred Qualifications. Could combine into Requirements? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Likely:
- About the role: description paragraph(s) about role.
- Responsibilities: bullet list of responsibilities.
- Requirements: maybe basic qualifications? Or could be "Requirements" for basic qualifications.
- Qualifications: preferred qualifications.
- Skills: maybe list of skills from qualifications? Could combine but we need to follow headings only if content exists. We have content for skills: knowledge of AWS services, etc. Could put under Skills.
But we must not invent sections. We have content for each.
Let's map:
About the role: The initial description paragraphs (first big paragraph) about role.
Responsibilities: bullet list under "Key job responsibilities".
Requirements: Basic Qualifications (3+ years cloud architecture..., knowledge of primary aws services..., experience implementing...).
Qualifications: Preferred Qualifications (5+ years IT implementation..., degree..., knowledge of AWS services..., knowledge of security..., experience..., experience..., experience..., experience...).
Skills: Could extract specific skills: proficiency across AI/ML, architecture modernization, data engineering, T-shaped profile, architecting complex scalable secure solutions, gathering requirements, assessing infrastructure, proposing migration strategies, providing guidance on industry trends, leading implementation, optimizing performance, managing risks, mentoring, training, creating reusable artifacts, etc. But many of these are already in responsibilities. Might be redundant. Perhaps better to put skills under Qualifications? But we need to follow instruction: Use headings only when posting has real specific content. We have content for skills: "proficiency across AI/ML, architecture modernization, and data engineering", "distinctive expertise in one of these technical areas", "deep understanding of AWS products and services", "proficient in architecting complex, scalable, and secure solutions", etc. We could put those under Skills.
Benefits: bullet list of benefits.
Pay: list salary ranges per location.
Schedule: statement about 50% co-location.
We must not include boilerplate like "About The Team About AWS:" etc. That's generic fluff; we should remove. Also remove "Diverse Experiences:", "Why AWS?", "Inclusive Team Culture", etc. Those are boilerplate. Also remove "10044". Also remove equal opportunity employer lines, Los Angeles County etc. Also remove "Learn more about our benefits at ..."? That's a link; maybe keep as part of benefits? It's a reference; could keep but it's not substantive benefit detail. Might be considered boilerplate; but it's a link to benefits page. Might be okay to keep as part of benefits? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not exactly boilerplate but it's a reference; could keep but it's not substantive benefit detail. Might be okay to keep as part of benefits? However, we already list benefits; the link is extra. Could keep as a
with link? Might be considered application instruction? Not exactly. Safer to omit.
Also remove "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." That's substantive for Pay section. Keep.
Now produce HTML.
Structure:
About the role
... (the description paragraph(s) about role). Need to combine maybe two paragraphs: first big paragraph about role, plus maybe second paragraph about AWS Professional Services organization? That is generic fluff; we should remove. So only keep the role description.
Let's extract role description: "The Amazon Web Services Professional Services (ProServe) team is seeking a skilled Delivery Consultant to serve as a technical builder for large-scale Healthcare and Life Sciences (HCLS) transformation programs. In this role as an individual contributor, you'll work closely with customers to design, implement, and manage AWS AI ML solutions that meet their technical requirements and business objectives. You'll be a key player in driving customer success through their cloud journey, providing hands-on technical builds and best practices throughout the project lifecycle. You will bring a "T-shaped" profile: proficiency across AI/ML, architecture modernization, and data engineering, paired with distinctive expertise in one of these technical areas. Possessing a deep understanding of AWS products and services, as a Delivery Consultant you will be proficient in architecting complex, scalable, and secure solutions tailored to meet the specific needs of each customer. You’ll work closely with stakeholders to gather requirements, assess current infrastructure, and propose effective migration strategies to AWS. As trusted advisors to our customers, providing guidance on industry trends, emerging technologies, and innovative solutions, you will be responsible for leading the implementation process, ensuring adherence to best practices, optimizing performance, and managing risks throughout the project. This role requires approximately 50% co-location on site with customer, AWS and partner teams within the U.S."
That includes schedule info; but we will move schedule to its own section. So we could keep the sentence about 50% co-location in About the role or schedule. Better to put schedule separate. So we can remove that sentence from About the role and put in Schedule.
Thus About the role paragraph: everything except the schedule sentence.
Let's craft:
"The Amazon Web Services Professional Services (ProServe) team is seeking a skilled Delivery Consultant to serve as a technical builder for large-scale Healthcare and Life Sciences (HCLS) transformation programs. In this role as an individual contributor, you'll work closely with