Delivery Consultant-Migrations, Worldwide Public Sector Professional Services, Health Care Life Sciences

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 description. We have: - Description includes Application deadline: Sep 20, 2026 (metadata, we can drop or short p). Not a heading. - The Amazon Web Services Professional Services (ProServe) team is seeking a skilled Delivery Consultant... (intro paragraph). That's about the role. - Then "Key job responsibilities As an experienced technology professional, you will be responsible for:" followed by bullet list. - Then "About The Team" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are more about team/culture, could be considered "About the role"? Actually "About The Team" is separate. But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. - "Basic Qualifications" list. - "Preferred Qualifications" list. - Then benefits paragraph: "Amazon also offers comprehensive benefits including health insurance ..." plus link. - 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." Then list of locations with salary ranges. - Schedule: Not mentioned. No schedule info. So we should not include Schedule section. - Skills: Could be derived from qualifications? But we have separate sections for Requirements, Qualifications, Skills. The posting includes Basic Qualifications (requirements) and Preferred Qualifications (preferred). Could map Basic Qualifications to Requirements, Preferred Qualifications to Qualifications? Or maybe Skills separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where. We have: - About the role: intro paragraph describing role. - Responsibilities: bullet list under "Key job responsibilities". - Requirements: Basic Qualifications. - Qualifications: Preferred Qualifications? Or maybe Qualifications includes both basic and preferred? But we have separate Requirements and Qualifications headings. Usually Requirements = basic qualifications, Qualifications = preferred qualifications or additional qualifications. We'll follow that. - Skills: Could be derived from preferred qualifications like experience with automation, scripting, certifications, etc. But we could also put those under Qualifications. However we need to avoid thin sections. If we put skills separate, we need to ensure there is real specific content. The posting includes "Experience with automation and scripting (e.g., Terraform, Python)" etc. That's skill. Also "Knowledge of Epic technical infrastructure..." etc. That's skill. So we could create Skills section with those items. - Benefits: paragraph about benefits. - Pay: salary ranges. - Schedule: none -> omit. We must not repeat job title as heading. Not include Job ID etc. We can include application deadline as short p maybe. We must remove boilerplate: EEO, equal-opportunity, scam-warning, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove Los Angeles County applicants text etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at ..."? That's maybe okay but it's a link; we can keep benefits description but maybe drop the link as it's not substantive? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is not substantive? It's a reference; we could keep but it's not required. Safer to keep the benefits description but maybe drop the link as it's not essential. However the link is part of benefits info; but it's a URL. Might be considered metadata. I'd keep the benefits description without the link. Also remove "Company - Amazon Web Services, Inc." maybe not needed. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

Application deadline: Sep 20, 2026

About the role

The Amazon Web Services Professional Services (ProServe) team is seeking a skilled Delivery Consultant to join our team at Amazon Web Services (AWS). In this role, you'll work closely with customers to design, implement, and manage AWS 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 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 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.

Responsibilities

• Designing and implementing complex, scalable, and secure AWS solutions tailored to customer needs
• Providing technical guidance and troubleshooting support throughout project delivery
• Collaborating with stakeholders to gather requirements and propose effective migration 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

Requirements

• 3+ years of cloud architecture and solution implementation experience
• Bachelor's degree in Computer Science, Math, or a related field
• Experience managing medium to large-scale projects
• Experience with software development life cycle (sdlc) and agile/iterative methodologies
• Experience architecting/operating solutions built on AWS
• Experience with the migration or implementation of a mission-critical healthcare platform, EHR environment, or similarly complex enterprise workload to AWS

Qualifications

• Experience with compliance & security standards including PCI DSS, ISO 27001, HIPAA, and NIST
• Experience implementing cloud services including migrations and modernization projects or similar AWS experience preferred, with proficiency in a wide range of AWS services (e.g., EC2, S3, RDS, Lambda, IAM, VPC, CloudFormation)
• AWS Professional level certifications (e.g., Solutions Architect Professional, DevOps Engineer Professional) preferred
• Experience with automation and scripting (e.g., Terraform, Python)
• Knowledge of Epic technical infrastructure, including Chronicles/InterSystems IRIS, ECP, Hyperspace, Hyperdrive, Interconnect, production and non-production environments, disaster recovery, and integrated third-party applications.
• Experience with the end-to-end migration, implementation, or modernization of an Epic EHR environment on AWS, including architecture, planning, testing, cutover, and post-migration stabilization.

Skills

• Experience with automation and scripting (e.g., Terraform, Python)
• Knowledge of Epic technical infrastructure (Chronicles/InterSystems IRIS, ECP, Hyperspace, Hyperdrive, Interconnect, production/non-production environments, disaster recovery, integrated third‑party applications)
• Experience with end‑to‑end Epic EHR migration/modernization on AWS (architecture, planning, testing, cutover, post‑migration stabilization)
• Proficiency with AWS services (EC2, S3, RDS, Lambda, IAM, VPC, CloudFormation)
• Understanding of compliance & security standards (PCI DSS, ISO 27001, HIPAA, NIST)
• AWS Professional level certifications (Solutions Architect Professional, DevOps Engineer Professional)

But note we duplicated some items from Qualifications into Skills. Might be redundant. Better to keep Skills distinct: maybe we can extract skills from the preferred qualifications that are skill-based: automation/scripting, Epic knowledge, AWS services proficiency, compliance/security standards, certifications. However the Qualifications section already includes those. To avoid duplication, we could move those to Skills and keep Qualifications more about experience/certifications? But the instruction: Prefer a few substantive sections over many thin ones. Having both Qualifications and Skills may be thin if they overlap. Perhaps we can combine them: Use Qualifications for both experience and skills, and omit Skills. But we need to follow allowed headings; we can omit Skills if not enough distinct content. Let's see: The posting includes "Preferred Qualifications" list which includes experience with compliance & security standards, experience implementing cloud services, AWS certifications, experience with automation/scripting, knowledge of Epic technical infrastructure, experience with end-to-end migration of Epic EHR. Those are all qualifications/experience. So we can put them under Qualifications. Then we may not need Skills section. However we still have Basic Qualifications (Requirements). So we have Requirements and Qualifications. That's two sections. That's fine. Thus we will not include Skills section. Now Benefits: we have paragraph about benefits. We'll include that. Pay: we have base salary ranges list. We'll include that. Schedule: none -> omit. We also need to include the application deadline maybe as a short p before sections. We must not include any boilerplate like EEO, legal, etc. Also remove "Los Angeles County applicants..." etc. Also remove "If you have a disability..." etc. Also remove "Learn more about our benefits at ..." link. Also remove "Company - Amazon Web Services, Inc." and Job ID. Now produce HTML. Check for any duplicated lines: we need to ensure we didn't inadvertently repeat same bullet. Let's craft final HTML. We'll start with

Application deadline: Sep 20, 2026

Then About the role paragraph as above. Then Responsibilities ul. Then Requirements ul (Basic Qualifications). Then Qualifications ul (Preferred Qualifications). Then Benefits

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.

Then Pay

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.

Then maybe a

with each location range as
• . We'll list them. We need to preserve all substantive information: the list of locations and ranges. We'll include them. Let's list: - 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 - 1