Solutions Architect, Consumer Packaged Goods

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: EEO, accommodations, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to extract content. Let's parse description. First paragraph: "AWS Global Sales drives adoption..." This is about the role? It's description of team. Could be "About the role". Then later: "As a trusted customer advocate, the Solutions Architect will help Consumer Packaged Goods organizations..." That's responsibilities. Then "Key job responsibilities" list bullet points. Then "A day in the life" maybe part of responsibilities or about role. Then "About The Team" maybe about team. Then sections: "Why AWS?" etc. Those are benefits? Actually they talk about work/life balance, mentorship, diverse experiences, inclusive team culture. Those could be Benefits or maybe "About the team". The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have Basic Qualifications and Preferred Qualifications -> Requirements and Qualifications. Skills: maybe not explicit; we could infer from responsibilities? But we should not create a Skills section unless posting actually states them. There's no explicit "Skills" list. So we should omit Skills. Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also earlier: "Work/Life Balance", "Mentorship & Career Growth", "Diverse Experiences", "Inclusive Team Culture". Those are benefits/ culture. So we can include Benefits section with those items. Pay: The posting includes salary ranges for various locations. So we can include Pay section with those ranges. Schedule: Not mentioned. No schedule info. So omit Schedule. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. About the role: Could be the initial description plus maybe "About The Team"? Actually "About The Team" is separate heading but we could map to About the role? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content. We have content for About the role: The initial paragraphs describing AWS Global Sales, the team, mission. Also "About The Team" section could be considered About the role? Might be redundant. But we can include About the role with the description of the team and mission. Responsibilities: The "Key job responsibilities" bullet list plus maybe "A day in the life" narrative. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Benefits: Work/Life Balance, Mentorship & Career Growth, Diverse Experiences, Inclusive Team Culture, plus comprehensive benefits list. Pay: Salary ranges. We must not include filler like "commensurate with experience". Not present. We must output only HTML fragment, no /. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as given (or close). Must not omit details. Let's extract bullet points from "Key job responsibilities": - Drive success in building and migrating consumer goods applications onto AWS, including ERP, trade promotion systems, digital commerce platforms, supply chain solutions, and AI-powered data pipelines that enable autonomous decision-making. - Formulate and execute a technical strategy aligned to enterprise CPG customers' growth goals, with a deliberate focus on GenAI and Agentic AI adoption. - Educate customers on AWS's value for CPG workloads and lead architectural discussions to ensure solutions are designed for resilience, cost efficiency, and rapid innovation, including multi-agent systems and foundation model integrations tailored to CPG use cases. - Conduct enablement sessions covering GenAI-powered demand forecasting, agentic ERP exception handling, real-time supply chain analytics, and autonomous trade promotion optimization. - Capture and share best practices across the SA community, including reusable agentic AI frameworks and responsible AI governance patterns. - Author customer-facing publications such as whitepapers, blogs, and reference architectures emphasizing Agentic AI for CPG. - Build deep relationships with senior technical and executive stakeholders to accelerate their GenAI transformation journeys, and serve as a technical liaison advocating for consumer goods-specific product needs and roadmap priorities. We should keep each as

• . "A day in the life" paragraph: we can include as prose under Responsibilities maybe after the list, or as separate paragraph. It's substantive; we should preserve. Could be included as

  after the list. Now Requirements: Basic Qualifications: - 2+ years of design, implementation, or consulting in applications and infrastructures experience - 4+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience We need to keep as list. Preferred Qualifications: - Experience working within software development or Internet-related industries - Experience migrating or transforming legacy customer solutions to the cloud - Experience working with AWS technologies from a dev/ops perspective Now Benefits: We have several paragraphs: 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." 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." 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." 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." Then benefits list: "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 all that. Could combine into a

  list? The instruction: Use
  • for any list of duties/requirements/benefits. So we should turn benefits into list items. However the benefits paragraph includes a sentence with many items; we could split into list items: health insurance..., 401(k) matching, paid time off, parental leave. Also the earlier culture items could be list items as well. But we need to preserve all substantive information; we can keep them as prose if not a list? The instruction says use
    • for any list of duties/requirements/benefits. If we have a list, we should use
      . The benefits are enumerated; we can make a list. But we also have descriptive paragraphs about work-life balance etc. Those are not a list but prose; we can keep as

      . Thus Benefits section could have multiple

      for each culture aspect, then a

      for the tangible benefits. Pay: Salary ranges for multiple locations. We need to preserve all. Could present as
      list items each location with range. Schedule: none. Now About the role: We need to include the initial description plus maybe "About The Team". Let's combine. Initial description: "AWS Global Sales drives adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and grow. Our team empowers every customer by providing tailored service, compelling technology, and hands-on support. We take the time to understand each customer's unique challenges, from demand forecasting and trade promotion optimization to supply chain resilience and direct-to-consumer transformation, then build solutions that accelerate their outcomes. This customer-first approach is how we built the world's most adopted cloud. Join us and help us grow." Then "About The Team" heading content: "The Consumer Packaged Goods (CPG) Solutions Architecture team partners with some of the most innovative brands and manufacturers in the industry. We are builders and trusted advisors with deep expertise across commerce platforms, supply chain modernization, real-time analytics, and AI-driven personalization. We celebrate curiosity, share knowledge freely, and take pride in the impact we deliver for customers and the broader AWS community. If you are energized by the intersection of technology and consumer goods, this is the team for you. No two days look the same as a CPG Solutions Architect. Your morning might kick off with a customer architecture review, helping a global CPG brand design a peak-season scaling strategy on AWS. By midday, you are collaborating with your account team on a proposal for a manufacturer exploring Generative AI to reinvent how they connect with consumers. Afternoons bring deep-dive whiteboarding sessions, internal knowledge sharing, or contributing to a CPG reference architecture. You close the day connecting with a senior engineering leader, building the trust that turns customers into cloud advocates. And somewhere in between, you get to do genuinely cool things: building Agentic AI workflows that automate complex supply chain decisions, experimenting with the latest foundation models, and helping CPG leaders imagine what their business looks like when AI is woven into everything. It is fast, meaningful, and never boring." We could include that as part of About the role (maybe as prose). It's substantive. Thus About the role section will have two paragraphs: first paragraph (AWS Global Sales...), second paragraph (About The Team...). Could combine. Now we must not repeat job title. Not include Job ID. Now produce HTML. Structure:

      About the role

      ...

      ...

      Responsibilities

      • ...
      ...

      A day in the life ...

      Requirements

      • ...
      ...

      Qualifications

      • ...
      ...

      Benefits

      We value work-life harmony....

      We’re continuously raising our performance bar....

      AWS values diverse experiences....

      Here at AWS, it’s in our nature to learn and be curious....

      • 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
      • parental leave

      Learn more about our benefits at https://amazon.jobs/en/benefits

      But the instruction says use
      • for any list of duties/requirements/benefits. The link is not a list; it's okay as

        with anchor. Pay section:

        Pay