Senior Solutions Architect — Cloud Economics & AI FinOps

nOps; Northern (KY); Hybrid; USD 140,000 - 190,000; Full time

Job summary

nOps is seeking a Senior Solutions Architect who has sat where customers sit, leading FinOps, cloud economics, or cloud financial management in a large enterprise. You will own commitment portfolios, build forecasts, and provide actionable insights across pre-sales and hands-on implementation.

You will shape the next generation of offerings with strong judgment on commitments, allocation, forecasting, and AI economics, sitting across from CFOs to deliver meaningful insights.

Qualifications

• 5+ years in cloud financial management, FinOps, cloud economics, or TBM.
• Own or govern a commitment portfolio including real purchases, renewals, and coverage decisions.
• Strong understanding of commitment risk and portfolio resilience through slow quarters or architecture changes.
• Hands-on experience with MCP servers or automation you've built.
• Fluency in billing data at the source (CUR/FOCUS) and Azure/GCP billing exports.
• Experience building cost allocation, showback, and unit economics models.
• Experience forecasting and owning a budget number, not just reporting.
• Comfort speaking with engineering and finance or FP&A audiences; C-level reporting a plus.
• Strong SQL and data modeling skills; familiarity with Looker/Tableau/Power BI.

Responsibilities

• Commitment management, multi-cloud: own the technical story on commitment coverage and utilization across AWS, Azure, and GCP, including RI, Savings Plans, and CUDs.
• Allocation, forecasting, and unit economics: architect cost allocation, showback, and chargeback models, and build forecasting and budget models.
• AI visibility and tokenomics: lead AI cost engagements end to end, including spend attribution from account to model to department, token-level economics, and optimization recommendations.
• Proofs of value and adoption: build proofs of value using MCP server and API, making analyses reusable for customers.
• Community: represent nOps in the FinOps community through events, FinOps X, enablement sessions, podcasts, and content.

Skills

FinOps

Cloud economics

TBM

SQL

Data modeling

BI tools

Tools

Apptio

Cloudability

CloudZero

Vantage

Finout

Job description

About nOps

nOps is the leading FinOps platform for AWS, Azure, and GCP, helping engineering and finance teams gain real-time cloud cost visibility and achieve autonomous optimization. Our mission is to make cloud cost management effortless, enabling teams to scale innovation without waste. We partner closely with the major hyperscalers and our customers to continuously improve how organizations optimize, manage, and invest in their cloud environments.

Today, nOps manages more than $5B in annual cloud spend across 500+ brands, consistently delivering effective savings rates above 55%. That track record is backed by recognition from the partners and standards: AWS Advanced Technology Partner status, FinOps Foundation Premier Membership, SOC 2 Type 2 certification, and a 4.8 rating on G2.

About the Role

We're looking for a Senior Solutions Architect who has sat where our customers sit: someone who has led FinOps, cloud economics, or cloud financial management inside a large enterprise, owned a commitment portfolio and an allocation model, and built forecasts that leadership actually relied on. You'll bring that experience directly to our customers, across both pre-sales conversations and hands‑on implementation, and help shape what we build next.

What matters most in this role is strong judgment on commitments, allocation, forecasting, and AI economics, along with the knowledge and credibility to sit across from a CFO and deliver insights that actually matter to them.

This is a hands‑on, builder's role. Our Solution Architects create working solutions for customers rather than presenting slides, and you'll partner closely with our Director of Solution Architecture on some of our most strategic accounts.

What You'll Do

• Commitment management, multi-cloud. Own the technical story on commitment coverage and utilization across AWS, Azure, and GCP, including Reserved Instances, Savings Plans, and Committed Use Discounts (CUDs). Help customers understand commitment risk, such as stranded capacity, expiry timing, or instance and region drift, and build a clear plan to address it.
• Allocation, forecasting, and unit economics. Architect cost allocation, showback, and chargeback models, and build forecasting and budget models that finance and engineering both trust. Stand up unit economics across customers, products, features, and transactions.
• AI visibility and tokenomics. Lead AI cost engagements end to end, including spend attribution from account to model to department, token-level economics, and optimization recommendations customers can put into action.
• Proofs of value and adoption. Build proofs of value using our Model Context Protocol (MCP) server and API, so customers see a working solution in their own environment rather than a slide deck. Turn one-off requests into reusable, repeatable analyses customers can run themselves.
• Community. Represent nOps in the FinOps community through FinOps Foundation events, FinOps X, enablement sessions, our podcast, and written content.

What You Bring

We've seen this role succeed along two different paths, and we're equally excited to talk to candidates from either background.

• You've led a FinOps, cloud economics, cloud financial management, or Technology Business Management (TBM) function inside a large enterprise, roughly $10M+ in annual cloud spend across multiple business units, and built that practice yourself.
• Or, you bring deep expertise in commitment and rate optimization specifically: how Reserved Instances, Savings Plans, and CUDs perform under real workloads, coverage versus utilization tradeoffs, and what separates paper savings from savings that are actually realized.

Required

• 5+ years of experience in cloud financial management, FinOps, cloud economics, or TBM. Experience with tooling such as Apptio, Cloudability, CloudZero, Vantage, or Finout counts fully.
• Hands‑on experience owning or governing a commitment portfolio, including real purchase, renewal, and coverage decisions.
• A strong working understanding of commitment risk, including what can go wrong and how to structure a portfolio that holds up through a slow quarter or an architecture change.
• Hands‑on experience with MCP servers or agentic tooling, a proof of concept, internal workflow, or automation you've built yourself.
• Fluency in billing data at the source, including CUR and FOCUS, and Azure and GCP billing exports.
• Experience building cost allocation, showback, chargeback, or unit economics models that an organization adopted and used.
• Experience forecasting and owning a budget number, not just reporting on one.
• Comfort speaking credibly with both engineering and finance or FP&A audiences; direct C-level reporting experience is a plus.
• Strong SQL and data modeling skills, along with familiarity with a BI tool such as Looker, Tableau, or Power BI.
• Comfort in a customer‑facing, revenue‑adjacent role that includes discovery calls, objection handling, executive readouts, and RFP support.

Nice to Have

• Recent hands‑on AI cost experience, such as token and inference economics, model routing, caching strategy, or GenAI spend attribution.
• Experience building customer‑facing proofs of concept or proofs of value from start to finish.
• Multi‑cloud experience beyond AWS, or experience with SaaS spend management.
• Experience with hybrid or private‑cloud environments alongside public cloud.
• Experience helping an organization build a FinOps practice from the ground up.
• Experience with M&A, divestitures, or data center modernization projects.
• Vendor contract or SOW negotiation experience.
• FinOps Certified Practitioner or Professional certification.
• A public presence in the FinOps community through talks, podcasts, or writing.
• Infrastructure engineering experience (Terraform, CI/CD, Kubernetes, or cloud architecture certifications) or Python, both are a plus, but not required for this role.