Jobs · Project Management · New Jersey

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

Amazon Web Services (AWS) · Jersey City, NJ · 3 wk ago
Project ManagementFull-time
We need to output HTML fragment with sections: About the role? Actually description includes "Description" then some intro paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. We need to decide which sections to include. From posting: - Intro paragraphs: description about excitement, role, etc. Could be "About the role" maybe. - "Key job responsibilities" repeated twice: we can put under Responsibilities. - "About The Team" with subheadings: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those could be part of "About the team" but not in required headings list. We could maybe put under "About the role" or maybe not create a separate heading because not in list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. ...). Likely we should only use those headings. But we can also include other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. Probably we should stick to those. Thus we need to map content to those sections. - About the role: include introductory paragraphs describing role, excitement, etc. - Responsibilities: list of responsibilities from "Key job responsibilities". Use
  • . - Requirements: maybe "Basic Qualifications". Use
    • . - Qualifications: maybe "Preferred Qualifications". Use
      • . - Skills: maybe combine some skill statements? Could be from responsibilities? But we might not have explicit skills section. Could skip if no specific content. - Benefits: posting mentions benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mentions sign-on payments and RSUs. So we can include Benefits. - Pay: posting includes base salary ranges per location. So we can include Pay. - Schedule: not mentioned. So we should not include Schedule. We must not include sections with filler like "commensurate with experience". The pay details are specific ranges per location, so we include. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, equal opportunity, legal, accommodations, etc. Also remove "Application deadline: Sep 27, 2026" maybe? That's metadata; could be folded into a short

        or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we can include a short

        for application deadline maybe. But we could also drop it. Safer to include a short

        with the deadline. We need to preserve all substantive information. So we need to keep the location-based salary ranges, benefits description, responsibilities, basic qualifications, preferred qualifications, about the role/intro, about the team? The about the team content may be considered substantive but not fitting headings. Could we include it under About the role? Possibly we can add a paragraph about team under About the role. But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid adding extra paragraphs inside a section. So we can put the team description inside About the role section as prose. Thus structure:

        Application deadline: Sep 27, 2026

        About the role

        Intro paragraphs about excitement, role description, etc.

        About The Team ... (the team description)

        Responsibilities

        • ... each responsibility

        Requirements

        • Basic Qualifications items

        Qualifications

        • Preferred Qualifications items

        Benefits

        • Benefits items

        Pay

        Salary ranges per location (list)

        We must not include Schedule. We need to ensure we preserve all substantive info: The intro paragraphs include multiple sentences about excitement, building software solutions around ML/AI, helping enterprises derive business value through GenAI, using massive data, eager to learn, thrilled to be part of Amazon, etc. Also mention that AWS Professional Services team seeking skilled ML Engineer to join as Delivery Consultant. Work closely with customers to design, implement, manage AWS AI/ML and GenAI solutions, etc. Also mention that you'll be a key player driving customer success, providing technical expertise throughout ML project lifecycle, possessing deep understanding of AWS products, architecting complex scalable secure solutions, work with stakeholders to gather requirements, assess infrastructure, propose migration strategies, trusted advisors, leading implementation, ensuring adherence to best practices, optimizing performance, managing risks. Also mention that AWS Professional Services organization is global team of experts helping customers realize desired business outcomes when using AWS Cloud, work with customer teams and AWS Partner Network to execute enterprise cloud computing initiatives, provide assistance through offerings, deliver focused guidance through global specialty practices. Also mention "This is a customer-facing role with potential travel to customer sites as needed." We need to keep all that. Now the "About The Team" section includes: - Diverse Experiences: AWS values diverse experiences. Even if you do not meet all qualifications, we encourage candidates to apply. If career just starting, hasn't followed traditional path, includes alternative experiences, don't let it stop you from applying. - Why AWS?: description of AWS being world's most comprehensive cloud platform, pioneered cloud computing, never stopped innovating, customers trust robust suite. - Inclusive Team Culture: employee-led affinity groups foster inclusion, events like CORE and AmazeCon. - Mentorship & Career Growth: raising performance bar, endless knowledge-sharing, mentorship, career-advancing resources. - Work/Life Balance: value work-life harmony, flexibility, etc. We should include that as prose under About the role. Now Responsibilities: list from "Key job responsibilities". The 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 Also note "This is a customer-facing role with potential travel to customer sites as needed." Could be added as a responsibility bullet. Now 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 Now 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 Now Benefits: The posting says: "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." We should include those benefits as list items. Now Pay: list of base salary ranges per location: - USA, CA, San Francisco - 151,000.00 - 204,300.00 USD annually - USA, CO, Denver - 131,300.00 - 177,600.00 USD annually - USA, GA, Atlanta - 131,300.00 - 177,600.00 USD annually - USA, IL, Chicago - 131,300.00 - 177,600.00 USD annually - USA, NJ, Jersey City - 144,500.00 - 195,400.00 USD annually - USA, NY, New York - 144,500.00 - 195,400.00 USD annually - USA, TX, Dallas - 131,300.00 - 177,600.00 USD annually - USA, VA, Arlington - 131,300.00 - 177,600.00 USD annually - USA, VA, Herndon - 131,300.00 - 177,600.00 USD annually - USA, WA, Seattle - 131,300.00 - 177,600.00 USD annually We should keep them as a list or paragraph. Now we need to output only HTML fragment, no /, no markdown fences. We'll include a

        for application deadline maybe. We must not include any boilerplate like EEO, equal opportunity, accommodations, etc. Also remove "Los Angeles County applicants:" etc. Also remove "Criminal history may have a direct..." etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10556723". Also remove "Description" heading. Now let's craft. We'll start with:

        Application deadline: Sep 27, 2026

        About the role

        [intro paragraphs]

        [About The Team content]

        We need to ensure we don't lose any substantive info. Let's write intro paragraphs combined: "Are

Similar jobs