Cloud FinOps Architect / Lead
We are looking for an experienced Cloud FinOps Architect / Lead with 15+ years of overall IT experience and 5+ years in Cloud FinOps, Cloud Cost Management, or Cloud Economics to drive enterprise cloud financial governance, cost optimization, forecasting, and accountability.
Required Knowledge
- Cloud Platforms: Deep working knowledge of AWS, Azure, or GCP pricing models.
- Data Querying: Strong SQL skills to pull granular data directly from data lakes (e.g., BigQuery, AWS Cost Explorer).
- FinOps Tooling: Hands-on experience with platforms like Apptio Cloudability, Datadog Cost Management, or CloudHealth.
- AWS CUR 2.0 or FOCUS, Azure Cost Management export, and GCP Cloud Billing export to BigQuery. At least one of these in production. The other two readable without a walkthrough.
- FOCUS-shaped columns: billed cost, effective cost, and list cost. Tag and account mapping for product, owner, environment, and cost center.
- Invoice reconciliation, and a reload that replaces a day instead of adding it again.
- Commitment types, Reserved Instances, Savings Plans, Azure reservations, and GCP committed use discounts.
Requirements
- Requires 5+ years of cloud engineering or architecture experience, expert-level SQL and scripting (Python), and advanced knowledge of enterprise cloud-billing mechanics.
Key Responsibilities
- Cost Allocation: Define tagging taxonomies, business mappings, and chargeback/showback models.
- Optimization: Recommend and configure Reserved Instances, Savings Plans, and idle resource cleanup.
- Automation: Build scripts or Infrastructure as Code (IaC) guardrails via Terraform or Python.
- Forecasting: Partner with FP&A to build variance, budget, and scenario models.
- Strategic Focus: Drives culture, governance, and architectural standards instead of just managing tool dashboards.
- Implements automated cost-guardrails via Infrastructure as Code (IaC), designs cross-functional unit economics, and manages massive multi-cloud commit strategies (Savings Plans/RIs).
Nice to have
- Snowflake usage views, including credits, warehouse, and compute versus storage.
- A SaaS invoice or seat file, mapped to vendor, product, owner, and period.
- An AI usage feed (OpenAI, Amazon Bedrock, Anthropic, or Vertex) with model, input tokens, output tokens, and request count.
- The customer's scheduler or Terraform, used to run this job, not to rebuild a landing zone.