Remote job
Cloud Finops Analyst
Job details
About this role
Role overview Help make cloud spending dashboards and reports accurate, well organized, and usable across a large enterprise. Working with FinOps, engineering, and business teams, you will govern reporting assets, validate cost data, and help users find and understand relevant insights.
Responsibilities - Curate cloud cost dashboards, views, and reports in a cost management platform and related internal tools. - Maintain an up-to-date catalog as dashboards are added, changed, or retired, and establish a clear information hierarchy. - Define checks for dashboard accuracy, ownership, naming, and organization. - Reconcile reported metrics and dimensions against billing and Kubernetes cluster data, documenting how figures are derived. - Test platform releases and new reporting features; write test cases and report regressions with supporting evidence. - Track dashboard changes, fixes, and remediation through to completion, and support adoption of updated metrics and layouts.
Requirements - Hands-on experience with Cloudability or equivalent direct experience with the named platform in the source. - Working knowledge of AWS or GCP billing data and Kubernetes cost allocation. - Understanding of FinOps practices such as cost allocation, efficiency, and tagging. - Experience building and governing BI dashboards, including naming standards and information architecture. - Ability to automate governance checks with code, APIs, scheduled jobs, or low-code tools. - End-to-end ownership of testing and implementation, with a methodical UAT or SaaS QA approach.
Nice to have - FinOps Certified Practitioner certification, SQL skills for checking platform results against raw data, or experience supporting a large enterprise.
Benefits and work setup - The organization describes itself as remote-first, with teams distributed internationally. - The work offers hands-on technical problem-solving, ongoing learning, and direct support for developers. The source also flags frequent context switching, recurring issue patterns, and pressure around highly visible systems.