Senior Worldwide Specialist Solutions Architect, Containers, Application Modernization
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.
We need to decide which sections to include.
We have:
- Description (intro paragraph) – could be "About the role" maybe. The description paragraph: "Containers now run some of the most demanding systems on AWS...". That's about the role. So we can have
About the role
with containing that paragraph.
- Key job responsibilities: list of bullet points. So we can have
Responsibilities
with - each bullet.
- About The Team: paragraph(s). Could be "About the Team". Could be a section heading "About the Team". Not in given list but we can use? The instruction says use 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. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can still include "About the Team" maybe as part of About the role? However they said "Prefer a few substantive sections over many thin ones." Might combine team and AWS info into About the role? But they'd be separate substantive content.
We have "About The Team" and "About AWS". Could combine into "About the Team and AWS"? But better to follow given headings: maybe "About the role" includes description, team, AWS info? But that may be too much.
Alternatively we could create sections: About the role (description), Responsibilities, Qualifications (basic + preferred), Benefits (maybe from benefits paragraph), Pay (salary ranges). Also maybe "Skills" not present.
We have Basic Qualifications and Preferred Qualifications. Could combine into "Qualifications" with sub-sections? But we need to use - for any list. So we can list basic qualifications as
- ... and preferred as separate list maybe under same heading? Could have two
under same Qualifications
. That's okay.
Benefits: there is a paragraph describing benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs. So we can have Benefits section.
Pay: there is salary ranges per location. So we can have Pay section with maybe a listing ranges.
Schedule: not mentioned, so omit.
Skills: not explicit, maybe omitted.
Requirements: maybe same as Qualifications.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to ensure we don't include boilerplate like EEO, accommodation, etc. Also remove duplicated lines.
We must preserve all substantive information: description paragraph, responsibilities bullets, team paragraph, AWS paragraph, basic qualifications, preferred qualifications, benefits paragraph, salary ranges.
We need to avoid repeating job title. Not include Job ID.
We need to format as HTML fragment only.
Let's extract content.
Description paragraph:
"Containers now run some of the most demanding systems on AWS, from real-time payment processing to large-scale AI inference. As more companies move production workloads onto Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), AWS Fargate, and Amazon Elastic Container Registry (Amazon ECR), they face harder questions about scaling, cost, and security. They need architects who go deep. In this role you will help organizations worldwide answer those questions, and you will shape the container services they depend on. You will reach customers and partners primarily through scale: workshops, reusable content, and enablement that help many organizations at once. Through these motions you will work closely with customers and partners, learning their requirements firsthand and turning them into production-ready architectures. You will bring that real-world feedback and usage data to product teams to influence feature development and future roadmaps. As a strategic technical leader in the field, you will provide architectural guidance that accelerates partner engagements worldwide while guiding an internal community of container subject matter experts."
That's the description.
Key job responsibilities bullet list:
- Serve as a trusted technical advisor on containers, helping customers and partners design, build, and run production workloads on Amazon EKS, Amazon ECS, AWS Fargate, and Amazon ECR with a focus on security, cost efficiency, and reliability.
- Channel customer feedback and usage data to product teams to shape feature development and product roadmaps.
- As part of the container go-to-market team, apply deep technical expertise to unblock customers' largest and most critical business challenges.
- Guide and support an AWS internal community of technical subject matter experts aligned to the containers domain.
- Develop reference architectures, guides, and workshops as repeatable, practical resources that scale enablement across the field and partners.
About The Team paragraph:
"The Worldwide Specialist Organization (WWSO) is part of AWS Specialist and Partner Organization (ASP). Specialists own the end-to-end go-to-market strategy for their respective technology domains, providing the business and technical expertise to help our customers succeed. Partner teams own the strategy, recruiting, development, and growth of our key technology and consulting partners. Together they provide our customers with the expertise and scale needed to build innovative solutions for their most complex challenges. Container adoption on AWS continues to accelerate, and the team is focused on expanding reference architectures, partner integrations, and field enablement programs to meet that demand. You will join a collaborative, technically deep group where your work directly shapes how customers run their most important workloads."
About AWS paragraph(s):
There are multiple paragraphs: "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". We need to preserve all substantive information. Could combine into a single
or multiple
under About AWS heading? Since we don't have a heading for About AWS, maybe we incorporate into About the role? But we have limited headings. Could we add a section "About AWS"? Not in list but maybe allowed as it's substantive. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we can add other headings as needed. But they said "Prefer a few substantive sections over many thin ones." So maybe we should combine the AWS culture paragraphs into a single section like "About AWS". That's okay.
Thus we can have About AWS
with multiple
paragraphs covering Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance.
Basic Qualifications bullet list:
- 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience
- Knowledge of software development tools and methodologies
- Experience migrating or transforming legacy customer solutions to the cloud
Preferred Qualifications bullet list:
- 5+ years of infrastructure architecture, database architecture and networking experience
- Experience working with end user or developer communities
- Experience with presentations and speaking with executives, IT, management, and developers
Benefits paragraph:
"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 preserve the link? Probably keep as plain text.
Pay section: list salary ranges per location.
We have:
USA, CA, East Palo Alto - 176,600.00 - 239,000.00 USD annually
USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually
USA, GA, Atlanta - 153,600.00 - 207,800.00 USD annually
USA, IL, Chicago - 153,600.00 - 207,800.00 USD annually
USA, NY, New York - 169,000.00 - 228,600.00 USD annually
USA, TX, Austin - 153,600.00 - 207,800.00 USD annually
USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually
USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually
USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually
We can present as
- each line.
Company - Amazon Web Services, Inc. Job ID: A10562019 – we can drop Job ID, maybe include company as 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 could include a short
at end: "Amazon Web Services, Inc." maybe.
But we already have About AWS section; maybe we don't need separate company line. Could drop.
Now we need to output HTML fragment only.
Let's craft:
About the role
Containers now run some of the most demanding systems on AWS, from real-time payment processing to large-scale AI inference. As more companies move production workloads onto Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), AWS Fargate, and Amazon Elastic Container Registry (Amazon ECR), they face harder questions about scaling, cost, and security. They need architects who go deep. In this role you will help organizations worldwide answer those questions, and you will shape the container services they depend on. You will reach customers and partners primarily through scale: workshops, reusable content, and enablement that help many organizations at once. Through these motions you will work closely with customers and partners, learning their requirements firsthand and turning them into production-ready architectures. You will bring that real-world feedback and usage data to product teams to influence feature development and future roadmaps. As a strategic technical leader in the field, you will provide
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. We need to decide which sections to include. We have: - Description (intro paragraph) – could be "About the role" maybe. The description paragraph: "Containers now run some of the most demanding systems on AWS...". That's about the role. So we can have
About the role
withcontaining that paragraph. - Key job responsibilities: list of bullet points. So we can have
Responsibilities
with- each bullet.
- About The Team: paragraph(s). Could be "About the Team". Could be a section heading "About the Team". Not in given list but we can use? The instruction says use 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. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can still include "About the Team" maybe as part of About the role? However they said "Prefer a few substantive sections over many thin ones." Might combine team and AWS info into About the role? But they'd be separate substantive content. We have "About The Team" and "About AWS". Could combine into "About the Team and AWS"? But better to follow given headings: maybe "About the role" includes description, team, AWS info? But that may be too much. Alternatively we could create sections: About the role (description), Responsibilities, Qualifications (basic + preferred), Benefits (maybe from benefits paragraph), Pay (salary ranges). Also maybe "Skills" not present. We have Basic Qualifications and Preferred Qualifications. Could combine into "Qualifications" with sub-sections? But we need to use
- for any list. So we can list basic qualifications as
- ... and preferred as separate list maybe under same heading? Could have two
- under same
- each line.
Company - Amazon Web Services, Inc. Job ID: A10562019 – we can drop Job ID, maybe include company as 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 could include a short
at end: "Amazon Web Services, Inc." maybe. But we already have About AWS section; maybe we don't need separate company line. Could drop. Now we need to output HTML fragment only. Let's craft:
About the role
Containers now run some of the most demanding systems on AWS, from real-time payment processing to large-scale AI inference. As more companies move production workloads onto Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), AWS Fargate, and Amazon Elastic Container Registry (Amazon ECR), they face harder questions about scaling, cost, and security. They need architects who go deep. In this role you will help organizations worldwide answer those questions, and you will shape the container services they depend on. You will reach customers and partners primarily through scale: workshops, reusable content, and enablement that help many organizations at once. Through these motions you will work closely with customers and partners, learning their requirements firsthand and turning them into production-ready architectures. You will bring that real-world feedback and usage data to product teams to influence feature development and future roadmaps. As a strategic technical leader in the field, you will provide
Qualifications
. That's okay. Benefits: there is a paragraph describing benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs. So we can have Benefits section. Pay: there is salary ranges per location. So we can have Pay section with maybe alisting ranges. Schedule: not mentioned, so omit. Skills: not explicit, maybe omitted. Requirements: maybe same as Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to ensure we don't include boilerplate like EEO, accommodation, etc. Also remove duplicated lines. We must preserve all substantive information: description paragraph, responsibilities bullets, team paragraph, AWS paragraph, basic qualifications, preferred qualifications, benefits paragraph, salary ranges. We need to avoid repeating job title. Not include Job ID. We need to format as HTML fragment only. Let's extract content. Description paragraph: "Containers now run some of the most demanding systems on AWS, from real-time payment processing to large-scale AI inference. As more companies move production workloads onto Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), AWS Fargate, and Amazon Elastic Container Registry (Amazon ECR), they face harder questions about scaling, cost, and security. They need architects who go deep. In this role you will help organizations worldwide answer those questions, and you will shape the container services they depend on. You will reach customers and partners primarily through scale: workshops, reusable content, and enablement that help many organizations at once. Through these motions you will work closely with customers and partners, learning their requirements firsthand and turning them into production-ready architectures. You will bring that real-world feedback and usage data to product teams to influence feature development and future roadmaps. As a strategic technical leader in the field, you will provide architectural guidance that accelerates partner engagements worldwide while guiding an internal community of container subject matter experts." That's the description. Key job responsibilities bullet list: - Serve as a trusted technical advisor on containers, helping customers and partners design, build, and run production workloads on Amazon EKS, Amazon ECS, AWS Fargate, and Amazon ECR with a focus on security, cost efficiency, and reliability. - Channel customer feedback and usage data to product teams to shape feature development and product roadmaps. - As part of the container go-to-market team, apply deep technical expertise to unblock customers' largest and most critical business challenges. - Guide and support an AWS internal community of technical subject matter experts aligned to the containers domain. - Develop reference architectures, guides, and workshops as repeatable, practical resources that scale enablement across the field and partners. About The Team paragraph: "The Worldwide Specialist Organization (WWSO) is part of AWS Specialist and Partner Organization (ASP). Specialists own the end-to-end go-to-market strategy for their respective technology domains, providing the business and technical expertise to help our customers succeed. Partner teams own the strategy, recruiting, development, and growth of our key technology and consulting partners. Together they provide our customers with the expertise and scale needed to build innovative solutions for their most complex challenges. Container adoption on AWS continues to accelerate, and the team is focused on expanding reference architectures, partner integrations, and field enablement programs to meet that demand. You will join a collaborative, technically deep group where your work directly shapes how customers run their most important workloads." About AWS paragraph(s): There are multiple paragraphs: "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance". We need to preserve all substantive information. Could combine into a single
or multiple
under About AWS heading? Since we don't have a heading for About AWS, maybe we incorporate into About the role? But we have limited headings. Could we add a section "About AWS"? Not in list but maybe allowed as it's substantive. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive list. So we can add other headings as needed. But they said "Prefer a few substantive sections over many thin ones." So maybe we should combine the AWS culture paragraphs into a single section like "About AWS". That's okay. Thus we can have
About AWS
with multipleparagraphs covering Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Basic Qualifications bullet list: - 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - Knowledge of software development tools and methodologies - Experience migrating or transforming legacy customer solutions to the cloud Preferred Qualifications bullet list: - 5+ years of infrastructure architecture, database architecture and networking experience - Experience working with end user or developer communities - Experience with presentations and speaking with executives, IT, management, and developers Benefits paragraph: "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 preserve the link? Probably keep as plain text. Pay section: list salary ranges per location. We have: USA, CA, East Palo Alto - 176,600.00 - 239,000.00 USD annually USA, CA, San Francisco - 176,600.00 - 239,000.00 USD annually USA, GA, Atlanta - 153,600.00 - 207,800.00 USD annually USA, IL, Chicago - 153,600.00 - 207,800.00 USD annually USA, NY, New York - 169,000.00 - 228,600.00 USD annually USA, TX, Austin - 153,600.00 - 207,800.00 USD annually USA, TX, Dallas - 153,600.00 - 207,800.00 USD annually USA, VA, Arlington - 153,600.00 - 207,800.00 USD annually USA, WA, Seattle - 153,600.00 - 207,800.00 USD annually We can present as
- each line.
Company - Amazon Web Services, Inc. Job ID: A10562019 – we can drop Job ID, maybe include company as a short p? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
- ... and preferred as separate list maybe under same heading? Could have two
- for any list. So we can list basic qualifications as