AWS Technical Architect

We need to output HTML fragment with sections: About the role? Actually we need to reformat job posting into clean semantic HTML. Use

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. The posting includes: - Intro about Accenture AWS Business Group (AABG) description. Could be "About the role" or "About the team". Probably "About the role" is appropriate. - "We are looking to expand our AWS Technical Architect team..." That's part of role description. - "The Work" section with bullet-like sentences (design and contribute..., support client pursuits..., participate..., collaborate..., stay current...). That's responsibilities. - "Here's What You Need" includes requirements: Minimum 5 years hands-on keyboard AWS experience, etc. Also includes required certifications, degree, bonus points, etc. That's qualifications/requirements. - "Compensation at Accenture varies..." includes Pay info: they give salary ranges per state. That's Pay section. - "Accenture offers a market competitive suite of benefits..." includes Benefits. - Travel may be required: "Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements." That's Schedule? Actually travel is not schedule; maybe we could put under "Schedule" but schedule typically refers to work schedule (full-time, part-time, remote). Not present. Travel could be under "Schedule" but not exactly. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. Travel is not schedule; but we could include a "Travel" subsection? Not among allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put travel under Schedule? Might be a stretch but maybe acceptable as schedule includes travel expectations. However they said never create Schedule section unless posting actually states them. The posting does mention travel may be required and amount varies. That's about travel, not schedule. But we could treat as Schedule? Might be okay. However we could also incorporate travel into Responsibilities or About the role. Safer to not create a Schedule section if not clearly schedule. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Travel is not schedule; but we could still include a short paragraph about travel under About the role or Responsibilities. Probably better to include travel in Responsibilities as a bullet. - There's also "Requesting an Accommodation", EEO statements, etc. Those are boilerplate to remove. - Also "Role Location Annual Salary Range" table with state ranges. That's Pay. - Benefits: medical, dental, vision, life, long-term disability, 401(k), bonus opportunities, paid holidays, paid time off. Also link to benefits. Thus sections: About the role (intro + team description), Responsibilities (The Work + travel), Requirements/Qualifications (Here's What You Need), Benefits, Pay. We might combine Requirements and Qualifications into one section? The instruction allows separate headings but we prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section called "Requirements". Or we could have "Requirements" and "Qualifications" separate but that's thin. Better to combine into "Requirements". Also "Skills" could be part of requirements. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

  for each section heading. Inside each section, use

  for prose,

  • for lists. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We must not include boilerplate like EEO, accommodation request, etc. Also remove duplicated lines. We need to include the intro paragraphs about Accenture AWS Business Group, etc. That's substantive. We need to include the "We are looking to expand..." paragraph. We need to include the "The Work" bullet points. We need to include the "Here's What You Need" requirements list. We need to include the benefits list. We need to include the pay table (state ranges). Could represent as a
    with each state line. We need to include the note about compensation varying depending on factors, and the anticipated posting date? That's metadata maybe minor; we could fold into a short

    or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. The posting includes: "We anticipate this job posting will be posted until 11/30/2026." That's minor metadata; we could include in a short

    under About the role or at end. Also "Compensation at Accenture varies depending on a wide array of factors..." is part of Pay section. We must not include the "Requesting an Accommodation", EEO statements, etc. We must not include the "See more information on our benefits here: U.S. Employee Benefits | Accenture" maybe we can keep as a link? It's part of benefits; we can keep as a

    with a link? The instruction says preserve ALL substantive information; we can keep the link as part of benefits paragraph. We must not include the "Learn more about Accenture's AWS capabilities: Accenture AWS Cloud Services" maybe that's part of intro; we can keep as a link. We need to output only HTML fragment. Let's craft. Structure:

    About the role

    We Are Accenture AWS Business Group (AABG) is part of Accenture Cloud First, Accenture’s industry-leading organization dedicated to helping clients achieve total enterprise reinvention through cloud, data, and artificial intelligence. With more than 141,000 cloud professionals and 124,000 cloud certifications across Accenture, Cloud First brings unmatched scale and expertise to some of the world’s most complex business and technology transformations. Within AABG, our AWS Practice brings together Accenture’s deepest AWS expertise, including more than 1,500 AWS-certified architects who serve as the AWS SWAT team for the most complex and innovative AWS engagements. As AWS’ deepest strategic partner in the ecosystem, AABG leverages cutting-edge engineering, high-performance computing (HPC), artificial intelligence (AI), machine learning (ML), and advanced data analytics to design, build, and deploy custom cloud-native applications and services. Our teams help clients rapidly prototype, scale, and productionize transformative solutions while accelerating their journey to modern, serverless, and cloud-native architectures. Joining AABG means working alongside some of the industry's top cloud practitioners to help the world’s leading organizations unlock new value and drive innovation at scale. Through our collaborative culture, unmatched client opportunities, and focus on continuous learning, you'll have the chance to grow your expertise, advance your career, and shape the future of cloud transformation. Learn more about Accenture's AWS capabilities: Accenture AWS Cloud Services

    But we need to ensure we don't invent URLs; we can just keep the text as is without link? The original says "Learn more about Accenture's AWS capabilities: Accenture AWS Cloud Services". It's not a URL but maybe a placeholder. We'll keep as plain text. Next section: Responsibilities.

    Responsibilities

    • Design and contribute to reusable Enterprise Cloud Architecture, Data & AI, Migration, and Agentic AI solution assets, including reference architectures, accelerators, frameworks, and proof-of-concept templates.
    • Support client pursuits and delivery through client presentations, solution workshops, demos, RFP/RFI responses, solution design, estimates, and technical guidance across cloud, data, analytics, machine learning, and generative AI.
    • Participate in architecture reviews and quality assessments, identifying risks and opportunities for improvement and providing recommendations to delivery teams.
    • Collaborate with AWS Partner sales, account teams, solution architects, and technology partners to support client solutions, business development, and delivery.
    • Stay current on emerging AWS and AI technologies and contribute to technical materials, solution approaches, and opportunities to apply new capabilities to client solutions.
    • Travel may be required for this role; the amount of travel will vary from 0 to 100% depending on business need and client requirements.
    Next: Requirements.

    Requirements

    • Minimum 5 years hands-on keyboard AWS experience, with deeper capabilities and interests in specific services, including cloud, enterprise networking, and AWS-specific services and technologies.
    • Must have hands-on AWS experience with at least 1 implementation and/or migration into AWS, preferably in an enterprise-scale environment.
    • Minimum 5 years of experience with core AWS platform architecture, including areas such as: Organizations, Account Design, VPC, Subnet, and segmentation strategies; CloudEndure, MGN, DataSync; Backup and Disaster Recovery approach and design; Environment and application automation; CloudFormation and third-party automation approaches; Network connectivity, Direct Connect, and VPN; AWS Cost Management and Optimization.
    • Minimum 4 years of proven scripting capability and the ability to develop AWS environments as code.
    • Minimum 1 year of experience with Automation/IAC solutions, such as CloudFormation, Terraform, Ansible, Puppet, Jenkins, etc.
    • Minimum required AWS certification must include AWS Certified Solutions Architect (Associate or Professional).
    • Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate’s Degree, must have minimum 6 years work experience)
    • Bonus points if you have a systems engineering or developer background with the ability to learn quickly and share knowledge with the broader team.
    • A mindset of automate everything, with experience demonstrating this.
    We might also include "We are looking to expand our AWS Technical Architect team with talented professionals who have a passion for driving growth, pre-sales, sales, and client delivery. The ideal candidate has hands-on AWS experience, a strong understanding of cloud architecture, and an interest in emerging technologies including AWS Agentic AI services." That's part of role description; could be included in About the role or Responsibilities. Probably better to include in About the role as part of intro. Let's add a paragraph after the intro about the team: "We are looking to expand our AWS Technical Architect team with talented professionals who have a passion for driving growth, pre-sales, sales, and client delivery. The ideal candidate has hands-on AWS experience, a strong understanding of cloud architecture, and an interest in emerging technologies including AWS Agentic AI services." We'll add that as a

    under About the role. Now Benefits.

    Benefits

    • Medical, dental, vision, life, and long-term disability coverage
    • 401(k) plan