Delivery Consultant - Application Modernization, AWS Professional Services

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the description. Key parts: - Application deadline: Sep 23, 2026 (metadata, maybe include in a short p? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include deadline in a p maybe under a generic "About the role"? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an About the role section with prose summarizing role. - The description includes: "The Amazon Web Services Professional Services (ProServe) team is seeking a skilled Delivery Consultant – Application Modernization, 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 leader in driving customer success through their cloud journey, providing technical expertise and best practices throughout the project lifecycle. As a Delivery Consultant - Application Modernization, you will be proficient in leading the architecture of 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 applications, 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." That's role description. - Then "The AWS Professional Services organization is a global team of experts..." That's about the team maybe. - Then "Key job responsibilities As an experienced technology professional, you will be responsible for:" then bullet list (but not using

? Actually they list bullet points after colon: "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". Those are responsibilities. - Then "About The Team ABOUT AWS: Diverse Experiences ..." This is about the team and culture. Could be part of About the role or maybe a separate section? The instruction says we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put team/culture info under About the role. - Then "Basic Qualifications" list: "3+ years of cloud architecture and solution implementation experience Bachelor's degree in Computer Science, Engineering, a related field, or equivalent experience Experience delivering application architecture/design/modernization projects, including cloud-based solutioning (AWS or equivalent), with AI and automation Experience with Infrastructure as Code (IaC) tools and practices". Those are requirements/qualifications. - Then "Preferred Qualifications" list: many items. Those could be under Qualifications or Skills? The instruction: Use sections Requirements, Qualifications, Skills. We need to decide where to put each. Typically Basic Qualifications are requirements; Preferred Qualifications could be additional qualifications or skills. We could combine them into a Qualifications section (maybe split into Required and Preferred). But we must not create empty sections. We'll include a Qualifications section with both required and preferred items, maybe using
• . Or we could split into Requirements (basic) and Qualifications (preferred). But we have both sections available. Let's do: Requirements for basic qualifications, Qualifications for preferred qualifications. Skills could be derived from preferred qualifications like communication skills, automation, etc. But we might not need a separate Skills section if content overlaps. However we could extract skills like "Strong communication skills", "Knowledge of software engineering best practices", "Experience with automation and scripting", "Knowledge of security and compliance standards". Those could go under Skills. Better: Use Requirements for basic qualifications, Qualifications for preferred qualifications, Skills for specific skill items (communication, automation, security). But we must avoid duplication. Let's see. Preferred qualifications list includes: - Knowledge of software engineering best practices across the development life cycle, including agile methodologies, coding standards, code reviews, source management, build processes, testing, and operations - Strong communication skills with the ability to explain technical concepts to both technical and non-technical audiences - Experience delivering large-scale software development and modernization initiatives, with deep expertise in multiple programming languages (e.g. Java, Python, C++, JavaScript, Microservices) and Generative AI tools/technologies - 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 security and compliance standards including HIPAA and GDPR We could put these under Qualifications (preferred). Or we could split: some are skills (communication, automation, security). But the instruction says prefer a few substantive sections over many thin ones. So maybe we just have Requirements (basic) and Qualifications (preferred) and maybe Skills not needed. However we have also Benefits, Pay, Schedule sections if present. Benefits: The description includes: "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." Thus we have benefits content. Pay: The description includes salary ranges for various locations: "USA, CA, San Francisco - 151,000.00 - 204,300.00 USD annually" etc. So we have pay info. Schedule: Not mentioned. No schedule info (like full-time, part-time). So we should not create a Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract. About the role: combine initial paragraphs and team description. We'll produce:

  About the role

  The Amazon Web Services Professional Services (ProServe) team is seeking a skilled Delivery Consultant – Application Modernization to join AWS. In this role, you'll work closely with customers to design, implement, and manage AWS solutions that meet technical requirements and business objectives, driving customer success through their cloud journey. You'll lead the architecture of complex, scalable, and secure solutions, gather requirements, assess current applications, propose migration strategies, and act as a trusted advisor on industry trends, emerging technologies, and innovative solutions. You'll oversee implementation, ensure best‑practice adherence, optimize performance, and manage risks throughout the project lifecycle. The AWS Professional Services organization is a global team of experts helping customers achieve desired business outcomes on AWS, working with customer teams and the AWS Partner Network to execute enterprise cloud initiatives and providing guidance through global specialty practices.

  That seems to capture. Responsibilities: list bullet points.

  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 (basic qualifications):

  Requirements

  • 3+ years of cloud architecture and solution implementation experience
  • Bachelor's degree in Computer Science, Engineering, a related field, or equivalent experience
  • Experience delivering application architecture/design/modernization projects, including cloud‑based solutioning (AWS or equivalent), with AI and automation
  • Experience with Infrastructure as Code (IaC) tools and practices
  Qualifications (preferred qualifications):

  Qualifications

  • Knowledge of software engineering best practices across the development life cycle, including agile methodologies, coding standards, code reviews, source management, build processes, testing, and operations
  • Strong communication skills with the ability to explain technical concepts to both technical and non‑technical audiences
  • Experience delivering large‑scale software development and modernization initiatives, with deep expertise in multiple programming languages (e.g., Java, Python, C++, JavaScript, Microservices) and Generative AI tools/technologies
  • 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 security and compliance standards including HIPAA and GDPR
  Benefits:

  Benefits

  • Sign‑on payments and restricted stock units (RSUs)
  • Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D, optional 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
  Pay: We need to include salary ranges for multiple locations. Could present as a list.

  Pay

  • San Francisco, CA: $151,000 – $204,300 USD annually
  • Denver, CO: $131,300 – $177,600 USD annually
  • Atlanta, GA: $131,300 – $177,600 USD annually
  • Chicago, IL: $131,300 – $177,600 USD annually
  • New York, NY: $144,500 – $195,400 USD annually
  • Austin, TX: $131,300 – $177,600 USD annually
  • Dallas, TX: $131,300 – $177,600 USD annually
  • Houston, TX: $131,300 – $177,600 USD annually
  • Arlington, VA: $131,300 – $177,600 USD annually
  • Bellevue, WA: $131,300 – $177,600 USD annually
  We should not include