Cloud Resource Manager

Cloud Resource Managers run the FinOps function — the organizational practice responsible for making cloud spending rational, transparent, and tied to business value. The role sits between engineering leadership, finance, and the executive team, translating the complexity of cloud infrastructure costs into decisions that those groups can act on.

At a practical level, the job divides into several streams. First is team leadership: managing analysts and engineers who do the day-to-day cost analysis, governance enforcement, and tooling work. Second is stakeholder management: engineering VPs want to build things fast; CFOs want budgets to hold; the Cloud Resource Manager finds the framework that lets both be true most of the time.

Vendor management is a distinctive part of this role that analysts don't typically handle. Enterprise Discount Programs and committed use agreements with AWS, Azure, and GCP are worth significant money — a large company negotiating well versus negotiating poorly can be a $5M–$20M annual difference. Managers who understand the commercial dynamics, build relationships with cloud vendor account teams, and come to negotiations prepared to walk away get better terms.

The internal charge-back model is another chronic challenge. When engineering teams don't see their own cloud costs, they have no reason to care about them. When finance sees only a single cloud invoice, they can't allocate costs to business units. Building a cost allocation model — tagging, account structure, and charge-back policy — that actually reflects how the organization works requires both technical understanding and organizational negotiation.

Most of this work doesn't produce visible output. It shows up as cloud costs that are lower than they would otherwise be, budgets that hold, and architecture decisions that are informed by cost data. The manager's job is to make those outcomes happen consistently.

Education:

• Bachelor's degree in computer science, information systems, finance, or business administration
• MBA valued for roles with significant budget authority and executive exposure

Certifications:

• FinOps Certified Practitioner (FOCP) — foundational; FinOps Certified Engineer or Professional for more advanced practitioners
• AWS Solutions Architect–Associate or Professional
• Azure Administrator Associate (AZ-104) or Azure Solutions Architect Expert (AZ-305)
• Google Cloud Professional Cloud Architect

Experience requirements:

• 7–12 years in cloud, infrastructure, or IT financial management roles
• 3–5 years of direct people management experience
• Demonstrated track record of cost reduction outcomes — specific dollar amounts and methods are standard interview asks
• Experience managing or negotiating vendor contracts

Technical knowledge:

• AWS, Azure, or GCP platform architecture at a working knowledge level — enough to evaluate optimization recommendations
• Cost management tooling: CloudHealth, Apptio, CAST AI, Flexera, or equivalent
• Infrastructure-as-code concepts (Terraform, CloudFormation) for governance policy integration
• Cloud billing data structures: AWS CUR, Azure Billing Exports, GCP BigQuery billing export

Leadership and business skills:

• Executive communication — ability to present cloud cost data to C-suite and board audiences
• Cross-functional influence without direct authority
• Financial modeling and budget management at department or program level
• Vendor negotiation tactics and commercial awareness

The Cloud Resource Manager role is in the growth phase of its lifecycle. FinOps as a formalized practice barely existed before 2018, and most enterprises still don't have a dedicated function. The organizations that do have one typically built it reactively — when cloud spending reached a scale where waste was visible and painful. Organizations that are earlier in their cloud maturity curve are hiring now to avoid reaching that pain point.

The FinOps Foundation's 2025 State of FinOps report showed that cloud spending governance is the top-ranked challenge among infrastructure and finance leaders at enterprises running $10M+ annual cloud budgets. Demand for people who can build and manage that function is strong and shows no sign of softening.

Cloud providers have made it easier to spend money and harder to predict how much you'll spend. New services launch monthly, AI infrastructure costs are difficult to model, and the bill is a mixture of a dozen different pricing dimensions. The complexity favors experienced practitioners who understand both the cloud platforms and the organizational dynamics that drive cost behavior.

Salaries have held up well relative to other senior IT management roles. The combination of scarcity — the FinOps talent pool is small — and the direct financial impact of the role (measurable savings on large budgets) creates leverage that most IT managers don't have when negotiating compensation.

Career paths forward include VP of Cloud Infrastructure, Director of Technology Finance, or Head of Platform Engineering. Some experienced managers move to cloud provider partner organizations or FinOps consulting firms, where they advise multiple enterprises rather than running one program. The FinOps Foundation's community provides a professional network that is unusually active for a technical specialty.

Dear Hiring Manager,

I'm applying for the Cloud Resource Manager position at [Company]. I currently lead the cloud FinOps function at [Company], where I manage a team of four analysts and engineers responsible for cost governance across a multi-cloud environment running approximately $8M in monthly AWS and Azure spend.

When I joined two years ago, the organization had no formal FinOps practice. Cloud costs had grown 60% year-over-year for two consecutive years with no governance model to explain or control the trajectory. I built the function from scratch: hiring two analysts, implementing Apptio Cloudability as our cost intelligence platform, establishing a tagging policy with cross-functional engineering buy-in, and building the charge-back model that now allocates cloud costs to 14 business units.

The most impactful single project was the AWS commitment strategy review we completed last fall. The organization had roughly 30% RI coverage with a mix of non-convertible reservations purchased years ago that no longer matched current instance families. I built a coverage model, presented three scenarios to the CFO and VP of Engineering, and executed a convertible RI exchange combined with a new Compute Savings Plan purchase. The net effect was a $2.1M reduction in annualized cloud spend.

I've also led our AWS EDP renewal twice. Last year's renewal extended our term by two years in exchange for a 7% incremental discount on compute — better terms than our AWS account team initially offered, which I achieved by developing an Azure migration cost model as a credible alternative.

I'd welcome the chance to discuss how this background applies to what you're building at [Company].

[Your Name]