Senior Worldwide Specialist Solutions Architect, Containers, Application Modernization

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, duplicate lines, application instructions, EEO etc. Must not create sections with filler like "commensurate with experience". Must include Pay and Benefits only if posting actually states them. The posting includes salary ranges for various locations and mentions benefits: "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." So we have Pay info (salary ranges) and Benefits info. So we can include Pay and Benefits sections. Also we have "About the role" description: first paragraph about containers, role description. Also "Key job responsibilities" list. Also "About The Team". Also "About AWS" with subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those could be considered sections but we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instructions say use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. We need to map content accordingly. Thus: - About the role: include description of role (first paragraph maybe plus "As a strategic technical leader..." etc). Also maybe include "About The Team" and "About AWS"? Those could be considered part of About the role? But they are separate sections in posting. However we only allowed those headings; we could put them under About the role as prose. Or we could create multiple sections but only allowed headings list; we could still use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but likely they want only those headings. It also says "Prefer a few substantive sections over many thin ones." So we should combine into those sections. Thus we can have:

About the role

with paragraphs covering role description, team, AWS culture etc.

Responsibilities

with

• list from "Key job responsibilities".

  Requirements

  maybe combine Basic Qualifications and Preferred Qualifications? The instruction says Requirements and Qualifications separate. Could put Basic Qualifications under Requirements, Preferred under Qualifications. Or combine. We have Basic Qualifications: 5+ years of specific technology domain areas..., Knowledge of software development tools..., Experience migrating or transforming legacy customer solutions to the cloud. Preferred Qualifications: 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. We could put Requirements = Basic Qualifications, Qualifications = Preferred Qualifications. Skills: maybe not explicitly listed; we could omit if no specific skills beyond those. Could combine into Requirements/Qualifications. Benefits: list benefits. Pay: list salary ranges per location. Schedule: not mentioned; we should not include Schedule section because no specific content. Thus output HTML fragment with those sections. We must not include boilerplate like EEO, equal opportunity, scam warning, etc. Also remove duplicated lines, navigation, cookie, legal. Also remove "Los Angeles County applicants..." etc. Also remove "If you have a disability..." etc. Also remove "Company - Amazon Web Services, Inc. Job ID: A10562019". Also remove "The base salary range for this position is listed below." but we need to keep the salary ranges. We'll keep the ranges. We need to preserve all substantive information: so keep the description paragraphs, responsibilities list, team description, AWS description, basic qualifications, preferred qualifications, benefits list, pay ranges. We must not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep substance but can rephrase slightly as long as not summarizing away detail. Safer to copy sentences. Let's extract substantive paragraphs: First paragraph: "Description 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." Second paragraph: "Key job responsibilities 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." Third: "About The Team 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." Fourth: "About AWS Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying. Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses. Inclusive Team Culture Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (gender diversity) conferences, inspire us to never stop embracing our uniqueness. Mentorship & Career Growth We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional. Work/Life Balance We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve in the cloud." Fifth: "Basic Qualifications 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" Sixth: "Preferred Qualifications 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" Seventh: benefits and pay: "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 salary ranges list: "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 need to include Pay section with those ranges. Benefits section with benefits list. We should not include the "Learn more about our benefits at ..." link? That's maybe application instruction? It's a link to benefits; could be considered reference but not essential. Might keep as part of benefits description. Probably okay to keep. We must not include any boilerplate like EEO etc. Already removed. Now construct HTML:

  About the role

  ... (combined description paragraphs about role, team, AWS)

  We need to ensure we don't repeat content. We'll combine the description, About The Team, About AWS into one

  or multiple

  s. Use

  for prose. Then

  Responsibilities

  • items. Then

    Requirements

    • for Basic Qualifications. Then

      Qualifications

      • for Preferred Qualifications. Then

        Benefits