Sr. Cloud FinOps Engineer II (6798)

We need to output HTML fragment with sections: About the role? The posting includes description of role responsibilities etc. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions, cookie/navigation, etc. We need to preserve all substantive information. Let's parse content. Job description: "As Sr. Cloud FinOps Engineer II, design secure, scalable, and resilient cloud solutions for complex enterprise environments. You will lead Azure architecture decisions, automate infrastructure, strengthen cloud governance, and collaborate with engineering and security teams to modernize critical technology platforms." Then a paragraph about MetroStar people etc. Then "If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below!" That's fluff maybe not needed but it's not boilerplate? Might be considered filler but it's part of posting. However we can keep as part of About the role? Probably we can include that as part of About the role. Then "What you’ll do:" list of responsibilities. Then "What you’ll need to succeed:" list of requirements. Then "SALARY RANGE: $150,000.00 - $175,000.00" plus explanation. Then "Additional Compensation: ..." Then "Benefits: All full-time employees are eligible to participate in our benefits programs:" list. Then "Like we said, we are big fans of our people..." that's fluff but maybe part of benefits description. Then "Commitment to Non-Discrimination" etc - that's EEO boilerplate, remove. Then "What we want you to know: In compliance with federal law..." that's legal boilerplate, remove. Then "Not ready to apply now? Sign up to join our newsletter here." - application instruction, remove. Thus we need sections: - About the role: include introductory paragraph(s) about role and company mission maybe. - Responsibilities: list from "What you’ll do:" bullet points. - Requirements: from "What you’ll need to succeed:" bullet points. - Qualifications? Might be overlapping with Requirements. Could combine but we need separate sections only if content. Could treat Requirements as qualifications. But we have both Requirements and Qualifications headings; we need to decide if we have distinct content. The posting includes "What you’ll need to succeed:" which includes certifications, years experience, etc. That's qualifications. Could map to Qualifications. Requirements maybe could be skills? But we also have Skills heading. Could separate: Requirements = mandatory (clearance, cert, years experience). Qualifications = preferred? But not clearly separated. Safer to have one section: Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. The instruction says use headings for those categories if content exists. We can include all that have content. Let's extract: About the role: first paragraph(s) up to "If you think you can see yourself delivering our mission..." maybe include that as motivational but it's okay. Responsibilities: list under "What you’ll do:" each bullet. We need to preserve all substantive information: each bullet point. Let's list them: - Cloud Financial Management: Monitor, analyze, and forecast Azure cloud spending across subscriptions, resource groups, and mission workloads. Develop financial dashboards, executive reports, and cost allocation models that improve visibility and accountability. - Cost Optimization: Identify and implement opportunities to optimize Azure cloud costs through rightsizing, Azure Reservations, Savings Plans, storage lifecycle management, networking optimization, and resource lifecycle management while maintaining mission performance and reliability. - Cloud Governance: Develop and enforce Azure tagging standards, cost allocation strategies, governance policies, and budget controls using Azure Policy, Management Groups, RBAC, and Azure Cost Management to improve financial accountability and operational efficiency. - Cost Analytics & Reporting: Develop dashboards and reports using Power BI, Azure Cost Management, and Log Analytics to monitor cloud utilization, forecast spending, measure optimization efforts, and communicate financial performance to technical and executive stakeholders. - Automation & Engineering: Develop automation using PowerShell, Python, Azure CLI, Terraform, or Bicep to streamline cost reporting, tagging validation, resource lifecycle management, policy enforcement, and cloud optimization activities. - Architecture & Optimization Reviews: Collaborate with cloud architects and engineering teams to evaluate solution designs, identify cost optimization opportunities, and recommend Azure services that balance business, operational, and security requirements, security, scalability, and operational efficiency. (Note duplicate "security" maybe but keep.) - Cloud Operations Support: Analyze cloud utilization, investigate cost anomalies, monitor resource consumption, and provide recommendations to improve overall Azure platform performance and cost efficiency. - Migration & Modernization: Support cloud migration planning by developing cost estimates, evaluating modernization strategies, and identifying optimization opportunities throughout migration and operational lifecycle activities. - Stakeholder Collaboration: Partner with client stakeholders, cloud engineers, cybersecurity teams, finance organizations, and program leadership to integrate FinOps best practices into cloud operations, governance, and engineering processes. Now Requirements/Qualifications: from "What you’ll need to succeed:" bullet list. Let's extract each line: - Active Secret security clearance. - FinOps Certified Practitioner certification (preferred) or equivalent cloud financial management certification. - 8+ years of experience supporting enterprise cloud engineering, cloud architecture, or cloud operations, with a strong focus on Microsoft Azure environments. - 4+ years of experience with Azure Cost Management, cloud financial management, cloud governance, or FinOps practices. - Strong experience with Azure services, including Azure Cost Management, Azure Monitor, Azure Policy, Azure Reservations, Savings Plans, Virtual Machines, Storage Accounts, Azure SQL, Networking, and Azure Active Directory. - Experience developing cloud financial dashboards and reports using Power BI, Azure Monitor, Log Analytics, or similar analytics platforms. - Experience implementing Infrastructure as Code (Terraform, Bicep, or ARM Templates) and integrating governance controls into CI/CD pipelines. - Proficiency with PowerShell, Python, Azure CLI, or similar scripting languages used for cloud automation and reporting. - Strong understanding of Azure governance, resource tagging strategies, cost allocation models, budgeting, forecasting, and cloud financial optimization. - Excellent analytical, communication, and stakeholder engagement skills with the ability to present technical and financial recommendations to both engineering teams and executive leadership. Now Skills: Could be separate but we already have many skill items in requirements. Could still have Skills heading for things like "Proficiency with PowerShell, Python, Azure CLI" etc. But to avoid duplication, we could treat Requirements as qualifications and Skills as technical skills. However the instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section called Requirements (or Qualifications). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. We have About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. We don't have Schedule info. So we omit Schedule. We need to decide whether to have both Requirements and Qualifications. Since the posting lumps experience, certifications, etc. Could treat that as Qualifications. And Skills could be the technical proficiencies (PowerShell, Python, etc). But there is overlap. To avoid duplication, we could assign: - Qualifications: certifications, years of experience, clearance. - Skills: technical skills (Azure services, scripting, IaC, Power BI, etc). But the posting also includes "Strong understanding of Azure governance..." which could be skill. Let's split: Qualifications: - Active Secret security clearance. - FinOps Certified Practitioner certification (preferred) or equivalent cloud financial management certification. - 8+ years of experience supporting enterprise cloud engineering, cloud architecture, or cloud operations, with a strong focus on Microsoft Azure environments. - 4+ years of experience with Azure Cost Management, cloud financial management, cloud governance, or FinOps practices. Skills: - Strong experience with Azure services, including Azure Cost Management, Azure Monitor, Azure Policy, Azure Reservations, Savings Plans, Virtual Machines, Storage Accounts, Azure SQL, Networking, and Azure Active Directory. - Experience developing cloud financial dashboards and reports using Power BI, Azure Monitor, Log Analytics, or similar analytics platforms. - Experience implementing Infrastructure as Code (Terraform, Bicep, or ARM Templates) and integrating governance controls into CI/CD pipelines. - Proficiency with PowerShell, Python, Azure CLI, or similar scripting languages used for cloud automation and reporting. - Strong understanding of Azure governance, resource tagging strategies, cost allocation models, budgeting, forecasting, and cloud financial optimization. - Excellent analytical, communication, and stakeholder engagement skills with the ability to present technical and financial recommendations to both engineering teams and executive leadership. That seems reasonable. Now Benefits: list from "Benefits: All full-time employees are eligible to participate in our benefits programs:" then list items. Let's extract: - Health, dental, and vision insurance - 401(k) retirement plan with company match - Paid time off (PTO) and holidays - Parental Leave and dependent care - Flexible work arrangements - Professional development opportunities - Employee assistance and wellness programs Also preceding sentence: "Like we said, we are big fans of our people. That’s why we offer a generous benefits package, professional growth, and valuable time to recharge." That's fluff but could be included as part of Benefits section prose. We can include a short paragraph before list. Now Pay: Salary range and additional compensation details. We have: SALARY RANGE: $150,000.00 - $175,000.00 The salary range for this position is determined based on qualifications, skills, and relevant experience. The final salary offered will be determined based on several factors including: The candidate's professional background and relevant work experience; The specific responsibilities of the role and organizational needs; Internal equity and alignment with current team compensation. This role is also eligible for additional compensation, subject to the terms and policies of MetroStar, which may include: Performance-based bonuses; Company-paid training and/or certifications; Referral bonuses. Application Deadline: ... (remove). Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance. (some duplication). We'll keep substantive: salary range, factors, additional compensation types (performance-based bonuses, company-paid training/certifications, referral bonuses). Also mention eligibility for bonuses/incentives. We should not include application deadline. Now About the role: include the initial description and maybe the mission paragraph. Let's craft:

As Sr. Cloud FinOps Engineer II, design secure, scalable, and resilient cloud solutions for complex enterprise environments. You will lead Azure architecture decisions, automate infrastructure, strengthen cloud governance, and collaborate with engineering and security teams to modernize critical technology platforms.

We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers.

If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below!

That's okay. Now we need to output only HTML fragment, no markdown fences. We'll produce:

About the role

...

Responsibilities

• ...
...

Qualifications

• Active Secret security clearance.
• FinOps Certified Practitioner certification (preferred) or equivalent cloud financial management certification.
• 8+ years of experience supporting enterprise cloud engineering, cloud architecture, or cloud operations, with a strong focus on Microsoft Azure environments.
• 4+ years of experience with Azure Cost Management, cloud financial management, cloud governance, or FinOps practices.