Cloud FinOps Analyst
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading with filler placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting and decide which sections to include.
The posting includes:
- Intro paragraph about MetLife Global Technology team, description of role.
- "The Opportunity" paragraph describing Cloud FinOps & AI Automation Analyst role.
- "Key Responsibilities" with bullet-like sentences (though not bullet list but sentences separated by periods). We need to turn into
- list.
- "Required Qualifications" with bullet-like sentences.
- "Preferred Qualifications" bullet-like.
- "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." That's schedule info.
- "The expected salary range for this position is $75,000 - $90,000. This role may also be eligible for annual short-term incentive compensation." That's pay info.
- Benefits section: "Benefits We Offer Our U.S. benefits address holistic well-being..." etc.
- About MetLife paragraph.
- Then EEO boilerplate etc to remove.
We need to decide sections: Possibly "About the role" (intro + opportunity), "Responsibilities", "Qualifications" (maybe combine required and preferred?), "Benefits", "Pay", "Schedule". Could also have "Skills" but not explicit. The posting includes required qualifications (skills) and preferred qualifications. Could combine into "Qualifications" section with sublists? But rule: Use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. So we can have separate sections for Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. Also maybe "About the role" as a prose section.
We must not include sections with filler placeholder text. All sections have real content.
We must not repeat job title as heading. So no heading for "Cloud FinOps & AI Automation Analyst". Good.
We must not put Job ID/requisition numbers as headings (none present).
We must remove boilerplate: EEO, accommodation, drug-free workplace, Massachusetts lie detector law, posting duration, etc. Also remove "For more information regarding MetLife’s U.S. benefits, please click here." That's a link but we can keep the benefits description but remove the link instruction? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "please click here" is maybe navigation/link; we can remove that sentence. Also "About MetLife" paragraph is not boilerplate; it's substantive about company; we could include as "About MetLife" maybe under a heading? The instruction says use headings for sections like About the role, Responsibilities, etc. "About MetLife" is not in the list but could be considered "About the role"? Actually "About the role" is separate. There's no explicit heading for company overview, but we could include as a prose paragraph under maybe "About MetLife" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About the company. So we should not create a heading for About MetLife; we could incorporate that info into "About the role" prose or maybe drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the About MetLife paragraph somewhere. Since we cannot create a heading not in the list, we could put it under "About the role" as prose, or maybe under a generic
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to have other headings but they'd be non-standard. Safer to stick to those headings. So we can put the About MetLife paragraph inside the "About the role" section as prose.
Thus sections:
- About the role (intro + opportunity + maybe about MetLife)
- Responsibilities (Key Responsibilities)
- Qualifications (maybe combine Required and Preferred? Could separate into Required Qualifications and Preferred Qualifications but both are under Qualifications heading? The list includes Requirements and Qualifications as separate possible headings. Could use "Requirements" for required qualifications and "Qualifications" for preferred? Or "Skills" for skills. But we have both required and preferred qualifications. Could do:
Requirements
for required qualifications.
Qualifications
for preferred qualifications.
But the instruction list includes both Requirements and Qualifications as possible headings. So we can use them.
- Benefits
- Pay
- Schedule
We should not include Skills unless we have explicit skills list; we have skills within qualifications but we can keep under Requirements/Qualifications.
Now we need to format lists.
Responsibilities: The text is a paragraph with sentences separated by periods. We need to split into list items. Let's extract each responsibility:
From "Key Responsibilities":
"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 can treat each bullet line as a list item. Some lines have multiple sentences separated by semicolons; but we can keep as one
- containing the sentences.
Thus produce
- ...
for each.
Required Qualifications: 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."
Each line as - .
Preferred Qualifications:
"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."
Each as
- .
Benefits: The paragraph describing benefits. We'll keep as
maybe with
- for list? The benefits paragraph includes many items separated by commas. Could convert to list for clarity but not required. The instruction: Use
- for any list of duties/requirements/benefits. So we should turn benefits into a list. Let's extract benefit items:
From benefits paragraph:
"We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability.
We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching,
group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance,
as well as Employee Assistance Program (EAP) and digital mental health programs,
parental leave,
paid time off,
paid holidays,
volunteer time off,
tuition assistance and much more!"
Also earlier: "Our U.S. benefits address holistic well-being with programs for physical and mental health, financial wellness, and support for families."
We could treat each sentence as list item, or break down further. Simpler: make each sentence a
- . Also include the introductory sentence about holistic well-being as a
- . So list items:
- Our U.S. benefits address holistic well-being with programs for physical and mental health, financial wellness, and support for families.
- We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability.
- We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching.
- Group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance.
- As well as Employee Assistance Program (EAP) and digital mental health programs.
- Parental leave.
- Paid time off.
- Paid holidays.
- Volunteer time off.
- Tuition assistance and much more!
We could combine some but fine.
Pay: The expected salary range $75,000 - $90,000 and eligibility for annual short-term incentive compensation. We'll put as
maybe with
- ? It's not a list but could be
. The instruction: Use
- for any list of duties/requirements/benefits. Pay is not a list, so
.
Schedule: "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." We'll put as
.
About the role: combine intro paragraph, The Opportunity paragraph, and About MetLife paragraph (maybe trimmed). We'll produce
for each paragraph or combine into one
with multiple sentences? Better to keep separate
for readability.
We must not include boilerplate like EEO etc. Also remove "For more
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading with filler placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting and decide which sections to include. The posting includes: - Intro paragraph about MetLife Global Technology team, description of role. - "The Opportunity" paragraph describing Cloud FinOps & AI Automation Analyst role. - "Key Responsibilities" with bullet-like sentences (though not bullet list but sentences separated by periods). We need to turn into
- list.
- "Required Qualifications" with bullet-like sentences.
- "Preferred Qualifications" bullet-like.
- "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." That's schedule info.
- "The expected salary range for this position is $75,000 - $90,000. This role may also be eligible for annual short-term incentive compensation." That's pay info.
- Benefits section: "Benefits We Offer Our U.S. benefits address holistic well-being..." etc.
- About MetLife paragraph.
- Then EEO boilerplate etc to remove.
We need to decide sections: Possibly "About the role" (intro + opportunity), "Responsibilities", "Qualifications" (maybe combine required and preferred?), "Benefits", "Pay", "Schedule". Could also have "Skills" but not explicit. The posting includes required qualifications (skills) and preferred qualifications. Could combine into "Qualifications" section with sublists? But rule: Use
for section headings. Use
- for any list of duties/requirements/benefits, and
for prose. So we can have separate sections for Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. Also maybe "About the role" as a prose section. We must not include sections with filler placeholder text. All sections have real content. We must not repeat job title as heading. So no heading for "Cloud FinOps & AI Automation Analyst". Good. We must not put Job ID/requisition numbers as headings (none present). We must remove boilerplate: EEO, accommodation, drug-free workplace, Massachusetts lie detector law, posting duration, etc. Also remove "For more information regarding MetLife’s U.S. benefits, please click here." That's a link but we can keep the benefits description but remove the link instruction? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "please click here" is maybe navigation/link; we can remove that sentence. Also "About MetLife" paragraph is not boilerplate; it's substantive about company; we could include as "About MetLife" maybe under a heading? The instruction says use headings for sections like About the role, Responsibilities, etc. "About MetLife" is not in the list but could be considered "About the role"? Actually "About the role" is separate. There's no explicit heading for company overview, but we could include as a prose paragraph under maybe "About MetLife" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About the company. So we should not create a heading for About MetLife; we could incorporate that info into "About the role" prose or maybe drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the About MetLife paragraph somewhere. Since we cannot create a heading not in the list, we could put it under "About the role" as prose, or maybe under a generic
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to have other headings but they'd be non-standard. Safer to stick to those headings. So we can put the About MetLife paragraph inside the "About the role" section as prose. Thus sections: - About the role (intro + opportunity + maybe about MetLife) - Responsibilities (Key Responsibilities) - Qualifications (maybe combine Required and Preferred? Could separate into Required Qualifications and Preferred Qualifications but both are under Qualifications heading? The list includes Requirements and Qualifications as separate possible headings. Could use "Requirements" for required qualifications and "Qualifications" for preferred? Or "Skills" for skills. But we have both required and preferred qualifications. Could do:
Requirements
for required qualifications.Qualifications
for preferred qualifications. But the instruction list includes both Requirements and Qualifications as possible headings. So we can use them. - Benefits - Pay - Schedule We should not include Skills unless we have explicit skills list; we have skills within qualifications but we can keep under Requirements/Qualifications. Now we need to format lists. Responsibilities: The text is a paragraph with sentences separated by periods. We need to split into list items. Let's extract each responsibility: From "Key Responsibilities": "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 can treat each bullet line as a list item. Some lines have multiple sentences separated by semicolons; but we can keep as one - containing the sentences.
Thus produce
- ... for each. Required Qualifications: 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." Each line as
- . Preferred Qualifications: "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." Each as
- .
Benefits: The paragraph describing benefits. We'll keep as
maybe with
- for list? The benefits paragraph includes many items separated by commas. Could convert to list for clarity but not required. The instruction: Use
- for any list of duties/requirements/benefits. So we should turn benefits into a list. Let's extract benefit items: From benefits paragraph: "We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability. We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching, group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance, as well as Employee Assistance Program (EAP) and digital mental health programs, parental leave, paid time off, paid holidays, volunteer time off, tuition assistance and much more!" Also earlier: "Our U.S. benefits address holistic well-being with programs for physical and mental health, financial wellness, and support for families." We could treat each sentence as list item, or break down further. Simpler: make each sentence a
- . Also include the introductory sentence about holistic well-being as a
- . So list items:
- Our U.S. benefits address holistic well-being with programs for physical and mental health, financial wellness, and support for families.
- We offer a comprehensive health plan that includes medical/prescription drug and vision, dental insurance, and no-cost short- and long-term disability.
- We also provide company-paid life insurance and legal services, a retirement pension funded entirely by MetLife and 401(k) with employer matching.
- Group discounts on voluntary insurance products including auto and home, pet, critical illness, hospital indemnity, and accident insurance.
- As well as Employee Assistance Program (EAP) and digital mental health programs.
- Parental leave.
- Paid time off.
- Paid holidays.
- Volunteer time off.
- Tuition assistance and much more!
We could combine some but fine.
Pay: The expected salary range $75,000 - $90,000 and eligibility for annual short-term incentive compensation. We'll put as
maybe with
- ? It's not a list but could be
. The instruction: Use
- for any list of duties/requirements/benefits. Pay is not a list, so
. Schedule: "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." We'll put as
. About the role: combine intro paragraph, The Opportunity paragraph, and About MetLife paragraph (maybe trimmed). We'll produce
for each paragraph or combine into one
with multiple sentences? Better to keep separate
for readability. We must not include boilerplate like EEO etc. Also remove "For more
- for any list of duties/requirements/benefits. Pay is not a list, so
- ? It's not a list but could be
- for list? The benefits paragraph includes many items separated by commas. Could convert to list for clarity but not required. The instruction: Use
- for any list of duties/requirements/benefits, and