Solutions Architect, Consumer Packaged Goods

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 when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse description. Content: - Intro paragraph about AWS Global Sales etc. Could be "About the role" maybe? Actually "About the role" heading could contain description of role. The description includes: "As a trusted customer advocate, the Solutions Architect will help Consumer Packaged Goods organizations within the Retail, Restaurants and Consumer Goods (RRCG) vertical understand best practices around advanced cloud-based solutions, and how to migrate and modernize existing workloads to the cloud. You will have the opportunity to help shape and execute a strategy to build mindshare and broad adoption of AWS within enterprise CPG, with a specific focus on how Generative AI and Agentic AI are reshaping how CPG companies operate, compete, and serve consumers. The ability to connect technology with measurable business value is critical to a Solutions Architect. You should have a demonstrated ability to think strategically about business, products, and technical challenges unique to the CPG space, including revenue growth management, shopper personalization, intelligent supply chain, and AI-powered product innovation. As CPG companies move from piloting Gen AI to deploying autonomous agents across their value chains, you will help them navigate that shift with confidence and speed." That's about role. Then "Key job responsibilities" list bullet points. Then "A day in the life" paragraph. Then "About The Team" with subsections: Why AWS?, Work/Life Balance, Mentorship & Career Growth, Diverse Experiences, Inclusive Team Culture. Those could be under "About the team" maybe but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "About The Team" maybe to "About the role"? Or we could create separate sections not in list? 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 we should use those headings when appropriate. Probably we should stick to those headings only. So we need to map content to those headings. We have: - About the role: intro description of role (maybe combine with "A day in the life"? Could be separate but we can put both under About the role). Or we could have "About the role" and then "Responsibilities". "Requirements" could be Basic Qualifications. "Qualifications" could be Preferred Qualifications. "Skills" maybe not explicitly listed; we could omit if no specific skills list. "Benefits", "Pay", "Schedule": we have pay ranges and benefits description. So we can include Pay and Benefits sections. Schedule not mentioned, so omit. Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So responsibilities list, basic qualifications list, preferred qualifications list, benefits list. We need to use

  for prose. We must not include boilerplate like EEO, accommodation link, etc. Remove those. We must preserve all substantive info: include details about responsibilities, day in the life maybe as prose under About the role. Include About The Team details maybe as prose under About the role or maybe we could incorporate into About the role? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to include the About The Team content (Why AWS?, Work/Life Balance, Mentorship & Career Growth, Diverse Experiences, Inclusive Team Culture). Where to put? Could be under About the role as additional prose. Or we could create a separate section but not in allowed headings. But we could still include it as prose under About the role. That would preserve it. We also need to include the intro paragraph about AWS Global Sales drives adoption etc. That's also substantive. Thus About the role section will contain multiple paragraphs: intro, role description, day in the life, about the team subsections. We need to format as

  for prose. For subheadings inside About the role (like Why AWS?, Work/Life Balance, etc.) we cannot use headings because only allowed headings are the list; but we could still use or just keep as prose. Probably okay to keep as sentences. Now Responsibilities: list bullet points from "Key job responsibilities". We'll convert each sentence to

• . Requirements: Basic Qualifications bullet points: "2+ years of design, implementation, or consulting in applications and infrastructures experience" and "4+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience". We'll put as
• . Qualifications: Preferred Qualifications bullet points: "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". Also maybe "Amazon is an equal opportunity employer..." but that's boilerplate; remove. Benefits: list from benefits paragraph: 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. Also mention sign-on payments and RSUs? That's compensation not benefits. Benefits list as above. Pay: we have multiple location salary ranges. We need to include them. Could present as
  • each location range. Or as prose. Since it's a list, we can use
    . Schedule: not present, omit. We must not include Job ID, company name maybe? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include company name maybe as a short

    but not as heading. Could drop it. Probably drop. We must not include markdown fences. Now produce HTML fragment. Let's craft. not needed; just headings and content. We'll output:

    About the role

    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.

    As a trusted customer advocate, the Solutions Architect will help Consumer Packaged Goods organizations within the Retail, Restaurants and Consumer Goods (RRCG) vertical understand best practices around advanced cloud-based solutions, and how to migrate and modernize existing workloads to the cloud. You will have the opportunity to help shape and execute a strategy to build mindshare and broad adoption of AWS within enterprise CPG, with a specific focus on how Generative AI and Agentic AI are reshaping how CPG companies operate, compete, and serve consumers. The ability to connect technology with measurable business value is critical to a Solutions Architect. You should have a demonstrated ability to think strategically about business, products, and technical challenges unique to the CPG space, including revenue growth management, shopper personalization, intelligent supply chain, and AI-powered product innovation. As CPG companies move from piloting Gen AI to deploying autonomous agents across their value chains, you will help them navigate that shift with confidence and speed.

    A day in the life 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.

    About The Team 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. 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.

    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.