Zoop.one

We're looking for a FinOps Engineer with a DevOps backbone who has an almost

obsessive eye for cost leaks, idle resources, and inefficiencies across our platform. If unused

EBS volumes, oversized instances, or a forgotten dev environment running on weekends

genuinely bother you — you'll fit right in.

This isn't a passive reporting role. You'll be expected to proactively hunt for waste,

propose optimizations, and drive strategic cost conversations with engineering, SRE,

and leadership across Zoop's entire platform — from infrastructure and Kubernetes clusters

to data pipelines and third-party services.

What You'll Own

●​ Continuously audit Zoop's cloud footprint (AWS/Azure/GCP) end-to-end —

compute, storage, networking, databases, observability stack, and SaaS tooling

— and flag every form of waste, big or small.

●​ Proactively propose cost-reduction strategies rather than waiting to be asked

— bring data, options, trade-offs, and a recommendation to the table.

●​ Lead monthly/quarterly cost reviews with engineering and product leadership;

turn billing data into actionable conversations.

●​ Build cost visibility dashboards and chargeback/showback models so every team

at Zoop knows what they're spending and why.

●​ Drive rightsizing, autoscaling tuning, Spot/Reserved Instance/Savings Plan

strategies, and storage tiering across the platform.

●​ Embed cost guardrails into CI/CD pipelines, IaC (Terraform/CloudFormation), and

Kubernetes manifests — catch wasteful resources before they're deployed.

●​ Optimize Kubernetes cost efficiency using tools like Kubecost, OpenCost, or

Karpenter; tune requests/limits, HPA/VPA, and node pools.

●​ Set up automated alerts and anomaly detection for budget breaches, idle

resources, and runaway costs.

●​ Partner with Finance for forecasting, unit economics (cost per user/transaction),

and cloud budget planning.

●​ Evangelize a cost-aware engineering culture — run internal sessions, write

playbooks, and make FinOps a shared responsibility, not a finance afterthought.

Who You Are

●​ Someone with genuine OCD around cost and wastage — you can't sleep

knowing a non-prod cluster ran all weekend at full capacity.

●​ A DevOps practitioner first, who understands why costs happen at the

infrastructure level — not just someone reading billing reports.

●​ Naturally proactive — you don't wait for tickets; you spot patterns, dig in, and

propose changes before anyone asks.

●​ Comfortable challenging engineering decisions diplomatically when they're

expensive, and equally comfortable defending necessary spend to finance.

●​ A clear communicator who can talk to both a senior engineer about Karpenter

configs and a CFO about quarterly burn.

Required Qualifications

●​ 3+ years of hands-on experience in DevOps, Cloud Engineering, SRE, or Cloud

FinOps roles.

●​ Strong working knowledge of at least one major cloud provider (AWS preferred), including native cost tools (Cost Explorer, CUR, Azure Cost Management, or GCP Billing).

●​ Proficiency with Infrastructure as Code (Terraform, CloudFormation, or Pulumi).

●​ Hands-on experience with Docker and Kubernetes (EKS/AKS/GKE).

●​ Scripting in Python, Bash, or Go for automation, reporting, and cost tooling.

●​ Familiarity with CI/CD tools (Jenkins, GitLab CI, GitHub Actions, ArgoCD).

●​ Solid grasp of cloud pricing models — On-Demand, Reserved Instances, Savings

Plans, Spot/Preemptible, committed-use discounts.

●​ SQL skills for querying billing data (AWS CUR via Athena/Redshift, BigQuery

billing exports).

Nice to Have

●​ FinOps Certified Practitioner (FOCP) certification.

●​ Cloud certifications (AWS, Azure, or GCP).

●​ Experience with FinOps platforms (CloudHealth, Cloudability/Apptio, Spot.io,

Vantage, Kubecost).

●​ Exposure to multi-cloud or hybrid-cloud cost optimization.

●​ Understanding of SaaS unit economics (cost per customer, cost per transaction,

gross margin impact).