This description is a summary of our understanding of the job description. Click on 'Apply' button to find out more.

Role Description

We are looking for a FinOps engineer that packs the technical chops of an SRE, but brings experience with cloud cost management & capacity planning. In this role, you aren’t a gatekeeper; you’re an enabler. You’ll be successful when:

• Cost is a first-class citizen: Engineers treat "cost per query" or "cost per ingest" with the same rigor they treat latency or availability.
• The "hot potato" dies: Build the systems that give teams the autonomy to own their own margins.
• Cultural compounding: Build a culture where 100 engineers make 1% better decisions every day.
• Own the strategy and enable cost-aware engineering: Build the systems and attribution structures (tagging, showbacks) that give teams ownership of their impact.
• Partner with Finance: Explain variances, maintain clean cost allocation, and help the business understand margins by product line.

Qualifications

• Previous experience in FinOps, cloud cost management, or cloud governance.
• Deep cloud fluency: Understanding of cross-AZ data transfer, NAT gateway costs, and price-performance ratios of different instance families.
• Kubernetes expertise: Understanding how to allocate costs in K8s.
• The "hybrid" brain: Ability to speak SQL and CI/CD with engineers and pivot to forecasting and margin analysis with Finance.
• Bias for action: Ability to write scripts to automate tagging hygiene.
• CI/CD awareness: Understanding how deployment patterns affect cost.
• Communication skills: Ability to explain cost insights to both engineers and finance.

Requirements

• You don’t need to be a ClickHouse expert on day one, but you should enjoy owning complex infrastructure.

Nice to have

• Experience with tools like Vantage, CloudHealth, or Kubecost.
• Experience with our specific stack (ClickHouse, Kafka, Postgres).
• Experience using SQL for querying cost data.
• Strong opinion on when not to use Spot instances.