Senior Solutions Architect, Global Energy & Utilities

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. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the description. Key sections: - About the role: The description starts with "AWS is leading the next phase...". That's about the role. Could be "About the role". We'll put that as

About the role

then

with prose. - Responsibilities: "Key job responsibilities" bullet list. We'll list each as

• . - A day in the life: Could be part of responsibilities or separate? Might be considered responsibilities but we can include as part of responsibilities or separate section "A day in the life". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "A day in the life". So we should incorporate that content into Responsibilities (maybe as part of responsibilities). Or we could treat as part of Responsibilities. - About The Team: Could be part of About the role or maybe separate but not allowed heading. Could be included in About the role. - Basic Qualifications: That's qualifications. We'll put under

  Qualifications

  maybe also Requirements? The spec includes both Requirements and Qualifications headings. We need to decide what goes where. Typically Requirements = basic qualifications, Qualifications = preferred qualifications. We'll split: Requirements = Basic Qualifications; Qualifications = Preferred Qualifications. - Skills: Not explicitly listed but could be derived from responsibilities (model selection, fine-tuning, RAG, agentic workflows, MLOps, etc.) Could be a Skills section. We'll create a Skills section with bullet list of relevant skills. - Benefits: The description includes benefits paragraph: "Amazon also offers comprehensive benefits including health insurance...". Also mentions sign-on payments and RSUs. So we can include Benefits section. - Pay: The description includes salary range: "The base salary range for this position is listed below. ... USA, FL, Miami - 153,600.00 - 207,800.00 USD annually" and also virtual location. So we have Pay info. We'll include Pay section. - Schedule: Not mentioned. No schedule info. So we should NOT include Schedule section. We must not include placeholder text like "commensurate with experience". Not present. We need to ensure we don't repeat job title. Not include Job ID. We must remove boilerplate: EEO, accommodation link, etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "Learn more about our benefits at ..."? That's maybe boilerplate but it's a link to benefits; we might keep benefits description but drop the link? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not necessarily boilerplate but could be considered navigation? It's a link to learn more; might be considered application instruction? Safer to remove the link and just keep the benefits description. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Company - Amazon Web Services, Inc." maybe not needed. We need to preserve all substantive information: responsibilities, qualifications, benefits, pay, etc. Let's extract substantive prose. About the role: The first paragraph: "AWS is leading the next phase of AI adoption with energy customers and is seeking a hands-on Senior Solutions Architect focused on Generative AI. In this role, you will work directly with AWS energy customers to help them build, differentiate, and scale GenAI solutions on AWS that drive measurable outcomes and accelerate revenue growth. This role focuses on converting GenAI ambition into repeatable, scalable offerings that can be built once and delivered to many customers. If you are someone who has built and shipped GenAI solutions in real-world settings and can transfer that expertise to customers, we want to hear from you." We'll put that as

  . Responsibilities: List from "Key job responsibilities" bullet points: - Work directly with energy customers to architect GenAI solutions, going deep on model selection, fine-tuning strategies, retrieval-augmented generation (RAG) architectures, agentic workflows, and MLOps to deliver production-ready outcomes. - Develop go-to-market motions with the AWS energy team, creating reusable assets such as reference architectures, proofs of concept, and delivery accelerators that can be deployed across multiple customers. - Present technical strategies to customer leadership and C-level executives, translating complex GenAI concepts into clear business value and actionable roadmaps. - Create field enablement materials for the broader solutions architect community, helping them integrate GenAI solutions into customer architectures, and share best practices through blog posts, white papers, and public-speaking engagements at events like AWS Summit and AWS re:Invent. - Act as a technical liaison between customers and AWS product teams, translating customer feedback into clear requirements that drive product improvements. Also "A day in the life" details could be added as responsibilities but we can incorporate as part of responsibilities maybe as additional bullet? But we should not invent content; we can add as a paragraph under responsibilities describing typical day. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the "A day in the life" content somewhere. Since we don't have a specific heading for it, we could add it as a paragraph under Responsibilities (maybe after the bullet list) as prose. That would preserve it. Thus Responsibilities section will have

  • for the bullet points, then a

    for the day in the life description. Now Requirements (Basic Qualifications): List: - 8+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - 3+ years of design, implementation, or consulting in applications and infrastructures experience - 10+ years of IT development or implementation/consulting in the software or Internet industries experience We'll put as

    • . Qualifications (Preferred Qualifications): List: - 5+ years of infrastructure architecture, database architecture and networking experience - Experience working with end user or developer communities - Experience leading or developing high quality, enterprise scale software products using a structured system development lifecycle - Knowledge of AWS services, market segments, customer base and industry verticals - 5+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience Note there is duplication of the first bullet? Actually first bullet is 5+ years of infrastructure architecture..., second bullet experience working..., third bullet experience leading..., fourth bullet knowledge..., fifth bullet 5+ years of specific technology domain areas... (similar to first but different). We'll keep as listed. Skills: We need to create a Skills section with bullet list of relevant skills derived from responsibilities and qualifications. Must not invent? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Creating a Skills section could be considered summarizing, but we can extract explicit skills mentioned: model selection, fine-tuning strategies, retrieval-augmented generation (RAG) architectures, agentic workflows, MLOps, Go-to-market motions, creating reusable assets (reference architectures, proofs of concept, delivery accelerators), presenting technical strategies to leadership, translating GenAI concepts to business value, creating field enablement materials, sharing best practices via blog posts, white papers, public speaking, acting as technical liaison, translating customer feedback into requirements. Also infrastructure architecture, database architecture, networking, working with end user/developer communities, leading/developing enterprise scale software products, knowledge of AWS services, market segments, etc. We can list these as skills. This is not inventing; it's extracting from text. So we can create a Skills section with bullet list. Benefits: Extract: "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." We'll put as
      • for each benefit? Could be a paragraph. We'll do
        • for each distinct benefit: sign-on payments, RSUs, health insurance (medical, dental, vision, prescription, Basic Life & AD&D, 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 that final compensation based on experience etc. That's more about pay. Pay: Salary range: "The base salary range for this position is listed below. 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." Then location specifics: "USA, FL, Miami - 153,600.00 - 207,800.00 USD annually" and "USA, FL, Virtual Location - Florida - 153,600.00 - 207,800.00 USD annually". We'll include Pay section with those ranges. We should not include the sentence about "Your Amazon package will include sign-on payments and RSUs" in Pay? It's part of compensation but could be in Benefits. We'll keep sign-on payments and RSUs in Benefits as they are part of compensation package. Pay section will focus on base salary range. Schedule: Not present, so omit. Now ensure we don't include any boilerplate: remove EEO, accommodation link, etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." Remove that sentence. Also remove "Company - Amazon Web Services, Inc." and "Job ID: A10559802". Also remove "Amazon is an equal opportunity employer..." etc. Now produce HTML fragment. Structure:

          About the role

          ...

          Responsibilities

          • ...
          ...

          ...

          (day in the life)

          Requirements

          • ...
          ...

          Qualifications

          • ...
          ...

          Skills

          • ...
          ...

          Benefits

          • ...
          ...

          Pay

          ...

          maybe list ranges. We need to ensure we don't create empty sections. Now craft the content precisely. About the role paragraph: combine the first two sentences? Let's copy exactly: "AWS is leading the next phase of AI adoption with energy customers and is seeking a hands-on Senior Solutions Architect focused on Generative AI. In this role, you will work directly with AWS energy customers to help them build, differentiate, and scale GenAI solutions on AWS that drive measurable outcomes and accelerate revenue growth. This role focuses on converting GenAI ambition into repeatable, scalable offerings that can be built once and delivered to many customers. If you are someone who has built and shipped GenAI solutions in real-world settings and can transfer that expertise to customers, we want to hear from you." We'll keep as is. Responsibilities bullets: copy each bullet exactly as in text. Bullet 1: "Work directly with energy customers to architect GenAI solutions, going deep on model selection, fine-tuning strategies, retrieval-augmented generation (