Delivery Consultant-Migrations, Worldwide Public Sector Professional Services, Health Care Life Sciences
About the role
with. Responsibilities: The "Key job responsibilities" bullet list. Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Skills: Could be derived from Preferred Qualifications (experience with compliance, automation, etc.) but we already have Qualifications. Might combine? The instruction says prefer few substantive sections over many thin ones. We could merge Preferred Qualifications into Qualifications? But they said separate headings for Requirements, Qualifications, Skills. We need to decide if we have content for each. We have Basic Qualifications (requirements). Preferred Qualifications (qualifications). Skills maybe from list of AWS services, automation, scripting, Epic etc. Could be considered Skills. We could put skills under Skills heading. Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also earlier mentions sign-on payments and RSUs. Also "Work/Life Balance" etc. So we have benefits content. Pay: The posting includes base salary ranges for various locations. So we have pay info. Schedule: No explicit schedule info (like full-time, remote). Not present. So we should not include Schedule section. We must not include boilerplate like EEO, equal opportunity, legal, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points etc. We need to format lists with
- . For prose use
. We need to avoid repeating job title as heading. We need to output only HTML fragment. Let's structure:
About the role
... (combined paragraphs describing role)
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
We could list specific technical skills: AWS services, automation/tools, Epic, compliance standards, etc. But we already covered many in Qualifications. Might be redundant. Perhaps we can omit Skills section if content overlaps heavily. But we need to decide: The instruction says prefer few substantive sections over many thin ones. If Skills would be thin, we could omit it. However we have some skill-specific items not captured elsewhere: e.g., proficiency in wide range of AWS services, automation scripting, Epic infrastructure. Those are in Qualifications already. So we could skip Skills. But we need to include Benefits and Pay sections. Benefits: combine bullet points.Benefits
- Sign-on payments
- Restricted stock units (RSUs)
- Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans)
- Employee Assistance Program (EAP)
- Mental Health Support
- Medical Advice Line
- Flexible Spending Accounts
- Adoption and Surrogacy Reimbursement coverage
- 401(k) matching
- Paid time off
- Parental leave
- USA, CA, San Francisco - $151,000.00 - $204,300.00 USD annually ... etc. We should keep the exact numbers as given. Let's list all: 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, 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, Austin - 131,300.00 - 177,600.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'll output as list. We must not include metadata like Application deadline, Job ID, Company, etc. Also remove EEO, legal, etc. Also remove "About The Team" subsections? Those contain info about diversity, why AWS, inclusive culture, mentorship, work/life balance. Some of that could be considered Benefits or About the role? But we already have Benefits covering compensation and benefits. The "About The Team" content is more about culture; could be considered part of About the role? But we already have About the role describing role. The instruction says include a section only when posting has real specific content for it. The "About The Team" content is specific but not covered by our headings. Could we map to "About the role"? Might be okay to incorporate into About the role paragraph? But we must preserve all substantive information; we cannot drop it. So we need to include that info somewhere. Where? Could be under About the role as additional paragraphs. Or we could create a separate section like "About the team" but not allowed headings list only those specific headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we shouldn't invent other headings. So we must fold that content into one of those allowed headings. Where does it fit best? Possibly "About the role" could include description of team culture etc. Or "Benefits" could include work/life balance, mentorship, etc. But Benefits already about compensation and benefits; culture could be considered part of Benefits? Might be a stretch but acceptable. However we already have Benefits list; we could add paragraphs about culture under Benefits heading as
elements. Alternatively we could put under "About the role" as additional paragraphs describing team and culture. That seems plausible: About the role can include description of team, culture, why AWS, etc. So we will expand About the role paragraph to include those details. Thus we need to incorporate all substantive info from "About The Team" subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. We'll add them as prose paragraphs under About the role. Now ensure we don't include boilerplate like "Amazon is an equal opportunity employer..." etc. Remove those lines. Also remove "Los Angeles County applicants:" etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (that's a link; maybe we can keep? It's a reference but could be considered boilerplate; but it's a link to benefits info. Might be considered part of Benefits? Might be okay to keep but it's a link; but we can drop as it's not substantive detail. Safer to drop. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10544056". Also remove "Application deadline: Sep 20, 2026". 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." Actually we need to keep the part about sign-on payments and RSUs (we already have in Benefits). The sentence about base salary range listed below we can keep as intro to Pay section maybe. But we can just list Pay. We need to preserve all substantive information: the sign-on payments and RSUs we have. The base salary range list we have. Now let's craft About the role paragraph(s). We'll combine: "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,