Supabase
FinOps Engineer
- Employment type
- Full-time
- Workplace type
- Remote
- Location
- Remote, Global
- Published
- Sep 17, 2026
- Last checked
- Oct 26, 2026
About this role
About Supabase
Supabase is the Postgres development platform, built by developers for developers. We provide a complete backend solution including Database, Auth, Storage, Edge Functions, Realtime, and Vector Search. All services are deeply integrated and designed for growth.
About the Role
We're looking for a FinOps Engineer to help drive cost optimization and cloud financial governance across our AWS infrastructure and GCP footprint. You'll work cross-functionally with Engineering, Finance, and Product to find and ship savings, build the tooling necessary to maximize efficiency of every dollar spent in the cloud, and cultivate a culture of cost awareness across engineering teams.
This is a hands-on engineering role, not an analyst seat. You'll do the schlep work other teams don't have time for, digging into a bucket's access pattern, writing the Terraform or Lambda that ships the fix, working on a product feature chasing a number until it reconciles, and influencing product decisions when cost to reliability tradeoffs hit. Strong communication matters as much as technical depth, you'll regularly explain a savings case to an engineering team, a finance stakeholder, and a leadership audience in the same week.
What You'll Be Responsible For
In this role, you'll:
- Find and ship savings across AWS and GCP: Analyze billing, usage, and cost trends to identify opportunities, rightsizing, storage lifecycle policies, data transfer, and spot/auto-scaling. Take ideas from identification through to a realized dollar figure, not just a recommendation.
- Build and maintain cost attribution: Tagging policies, cost allocation, and chargeback/showback so engineering teams can see and own their own spend. This is foundational work other savings work depends on.
- Automate cost governance: Build automated cost reporting, anomaly detection, and alerting. Write the scripts and infrastructure-as-code (Python, Terraform, Lambda) that enforce cost policy rather than relying on manual review.