Delivery Consultant - Application Modernization, AWS Professional Services
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
We have:
- Application deadline: Sep 23, 2026 (metadata)
- Description paragraph: "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. 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."
- "Key job responsibilities As an experienced technology professional, you will be responsible for:" then bullet list:
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
- "About The Team ABOUT AWS: Diverse Experiences ..." then paragraphs about AWS, work/life balance, inclusive team culture, mentorship and career growth.
- "10046 Basic Qualifications" then bullet 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
- "Preferred Qualifications" then bullet list:
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
- Then EEO statements etc (remove).
- Then Los Angeles County applicants: ... (some legal) remove.
- Then "Our inclusive culture empowers Amazonians..." (maybe part of earlier but we can keep as part of About the Team? It's duplicate of inclusive culture; but we can keep as part of About the Team.
- Then accommodation info (remove as legal/EEO? It's about disability accommodation; maybe considered EEO? Probably remove.
- Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." (application instruction) remove.
- Then "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. 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."
- Then list of locations with salary ranges.
Thus we have Pay info (salary ranges) and Benefits info (list of benefits). Also we have Schedule? Not mentioned. So we should include Pay and Benefits sections if they have real specific content. The posting does state salary ranges per location and benefits list. So we should include Pay and Benefits sections.
We also have About the role (maybe we can combine description and responsibilities? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have:
- About the role: could be the initial description paragraph(s) about role and team? Could be "About The Team" section.
- Responsibilities: the bullet list under "Key job responsibilities".
- Requirements: maybe Basic Qualifications? Or we could separate Requirements (basic) and Qualifications (preferred). The instruction includes Requirements and Qualifications as separate headings. We could put Basic Qualifications under Requirements, and Preferred Qualifications under Qualifications.
- Skills: maybe we could include some skills from preferred qualifications? But we already have Qualifications. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those that have real content. We have content for About the role (description), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. Skills maybe not needed separately; we could omit Skills if no specific skills section beyond qualifications. But we could treat some of the preferred qualifications as skills; but better to follow instruction: include a section only when posting has real, specific content for it. We have content for Skills? The posting mentions "Strong communication skills", "Experience with automation and scripting", "Knowledge of security and compliance standards", etc. Those could be considered skills. However we already have Qualifications covering them. To avoid thin sections, we could merge Skills into Qualifications or Requirements. But the instruction says we can use Skills heading if we have content. However we already have Qualifications; maybe we treat Qualifications as both basic and preferred, and not separate Skills. Let's decide to include: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay.
We need to avoid repeating job title as heading. So we won't put a heading for the job title.
We need to fold minor metadata like Application deadline and Job ID into a short
or drop it. We can include a short
at top: "
Application deadline: Sep 23, 2026
" maybe also include Job ID? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short or drop it. So we can include a
with both: "Application deadline: Sep 23, 2026 | Job ID: A10553846". Or separate lines.
We need to remove boilerplate like EEO, legal, accommodation, etc.
We need to preserve all substantive information: that includes the description paragraphs, responsibilities, basic qualifications, preferred qualifications, benefits, pay ranges per location, and maybe the "About The Team" content (diverse experiences, work/life balance, inclusive team culture, mentorship and career growth). That content could go under About the role or About The Team. We could put that under About the role (or About The Team). Since we have About the role heading, we can include the descriptive paragraphs about AWS, team culture, etc.
Thus structure:
Application deadline: Sep 23, 2026 | Job ID: A10553846
About the role
[combined description paragraphs about role, AWS ProServe, team, diverse experiences, work/life balance, inclusive team culture, mentorship and career growth]
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, 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
- 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
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Application deadline: Sep 23, 2026 (metadata) - Description paragraph: "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. 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." - "Key job responsibilities As an experienced technology professional, you will be responsible for:" then bullet list: 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 - "About The Team ABOUT AWS: Diverse Experiences ..." then paragraphs about AWS, work/life balance, inclusive team culture, mentorship and career growth. - "10046 Basic Qualifications" then bullet 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 - "Preferred Qualifications" then bullet list: 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 - Then EEO statements etc (remove). - Then Los Angeles County applicants: ... (some legal) remove. - Then "Our inclusive culture empowers Amazonians..." (maybe part of earlier but we can keep as part of About the Team? It's duplicate of inclusive culture; but we can keep as part of About the Team. - Then accommodation info (remove as legal/EEO? It's about disability accommodation; maybe considered EEO? Probably remove. - Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." (application instruction) remove. - Then "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. 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." - Then list of locations with salary ranges. Thus we have Pay info (salary ranges) and Benefits info (list of benefits). Also we have Schedule? Not mentioned. So we should include Pay and Benefits sections if they have real specific content. The posting does state salary ranges per location and benefits list. So we should include Pay and Benefits sections. We also have About the role (maybe we can combine description and responsibilities? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: could be the initial description paragraph(s) about role and team? Could be "About The Team" section. - Responsibilities: the bullet list under "Key job responsibilities". - Requirements: maybe Basic Qualifications? Or we could separate Requirements (basic) and Qualifications (preferred). The instruction includes Requirements and Qualifications as separate headings. We could put Basic Qualifications under Requirements, and Preferred Qualifications under Qualifications. - Skills: maybe we could include some skills from preferred qualifications? But we already have Qualifications. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those that have real content. We have content for About the role (description), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. Skills maybe not needed separately; we could omit Skills if no specific skills section beyond qualifications. But we could treat some of the preferred qualifications as skills; but better to follow instruction: include a section only when posting has real, specific content for it. We have content for Skills? The posting mentions "Strong communication skills", "Experience with automation and scripting", "Knowledge of security and compliance standards", etc. Those could be considered skills. However we already have Qualifications covering them. To avoid thin sections, we could merge Skills into Qualifications or Requirements. But the instruction says we can use Skills heading if we have content. However we already have Qualifications; maybe we treat Qualifications as both basic and preferred, and not separate Skills. Let's decide to include: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. We need to avoid repeating job title as heading. So we won't put a heading for the job title. We need to fold minor metadata like Application deadline and Job ID into a short
or drop it. We can include a short
at top: "
Application deadline: Sep 23, 2026
" maybe also include Job ID? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. So we can include a
with both: "Application deadline: Sep 23, 2026 | Job ID: A10553846". Or separate lines. We need to remove boilerplate like EEO, legal, accommodation, etc. We need to preserve all substantive information: that includes the description paragraphs, responsibilities, basic qualifications, preferred qualifications, benefits, pay ranges per location, and maybe the "About The Team" content (diverse experiences, work/life balance, inclusive team culture, mentorship and career growth). That content could go under About the role or About The Team. We could put that under About the role (or About The Team). Since we have About the role heading, we can include the descriptive paragraphs about AWS, team culture, etc. Thus structure:
Application deadline: Sep 23, 2026 | Job ID: A10553846
About the role
[combined description paragraphs about role, AWS ProServe, team, diverse experiences, work/life balance, inclusive team culture, mentorship and career growth]
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, 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
- 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