Cloud FinOps Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About MetLife" maybe? The instruction: "Prefer a few substantive sections over many thin ones." We need to decide which sections to include based on content. We have content: The Opportunity (description) could be "About the role". Then "Key Responsibilities" -> Responsibilities. Then "Required Qualifications" and "Preferred Qualifications" -> maybe combine into Qualifications? Could separate Required and Preferred but we have only Qualifications heading. Could also have Skills heading for tools etc. But we have many skill mentions in qualifications. Could put them under Skills. However we must not invent sections with placeholder text. We need to include sections only when posting has real specific content. We have location expectation (hybrid 3 days/week) -> Schedule. Pay: salary range $75,000 - $90,000 plus possible short-term incentive. Benefits: described. So we have Pay, Schedule, Benefits. We also have "About MetLife" description but that's company overview; could be part of About the role? Might be considered boilerplate? It's not exactly boilerplate but it's generic company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About MetLife" is not those; it's company overview. Could be included under About the role or maybe separate section "About MetLife". But we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit company overview into About the role. Thus sections: - About the role: include the introductory paragraph about joining MetLife's Global Technology team, plus The Opportunity description (Cloud Business Office seeking...), plus maybe the MetLife overview? We'll incorporate. - Responsibilities: list from Key Responsibilities (Cloud Financial Management and FinOps, AI Agent Development and Automation, Cloud Governance and Business Office Operations). Use

• . - Qualifications: combine Required Qualifications and Preferred Qualifications? Could separate but we only have Qualifications heading. We'll list required and preferred as subpoints maybe using
  with notes. Must preserve all info. Could do two subheadings? Not allowed because only h3 headings allowed for those specific section names. Could we embed inside? Probably okay. We'll list required qualifications as bullet points, then preferred qualifications as bullet points preceded by "Preferred:" maybe. - Skills: maybe extract specific tools: Power BI, SQL, Python, PowerShell, APIs, workflow automation, low-code platforms, generative AI, LLMs, copilots, agent frameworks, prompts, tools, workflows, structured outputs, retrieval, orchestration, evaluation, human-in-the-loop controls, REST APIs, JSON, Git, CI/CD, data pipelines, cloud-native automation, IaC Terraform, etc. But many are already in qualifications. Might be redundant. Could omit Skills section to avoid thin sections. But we have skill details; maybe we can put them under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine qualifications and skills into Qualifications. Then we don't need Skills. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Check if we have content for each: - About the role: yes. - Responsibilities: yes. - Qualifications: yes (required + preferred). - Benefits: yes. - Pay: yes salary range. - Schedule: yes location expectation hybrid 3 days/week. We must not include sections with placeholder text like "commensurate with experience". Not present. Now produce HTML fragment: use

  for each heading, then content:

  for prose,

  • for lists. We need to preserve all substantive information; do not invent or summarize away detail. Must keep details like "Analyze cloud consumption, cost, utilization, budgets, forecasts, and financial trends to identify rightsizing, commitment, scheduling, waste-reduction, and architecture optimization opportunities." etc. We'll need to convert paragraphs into

    . For lists, each responsibility bullet becomes

  • . Ensure we don't lose any detail. Let's extract About the role content: Paragraph 1: "When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group dedicated to shaping the future of digital solutions for customers worldwide. You’ll develop, maintain and support technology applications and delivery, leveraging AI, automation, and contemporary ways of working to enhance experiences and drive business outcomes. Your work will simplify complex processes, improve tech resiliency, and ensure high-performing, seamless solutions that power life’s most important moments. In this dynamic environment, you’ll collaborate with talented peers across teams and functions, expanding your skills in impactful ways. Ready to push boundaries and set new industry standards? Join us and help drive the future of technology forward." Then "The Opportunity The Cloud Business Office is seeking a Cloud FinOps & AI Automation Analyst to help evolve the organization into a data-driven, automated Cloud Value Office. The role combines cloud financial management, data analytics, process optimization, and applied AI to improve cost efficiency, governance, operational effectiveness, customer experience, and value realization. Working across Finance, Technology, Cloud Engineering, application teams, product owners, and business stakeholders, this analyst will use cloud and financial data, APIs, automation, and AI to generate actionable insights and automate repeatable Cloud Business Office activities. The role governs, analyzes, optimizes, and demonstrates value from cloud investments; it does not build or operate the enterprise cloud platform." We can combine into one or two paragraphs. Now Responsibilities: three bullet areas each with sub-bullets? The text includes sentences with multiple responsibilities separated by periods. We'll treat each sentence as a bullet? Better to break into logical bullet points. From text: "Cloud Financial Management and FinOps Analyze cloud consumption, cost, utilization, budgets, forecasts, and financial trends to identify rightsizing, commitment, scheduling, waste-reduction, and architecture optimization opportunities. Develop forecasts, detect budget variances and anomalies, and support cost allocation, showback/chargeback, unit economics, and application or business-service cost analysis. Partner with application owners and engineering teams to convert consumption data into actionable recommendations, track opportunities through implementation, and validate realized savings, cost avoidance, efficiency gains, and business value." "AI Agent Development and Automation Identify, design, prototype, test, and maintain AI agents, workflow automations, APIs, and data integrations for repeatable Cloud Business Office activities. Build agents that use approved enterprise data, defined policies, and decision logic to generate recommendations and escalate matters requiring human judgment. Apply human-in-the-loop controls; evaluate accuracy, cost, reliability, explainability, and business value; and document each agent’s purpose, data sources, logic, controls, ownership, performance, and lifecycle." "Cloud Governance and Business Office Operations Support practical cloud financial and operational guardrails, including tagging, ownership, budget accountability, lifecycle management, financial controls, and optimization expectations. Partner with Cloud Engineering, Architecture, Security, Risk, Finance, Procurement, and application teams to strengthen governance while minimizing unnecessary friction. Support intake, triage, governance, FinOps, portfolio management, and value-realization processes; identify process bottlenecks, control gaps, manual work, and unnecessary handoffs for simplification or automation." We'll make each of these sentences as
  • . Could group under subheadings? Not allowed; only h3 headings for sections. We can keep as flat list. Now Qualifications: Required Qualifications bullet list: - Bachelor’s degree or equivalent practical experience in finance, technology, engineering, analytics, or a related discipline. - 1-3 years of overall related experience. - Experience in cloud financial management, FinOps, cloud governance, cloud engineering, technology finance, or a related field, with working knowledge of Azure, AWS, or Google Cloud. - Understanding of cloud pricing, consumption, commitments, billing, utilization, and operational datasets, with the ability to translate findings into business and technical recommendations. - Experience with data analysis and visualization tools, such as Power BI, and with SQL, Python, PowerShell, APIs, workflow automation, low-code platforms, or comparable technologies. - Hands-on experience applying generative AI, large language models, copilots, or agent frameworks, including prompts, tools, workflows, structured outputs, retrieval, orchestration, evaluation, and human-in-the-loop controls. - Strong analytical and communication skills, with the ability to work effectively across financial, business, and highly technical stakeholders. Preferred Qualifications bullet list: - FinOps certification or equivalent advanced FinOps experience, plus a cloud certification in Azure, AWS, or Google Cloud. - Experience with enterprise FinOps platforms, financial modeling, forecasting, business cases, or value-realization models. - Experience building enterprise-grade AI agents or AI-enabled workflows, including AI cost management and workload attribution. - Experience with REST APIs, JSON, Git, CI/CD, data pipelines, cloud-native automation, or infrastructure as code such as Terraform. - Experience in a Cloud Business Office, Cloud Center of Excellence, Cloud Value Office, Technology Business Management, or enterprise cloud governance organization. We'll combine into one list maybe with headings inside? Could use

    to label Required and Preferred then

    . But we must not invent headings beyond allowed. We can use

    for prose like "Required Qualifications:" then list. That's okay. Now Benefits: paragraph describing benefits. We'll keep as

    . Pay: sentence: "The expected salary range for this position is $75,000 - $90,000. This role may also be eligible for annual short-term incentive compensation. All incentives and benefits are subject to the applicable plan terms." We'll put in

    . Schedule: "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." We'll put in

    . Now ensure we removed boilerplate: EEO, accommodation, drug-free workplace, Massachusetts lie detector law, posting duration, etc. Also removed "About MetLife" company overview? We omitted that; but we might have lost some substantive info about MetLife being a leading financial services company etc. Is that considered substantive? It's generic but maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About MetLife" is not those; it's company description. Could be considered substantive? It's about the company, not the role. The instruction says we can include About the role section; we could incorporate that description there. It might be okay to include it in About the role. Let's add a sentence about MetLife being recognized etc. But we must not invent or summarize away detail. We'll include that as part of About the role after the opportunity description. Thus About the role will have: - Intro paragraph about joining MetLife's Global Technology team. - The Opportunity paragraph. - Then maybe a paragraph about MetLife: "Recognized on Fortune magazine's list of the "World's Most Admired Companies", Fortune World’s 25 Best Workplaces™, as well as the Fortune 100 Best Companies to Work For®, MetLife, through its subsidiaries and affiliates, is one of the world’s leading financial services companies; providing insurance, annuities, employee benefits and asset management to individual and institutional customers. With operations in more than 40 markets, we hold leading positions in the United States, Latin America, Asia, Europe, and the Middle East. As part of our New Frontier strategy, MetLife is building an AI-enabled, people-centered future. We’re looking for people who bring curiosity, adaptability, and a growth mindset as we use AI to enhance how we serve customers, support communities, and evolve the way work gets done. At MetLife, AI is a responsible partner