Delivery Consultant - AI/ML, AWS Professional Services WWPS Healthcare and Life Science

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Description: Application deadline: Sep 27, 2026 (metadata, can be minor metadata, maybe include in a short p or drop). We can include as a short p. - The role: "Delivery Consultant" at AWS, ML Engineer. - About the role: The paragraph after "In this role, you'll work closely with customers..." etc. That's about the role. - Responsibilities: There's a "Key job responsibilities" repeated. We'll extract bullet list. - Basic Qualifications: list of qualifications. - Preferred Qualifications: list. - Skills: maybe combine? The posting mentions knowledge of AWS services, etc. Could be under Skills. - Benefits: The posting mentions "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, parental leave." 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 info. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Also there is "About The Team" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those could be considered as part of About the role or maybe separate sections? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About The Team" could be part of About the role? Probably we can include under About the role. We must not repeat job title as heading. Do not put Job ID as heading. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out things like "Amazon is an equal opportunity employer..." and Los Angeles County specifics, etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at ..."? That's maybe okay to keep as link? Might be considered boilerplate? It's a link to benefits; but it's part of benefits description. Might keep but it's not essential. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly those; but it's a reference. Might keep. We need to preserve all substantive information: so we need to keep the salary ranges per location, the bullet list of responsibilities, basic qualifications, preferred qualifications, benefits description, etc. We need to format as HTML: use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not emit a heading followed by filler/placeholder text. So only include sections where we have real content. Thus sections: - About the role: combine the initial description paragraphs and maybe "About The Team" content (excluding boilerplate). We'll need to extract substantive prose. Let's extract: Opening: "Are you excited about building software solutions around large, complex Machine Learning (ML) and Artificial Intelligence (AI) systems? Want to help the largest global enterprises derive business value through the adoption and automation of Generative AI (GenAI)? Excited by using massive amounts of disparate data to develop AI/ML models? Eager to learn to apply AI/ML to a diverse array of enterprise use? Thrilled to be a key part of Amazon, who has been investing in Machine Learning for decades - pioneering and shaping the world’s AI technology? The Amazon Web Services Professional Services (ProServe) team is seeking a skilled ML Engineer to join our team as a Delivery Consultant at Amazon Web Services (AWS). In this role, you'll work closely with customers to design, implement, and manage AWS AI/ML and GenAI solutions that meet their technical requirements and business objectives. You'll be a key player in driving customer success through their cloud journey, providing technical expertise and best practices throughout the ML project lifecycle. Possessing a deep understanding of AWS products and services, as a Delivery Consultant you will be proficient in architecting complex, scalable, and secure AI/ML and GenAI 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. 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." That's a lot of prose. We'll keep as

  . Then "About The Team" subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are also prose. We'll include them maybe as part of About the role. But we need to avoid duplication: The "About The Team" content includes statements like "AWS values diverse experiences. Even if you do not meet all of the qualifications and skills listed in the job description, we encourage candidates to apply." etc. That's substantive. We'll include them as separate paragraphs under About the role. Now Responsibilities: The "Key job responsibilities" list (some duplicated). We'll extract bullet points: - Implementing end-to-end AI/ML and GenAI projects, from understanding business needs to data preparation, model development, deployment and monitoring - Designing and implementing machine learning pipelines that support high-performance, reliable, scalable, and secure ML workloads - Designing scalable ML solutions and operations (MLOps) using AWS services and leveraging GenAI solutions when applicable - Collaborating with cross-functional teams (Applied Science, DevOps, Data Engineering, Cloud Infrastructure, Applications) to prepare, analyze, and operationalize data and AI/ML models - Serving as a trusted advisor to customers on AI/ML and GenAI solutions and cloud architectures - Sharing knowledge and best practices within the organization through mentoring, training, publication, and creating reusable artifacts - Ensuring solutions meet industry standards and supporting customers in advancing their AI/ML, GenAI, and cloud adoption strategies - This is a customer-facing role with potential travel to customer sites as needed. We'll put each as

• . Now Requirements: Could be Basic Qualifications? The instruction says Requirements and Qualifications separate. Usually Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. We'll follow that. Thus: - Requirements (Basic Qualifications): - 3+ years of software development, or 3+ years of scripting language experience - 3+ years of building machine learning and generative AI models for business application experience - Experience with cloud services related to machine learning (e.g., Amazon SageMaker) and generative AI applications - Qualifications (Preferred Qualifications): - Knowledge of AWS services including compute, storage, networking, security, databases, machine learning, and serverless technologies - Knowledge of AWS services including SageMaker, Bedrock, EC2, ECS, EKS, OpenSearch and AWS certifications - 2+ years of experience with design, deployment, and evaluation of AI agents and orchestration approaches; experience with open source frameworks like LangChain, LangGraph, LlamaIndex, and/ or similar tools - 3+ years of deep learning, computer vision, human robotic interaction, algorithms implementation experience using PyTorch or TensorFlow - Experience building ML pipelines with MLOps best practices, including: data preprocessing, distributed & GPU training, model deployment, monitoring, and retraining; experience with container and CI/CD pipelines - Domain expertise in healthcare and life sciences Note there is some duplication: "Knowledge of AWS services including compute, storage, networking, security, databases, machine learning, and serverless technologies" and "Knowledge of AWS services including SageMaker, Bedrock, EC2, ECS, EKS, OpenSearch and AWS certifications". We'll keep both as separate bullet points. Now Skills: Could be derived from the qualifications? But we already have qualifications. The instruction says we can have Skills section if there is real specific content. The posting mentions "proficiency in architecting complex, scalable, and secure AI/ML and GenAI solutions", "deep understanding of AWS products and services", etc. Might be covered. But we could create a Skills section summarizing technical skills: e.g., "Proficiency in AWS AI/ML services (SageMaker, Bedrock, etc.), experience with MLOps, programming languages, etc." However we must not invent or summarize away detail. We should only include if the posting explicitly lists skills. The posting does not have a separate "Skills" heading; but we could extract from responsibilities and qualifications. However that might be considered summarizing. Safer to omit Skills section if not explicitly present. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills. Now Benefits: We have 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 "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Also "Learn more about our benefits at https://amazon.jobs/en/benefits." We'll keep that as prose or list? Benefits are a list; we can make
  • for each benefit item. But we need to preserve all detail. Could break into items: 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, parental leave, sign-on payments, restricted stock units (RSUs). We'll keep as list. Now Pay: Salary ranges per location. We'll present as a list: each location with range. We must not include filler like "commensurate with experience". The posting includes specific numbers, so we keep. Now Schedule: none, omit. Now also include Application deadline as minor metadata: maybe a short p at top: "Application deadline: Sep 27, 2026". We'll include as

    . Now we need to ensure we don't include boilerplate like "Amazon is an equal opportunity employer..." etc. Remove those. Also remove "Los Angeles County applicants..." etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "Pursuant to the Los Angeles County Fair Chance Ordinance..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's maybe application instruction; remove. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." Might be considered a reference; but it's not boilerplate; it's a link to benefits. Might keep as part of benefits? Could be considered a reference; but it's not essential. I'd keep it as part of benefits paragraph. Now we need to output only HTML fragment, no /, no markdown