Senior Platform Engineer - Cloud Native Engineering (Azure FinOps)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. The posting includes: - Overview (first paragraph about sponsorship, SME, Azure, etc.) - Responsibilities (list) - Qualifications (list) - Desired Qualifications (list) - Hours (Monday - Friday, 8:00AM - 4:30PM) - Locations (list of addresses) - About Us (company description) - Additional sections like Benefits? Not explicitly stated. There's mention of "highly competitive pay and generous benefits and perks" but no specifics. So we should not create Benefits section because no specific benefits listed. Pay not specified. Schedule we have hours: Monday-Friday 8:00AM-4:30PM. That is schedule info. So we can include a Schedule section with that content. We also have location info; could be part of Overview or separate? There's no explicit heading for Locations but we could include as a short p under Overview or separate? The instruction: "Prefer a few substantive sections over many thin ones." Could combine location and hours into Overview? But we have separate headings for Schedule and maybe Location not a standard heading. Could include location as part of Overview paragraph. We need to avoid duplication. The posting includes "Hours Additional Information Monday - Friday, 8:00AM - 4:30PM Locations: ...". So we can extract schedule and location. We need to remove boilerplate: EEO, accommodations, disclaimers, scam warnings, Bank Secrecy Act, etc. Also remove duplicated lines. We need to preserve all substantive information: overview, responsibilities, qualifications, desired qualifications, schedule, locations, about us. We need to format with
headings and appropriate content: - for lists,
for prose.
We need to decide headings: Could use "Overview", "Responsibilities", "Qualifications", "Desired Qualifications", "Schedule", "About Us". Possibly also "Location" but we can embed location in Schedule or Overview.
But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It gives examples but not strict; we can use those headings if appropriate. "Overview" maybe similar to "About the role". Could use "About the role" as heading for overview. But the posting already has "Overview". Might be okay to use "Overview". 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 suggests those. Safer to use those exact headings where applicable. Let's map:
- Overview -> could be "About the role"
- Responsibilities -> "Responsibilities"
- Qualifications -> "Qualifications"
- Desired Qualifications -> maybe "Skills" or "Preferred Qualifications". But we have "Desired Qualifications". Could treat as "Skills". However we should not invent headings if not matching content? The instruction says use those headings for section headings (e.g...). It doesn't say we cannot use other headings, but we should follow the spirit. I'd use "Qualifications" for required qualifications, and maybe "Preferred Qualifications" for desired. But "Preferred Qualifications" not in list. Could use "Skills" for desired qualifications (since they are skills/certs). Might be okay.
- Schedule -> "Schedule"
- About Us -> maybe "About the company"? Not in list. Could use "About the role" already used. Could just not include About Us? But we need to preserve substantive information. Could include as a
under Overview or separate section with heading "About the company". The instruction didn't forbid other headings, just gave examples. I'd include a heading "About the company" as
.
- Location: Could embed in Schedule section as a
after schedule.
We must not include filler like "commensurate with experience". Not present.
We need to remove any duplicated lines.
Let's extract content.
Overview paragraph(s):
"Navy Federal Credit Union currently does not provide sponsorship for this role. Applicants must be authorized to work in the United States without the need for current or future sponsorship. The successful candidate will be a subject matter expert with hands-on experience in cloud technologies, tools, and methodologies, with a particular focus on Microsoft Azure. This role is suited for an experienced Senior Platform Engineer with deep expertise in Cloud FinOps, especially in Azure cost optimization and billing administration. The engineer will serve as the sole FinOps expert within the Cloud Native Engineering group and will be responsible for driving financial accountability and efficiency across cloud operations. Cloud Native Engineering fosters a collaborative environment and is building a best-in-class cloud platform that supports scalable, secure, and cost-effective solutions across the enterprise."
That's overview.
Responsibilities list:
- Lead FinOps strategy and execution for Azure cloud, including cost forecasting, budgeting, and optimization.
- Own and manage Azure billing administration tasks such as reservation purchases, compute savings plans, and cost allocation.
- Develop and maintain tooling and dashboards to monitor cloud spend and identify savings opportunities.
- Collaborate with engineering, finance, and procurement teams across geographies to align cloud usage with business goals.
- Provide guidance and training to teams on cloud cost management best practices.
- Analyze usage patterns and recommend architectural changes to improve cost efficiency.
- Ensure compliance with internal financial policies and external regulatory requirements.
- Contribute to platform engineering initiatives, including automation, infrastructure as code, and cloud governance.
- Actively participate in Cloud Native Engineering’s roadmap planning and execution.
- Manage relationships with cloud vendors, including Microsoft and third-party FinOps tooling providers, to ensure optimal service delivery, contract alignment, and cost efficiency.
Qualifications list:
- Bachelor’s degree in Computer Science, Information Technology, Finance, or a related field.
- 5+ years of experience in cloud engineering, with at least 3 years focused on Azure FinOps or cloud cost management.
- Proven experience managing Azure rate optimization techniques including reservations, savings plans, and cost analysis.
- Strong understanding of Azure services, pricing models, and usage optimization techniques including but not limited to right-sizing, automated decommissioning, and automated shutdowns.
- Experience with Azure Cost Management + Billing, Azure Advisor, and third-party FinOps tools.
- Familiarity with Infrastructure-as-Code tools such as ARM templates, Bicep, or Terraform.
- Excellent collaboration and communication skills across technical and non-technical teams.
- Ability to work independently and drive initiatives as the sole FinOps expert.
- Strong analytical and problem-solving skills.
Desired Qualifications list:
- FinOps Certified Practitioner or similar certification.
- Experience in financial operations within large-scale enterprise cloud environments.
- Knowledge of Microsoft Defender for Cloud, Azure Policy, and Identity Governance.
- Expertise with scripting languages such as PowerShell or Python.
- Familiarity with Azure DevOps, CI/CD pipelines, and cloud governance frameworks.
- Exposure to data platforms such as Azure Synapse, Databricks, or Microsoft Fabric.
Hours: Monday - Friday, 8:00AM - 4:30PM
Locations:
- 820 Follin Lane, Vienna, VA 22180
- 5510 Heritage Oaks Drive, Pensacola, FL 32526
- 141 Security Drive, Winchester, VA 22602
About Us paragraph:
"Navy Federal provides much more than a job. We provide a meaningful career experience, including a culture that is energized, engaged and committed; and fierce appreciation for our teams, who are rewarded with highly competitive pay and generous benefits and perks. Our approach to careers is simple yet powerful: Make our mission your passion. FORTUNE 100 Best Companies to Work For® 2026 Yello and WayUp Top 100 Internship Programs 2025 Computerworld® Best Places to Work in IT 2026 Most Loved Workplace – America’s Top Most Loved Workplaces® 2025 2025 PEOPLE® Companies That Care Newsweek Most Trustworthy Companies in America 2026 Military Times 2025 Best for Vets Employers Forbes® 2026 America's Best Large Employers Forbes® 2025 America's Best Employers for New Grads Forbes® 2025 America's Best Employers for Tech Workers 2025 RippleMatch Campus Forward Award Winner for Overall Excellence Military.com Top Military Spouse Employers 2025 2026 Handshake Early Talent Award Newsweek America’s Greatest Workplaces for Culture, Belonging and Community 2026 From Fortune Magazine. © 2026 Fortune Media IP Limited. All rights reserved. Used under license. Fortune and Fortune 100 Best Companies to Work For are registered trademarks of Fortune Media IP Limited and are used under license. Fortune Magazine, Fortune Media (USA) Corporation, and its affiliates are not affiliated with, and do not endorse products or services of, Navy Federal Credit Union."
We need to remove the trademark/legal boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The About Us includes some trademark statements that might be considered legal boilerplate. Should we remove those lines? The About Us includes copyright and trademark statements. Likely we should remove them as they are legal boilerplate. Keep the descriptive part about Navy Federal providing meaningful career experience, culture, awards, etc. The trademark lines are likely legal. So we strip:
"From Fortune Magazine. © 2026 Fortune Media IP Limited. All rights reserved. Used under license. Fortune and Fortune 100 Best Companies to Work For are registered trademarks of Fortune Media IP Limited and are used under license. Fortune Magazine, Fortune Media (USA) Corporation, and its affiliates are not affiliated with, and do not endorse products or services of, Navy Federal Credit Union."
We can keep the rest up to "Newsweek America’s Greatest Workplaces for Culture, Belonging and Community 2026". That seems like substantive awards.
Thus About Us section will be a paragraph with that content.
Now schedule and location: We'll create a Schedule section with the hours and location list.
We need to avoid creating Pay/Benefits sections because not specified.
Now produce HTML fragment.
Structure:
About the role
Overview paragraph(s)
Responsibilities
- ...
...
Qualifications
- ...
...
Skills
(for Desired Qualifications)
- ...
...
Schedule
Monday - Friday, 8:00AM - 4:30PM
- 820 Follin Lane, Vienna, VA 22180
- 5510 Heritage Oaks Drive, Pensacola, FL 3
for prose. We need to decide headings: Could use "Overview", "Responsibilities", "Qualifications", "Desired Qualifications", "Schedule", "About Us". Possibly also "Location" but we can embed location in Schedule or Overview. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It gives examples but not strict; we can use those headings if appropriate. "Overview" maybe similar to "About the role". Could use "About the role" as heading for overview. But the posting already has "Overview". Might be okay to use "Overview". 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 suggests those. Safer to use those exact headings where applicable. Let's map: - Overview -> could be "About the role" - Responsibilities -> "Responsibilities" - Qualifications -> "Qualifications" - Desired Qualifications -> maybe "Skills" or "Preferred Qualifications". But we have "Desired Qualifications". Could treat as "Skills". However we should not invent headings if not matching content? The instruction says use those headings for section headings (e.g...). It doesn't say we cannot use other headings, but we should follow the spirit. I'd use "Qualifications" for required qualifications, and maybe "Preferred Qualifications" for desired. But "Preferred Qualifications" not in list. Could use "Skills" for desired qualifications (since they are skills/certs). Might be okay. - Schedule -> "Schedule" - About Us -> maybe "About the company"? Not in list. Could use "About the role" already used. Could just not include About Us? But we need to preserve substantive information. Could include as a
under Overview or separate section with heading "About the company". The instruction didn't forbid other headings, just gave examples. I'd include a heading "About the company" as
. - Location: Could embed in Schedule section as a
after schedule. We must not include filler like "commensurate with experience". Not present. We need to remove any duplicated lines. Let's extract content. Overview paragraph(s): "Navy Federal Credit Union currently does not provide sponsorship for this role. Applicants must be authorized to work in the United States without the need for current or future sponsorship. The successful candidate will be a subject matter expert with hands-on experience in cloud technologies, tools, and methodologies, with a particular focus on Microsoft Azure. This role is suited for an experienced Senior Platform Engineer with deep expertise in Cloud FinOps, especially in Azure cost optimization and billing administration. The engineer will serve as the sole FinOps expert within the Cloud Native Engineering group and will be responsible for driving financial accountability and efficiency across cloud operations. Cloud Native Engineering fosters a collaborative environment and is building a best-in-class cloud platform that supports scalable, secure, and cost-effective solutions across the enterprise." That's overview. Responsibilities list: - Lead FinOps strategy and execution for Azure cloud, including cost forecasting, budgeting, and optimization. - Own and manage Azure billing administration tasks such as reservation purchases, compute savings plans, and cost allocation. - Develop and maintain tooling and dashboards to monitor cloud spend and identify savings opportunities. - Collaborate with engineering, finance, and procurement teams across geographies to align cloud usage with business goals. - Provide guidance and training to teams on cloud cost management best practices. - Analyze usage patterns and recommend architectural changes to improve cost efficiency. - Ensure compliance with internal financial policies and external regulatory requirements. - Contribute to platform engineering initiatives, including automation, infrastructure as code, and cloud governance. - Actively participate in Cloud Native Engineering’s roadmap planning and execution. - Manage relationships with cloud vendors, including Microsoft and third-party FinOps tooling providers, to ensure optimal service delivery, contract alignment, and cost efficiency. Qualifications list: - Bachelor’s degree in Computer Science, Information Technology, Finance, or a related field. - 5+ years of experience in cloud engineering, with at least 3 years focused on Azure FinOps or cloud cost management. - Proven experience managing Azure rate optimization techniques including reservations, savings plans, and cost analysis. - Strong understanding of Azure services, pricing models, and usage optimization techniques including but not limited to right-sizing, automated decommissioning, and automated shutdowns. - Experience with Azure Cost Management + Billing, Azure Advisor, and third-party FinOps tools. - Familiarity with Infrastructure-as-Code tools such as ARM templates, Bicep, or Terraform. - Excellent collaboration and communication skills across technical and non-technical teams. - Ability to work independently and drive initiatives as the sole FinOps expert. - Strong analytical and problem-solving skills. Desired Qualifications list: - FinOps Certified Practitioner or similar certification. - Experience in financial operations within large-scale enterprise cloud environments. - Knowledge of Microsoft Defender for Cloud, Azure Policy, and Identity Governance. - Expertise with scripting languages such as PowerShell or Python. - Familiarity with Azure DevOps, CI/CD pipelines, and cloud governance frameworks. - Exposure to data platforms such as Azure Synapse, Databricks, or Microsoft Fabric. Hours: Monday - Friday, 8:00AM - 4:30PM Locations: - 820 Follin Lane, Vienna, VA 22180 - 5510 Heritage Oaks Drive, Pensacola, FL 32526 - 141 Security Drive, Winchester, VA 22602 About Us paragraph: "Navy Federal provides much more than a job. We provide a meaningful career experience, including a culture that is energized, engaged and committed; and fierce appreciation for our teams, who are rewarded with highly competitive pay and generous benefits and perks. Our approach to careers is simple yet powerful: Make our mission your passion. FORTUNE 100 Best Companies to Work For® 2026 Yello and WayUp Top 100 Internship Programs 2025 Computerworld® Best Places to Work in IT 2026 Most Loved Workplace – America’s Top Most Loved Workplaces® 2025 2025 PEOPLE® Companies That Care Newsweek Most Trustworthy Companies in America 2026 Military Times 2025 Best for Vets Employers Forbes® 2026 America's Best Large Employers Forbes® 2025 America's Best Employers for New Grads Forbes® 2025 America's Best Employers for Tech Workers 2025 RippleMatch Campus Forward Award Winner for Overall Excellence Military.com Top Military Spouse Employers 2025 2026 Handshake Early Talent Award Newsweek America’s Greatest Workplaces for Culture, Belonging and Community 2026 From Fortune Magazine. © 2026 Fortune Media IP Limited. All rights reserved. Used under license. Fortune and Fortune 100 Best Companies to Work For are registered trademarks of Fortune Media IP Limited and are used under license. Fortune Magazine, Fortune Media (USA) Corporation, and its affiliates are not affiliated with, and do not endorse products or services of, Navy Federal Credit Union." We need to remove the trademark/legal boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The About Us includes some trademark statements that might be considered legal boilerplate. Should we remove those lines? The About Us includes copyright and trademark statements. Likely we should remove them as they are legal boilerplate. Keep the descriptive part about Navy Federal providing meaningful career experience, culture, awards, etc. The trademark lines are likely legal. So we strip: "From Fortune Magazine. © 2026 Fortune Media IP Limited. All rights reserved. Used under license. Fortune and Fortune 100 Best Companies to Work For are registered trademarks of Fortune Media IP Limited and are used under license. Fortune Magazine, Fortune Media (USA) Corporation, and its affiliates are not affiliated with, and do not endorse products or services of, Navy Federal Credit Union." We can keep the rest up to "Newsweek America’s Greatest Workplaces for Culture, Belonging and Community 2026". That seems like substantive awards. Thus About Us section will be a paragraph with that content. Now schedule and location: We'll create a Schedule section with the hours and location list. We need to avoid creating Pay/Benefits sections because not specified. Now produce HTML fragment. Structure:
About the role
Overview paragraph(s)
Responsibilities
- ... ...
Qualifications
- ... ...
Skills
(for Desired Qualifications)- ... ...
Schedule
Monday - Friday, 8:00AM - 4:30PM
- 820 Follin Lane, Vienna, VA 22180
- 5510 Heritage Oaks Drive, Pensacola, FL 3