VP, Cloud Infrastructure Engineering Lead - GenAI

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "Job Overview", "Key Responsibilities", "What We’re Looking For", "Additional Preferred Qualifications", "At AIG, we value in-person collaboration..." (Schedule?), "Enjoy Benefits That Take Care Of What Matters" (Benefits), then more about AIG culture etc. We need to include sections only when posting has real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. We must not repeat job title as heading. No Job ID. We need to preserve all substantive info, no boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to decide which sections to include. Content: - Who We Are: description of AIG. Could be "About the role"? Actually "Who We Are" is about company, not role. Could fit under "About the role"? Probably "About the role" is more about the position. But we have "Job Overview". That could be "About the role". Use heading "About the role" for Job Overview paragraph. - Key Responsibilities: list bullet points. Use

• under heading "Responsibilities". - What We’re Looking For: list of requirements (10+ years experience etc). That's requirements/qualifications/skills. We need to split maybe into Requirements and Qualifications and Skills. But we can combine? The instruction: prefer a few substantive sections over many thin ones. So we could have one section "Requirements" covering the list. Or separate "Qualifications" for additional preferred qualifications. Let's see. We have "What We’re Looking For" bullet list (starting with 10+ years...). Then "Additional Preferred Qualifications" list (AWS certified etc). Then "At AIG, we value in-person collaboration..." that's schedule (in-office). Then "Enjoy Benefits That Take Care Of What Matters" benefits description. Thus sections: - About the role (Job Overview) - Responsibilities (Key Responsibilities) - Requirements (What We’re Looking For) - Qualifications (Additional Preferred Qualifications) maybe also include skills? Could combine Qualifications and Skills but we have separate headings available. Could put "Qualifications" for the additional preferred qualifications, and "Skills" maybe not needed if we already covered skills in requirements. But we need to avoid empty sections. If we don't have specific content for Skills, we should omit it. - Benefits (Enjoy Benefits That Take Care Of What Matters) - Schedule (At AIG, we value in-person collaboration...). This is about in-office requirement. Pay: not mentioned, so omit. Thus output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We need to use

  for each heading. Then content: for About the role, use

  with the Job Overview paragraph(s). For Responsibilities,

  • each bullet. For Requirements,
    • each bullet from What We’re Looking For. For Qualifications,
      • each bullet from Additional Preferred Qualifications. For Benefits,

        with the benefits paragraph(s). For Schedule,

        with the in-office collaboration paragraph. We must preserve all substantive info, not invent or summarize away detail. Ensure we keep all details from those sections. Let's extract text. Who We Are paragraph: "AIG is a leading global insurance organization providing a wide range of property casualty insurance and other financial services. We provide world-class products and expertise to businesses and individuals in approximately 190 countries and jurisdictions. At AIG, we’re reshaping how the world manages risk, and we’re inviting you to be a key part of that transformation. As our GenAI Cloud Engineer, you will have the opportunity to make a meaningful impact, leveraging and further developing your skills to guide groundbreaking AI initiatives. If you’re looking for a place to grow your career and where your contributions will shape the future, AIG is where you belong." But we are not using Who We Are as a section; maybe we incorporate into About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So About the role likely should contain description of the role, not company. But we have Job Overview which describes role. The Who We Are is company description; could be omitted? It's substantive info about company; but we might still include it under About the role? The heading is About the role, not About the company. However we could still include company info as part of About the role? Might be considered filler? The instruction: "Prefer a few substantive sections over many thin ones." Including company description under About the role may be okay as it's substantive. But the heading is About the role, not About the company. Might be misaligned but still acceptable? Better to follow the given headings strictly: About the role should contain role overview. So we should put Job Overview there. The Who We Are could be omitted? It's substantive but not about role. However we could incorporate it into About the role as a brief intro? Might be considered adding detail not requested but not prohibited. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep Who We Are info somewhere. If we omit it, we lose substantive info. So we need to include it somewhere. Could we create a section "About the company"? Not allowed headings list. But we could put it under About the role as a preamble? Might be okay. Alternatively, we could treat "Who We Are" as "About the role" albeit not perfect. The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive? It says use

        for section headings (e.g. About the role, Responsibilities...). Likely they expect those headings only. So we must fit all content into those headings. So we need to place Who We Are somewhere, maybe under About the role as an introductory paragraph before the role overview. That would still be under About the role heading. That seems acceptable. Thus About the role section will contain two paragraphs: Who We Are and Job Overview. Now Responsibilities: list bullet points from Key Responsibilities. Need to extract each bullet. Key Responsibilities text: "Cloud Strategy Development – Work alongside Head of Cloud Engineering & Architecture to design and implement a repeatable and scalabale Infrastructure strategy for GenAI infrastructure needs. This will involve working with Information Security, GenAI Engineers, Application and Data teams. Additionally, from an Operational perspective, working closely with FinOps and AIG Operations to support dedicate GenAI infrastructure needsArchitecture – Work closely with the Enterprise, Security and Cloud Architecture teams to develop the Architecture patterns for AI workloads ensuring security, performance and reliability and building repeatable infrastructure for Research, Test, Development and ProductionAI Model Implementation – Setup the AI models that need to be leveraged by the GenAI teams for their development work. Also provide solutions and alternatives as deemed necessary for the implementation. Setup and maintain AI Sandbox/ Research environment for model explorations, development and assessments Performance Optimization – Continuously Monitor and Optimize the cloud workloads to ensure optimal performance and cost-effectiveness of the solutions being implemented.Cloud Financial Management – Ensure cloud estimations, cloud cost transparency, and cost estimations are developed and managed in collaboration with the FinOps teamGenAI Explorations – Work with AIG GenAI delivery teams across Business or IT initiatives in the exploration phases, build phase and roll out phases to ensure fit for purpose and timely cloud infrastructure and platforms are made available." We need to split into separate bullets. The text uses dash and then description, but there are missing spaces. We'll parse: - Cloud Strategy Development – Work alongside Head of Cloud Engineering & Architecture to design and implement a repeatable and scalabale Infrastructure strategy for GenAI infrastructure needs. This will involve working with Information Security, GenAI Engineers, Application and Data teams. Additionally, from an Operational perspective, working closely with FinOps and AIG Operations to support dedicate GenAI infrastructure needs - Architecture – Work closely with the Enterprise, Security and Cloud Architecture teams to develop the Architecture patterns for AI workloads ensuring security, performance and reliability and building repeatable infrastructure for Research, Test, Development and Production - AI Model Implementation – Setup the AI models that need to be leveraged by the GenAI teams for their development work. Also provide solutions and alternatives as deemed necessary for the implementation. Setup and maintain AI Sandbox/ Research environment for model explorations, development and assessments - Performance Optimization – Continuously Monitor and Optimize the cloud workloads to ensure optimal performance and cost-effectiveness of the solutions being implemented. - Cloud Financial Management – Ensure cloud estimations, cloud cost transparency, and cost estimations are developed and managed in collaboration with the FinOps team - GenAI Explorations – Work with AIG GenAI delivery teams across Business or IT initiatives in the exploration phases, build phase and roll out phases to ensure fit for purpose and timely cloud infrastructure and platforms are made available. We'll keep as is. Now Requirements: What We’re Looking For bullet list: "10+ years of experience in Infrastructure management with 4+ years of Cloud experience Proficient in Cloud Platforms (primarily AWS) and related tools/services Strong understanding of the security postures needed for cloud implementation, with knowledge of enabling and setting up policy as code in Prisma Knowledge or experience with AWS Bedrock and associated LLMs OR Proficient in Terraform, and knowledge in Ansible platform Proficient with Microsoft platforms such as GitHub and knowledge in CoPilot, Amazon Q, Microsoft Co Pilot Knowledge in the software development lifecycle, with significant experience leading teams through Agile and DevSecOps processes, ideally in AWS and Python environments. Proficient in troubleshooting, issue resolution, and system monitoring, ensuring applications run smoothly in production environments." We'll make each line a

        . Now Qualifications: Additional Preferred Qualifications: "AWS certified FinOps certified Azure certified GenAI certified on any LLMs or platforms like Bedrock or CoPilot" Make

        each. Now Benefits: Enjoy Benefits That Take Care Of What Matters paragraph(s): "At AIG, our people are our greatest asset. We know how important it is to protect and invest in what’s most important to you. That is why we created our Total Rewards Program, a comprehensive benefits package that extends beyond time spent at work to offer benefits focused on your health, wellbeing and financial security—as well as your professional development—to bring peace of mind to you and your family." Then following paragraphs about Reimagining insurance... etc. Those are more about company culture, maybe also part of Benefits? But they are not benefits. However they are substantive. We need to place them somewhere. Could be under About the role? Or maybe we could create a section "About the company"? Not allowed. Could we put them under Benefits? Not appropriate. Could we put them under About the role as extra description? Might be okay. But we also have later paragraphs about culture, inclusion, EEO etc. Those are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The later paragraphs about culture, inclusion, EEO etc might be considered boilerplate? They are about culture and inclusion, maybe not boilerplate but could be considered part of company description. However they include EEO statement at the end: "AIG provides equal opportunity...". That is boilerplate to remove. Also the accommodation request line. So we need to remove EEO and accommodation lines. Also the earlier "We invest in our largest asset..." etc might be considered substantive? It's about culture and learning. Might be okay to keep as part of About the role or Benefits? But we already have Benefits section; we could add more paragraphs under Benefits about professional development etc. The Benefits paragraph already mentions professional development. The later paragraphs about continuous learning and development, culture of inclusion, ERGs, awards, etc. Could be considered part of Benefits or About