Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
FinOps Engineer
- Remote from
- 🌐 Anywhere
- Salary
- Undisclosed
- Department
- DevOps & Infrastructure
- Employment
- Full Time
- Experience
- Open level
- Published
- Apply before
- 6 Dec 2026
- Listing views
- 22
- Application actions
- 1
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
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.
Partner with engineering on architecture decisions: Bring cost into the room early, cost-efficiencies are cheaper to get right at design than to retrofit.
Work with Finance on forecasting and reporting: Support budget tracking and financial KPIs; build dashboards engineering and finance can both read.
You Might Be a Good Fit If You
Have strong AWS expertise and working GCP knowledge, including pricing models, billing structures, and cost optimization mechanics.
Have automation and scripting skills: Python, Terraform/ pulumi, Lambda, or Bash
Are comfortable with cost/billing tooling: AWS Cost Explorer, Cost & Usage Reports, GCP Billing Reports, and BI/dashboarding (we use Hex).
Have experience with, or are comfortable picking up, Linear and Notion as the system of record for tracking and documenting FinOps work.
Experience with a dedicated cloud cost management platform (e.g. CloudZero, Vantage, or similar) is a plus, not required.
Can analyze cost data and present it clearly to both technical and non-technical audiences.
Have prior experience in a FinOps, cloud cost management, or cloud governance role.
Are energized by doing the unglamorous, high-leverage work (the schlep) that unblocks other teams, and by working cross-functionally without positional authority.
What We Offer
Fully Remote
We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.
ESOP
Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together.
Tech Allowance
Use this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work.
Health Benefits
Supabase covers 100% of health insurance for employees and 80% for dependents, wherever you are. Your wellbeing and your family’s health are important to us.
Annual Off-Sites
Once a year, the entire company gathers in a new city for a week of connection, collaboration, and fun. It’s a highlight of our year.
Flexible Work
We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.
Professional Development
Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.
About the Team
Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.
~400 team members
60+ countries
20+ languages spoken
Over $1B raised (including our $500M Series F)
540,000+ community members
We move fast, build in public, and use what we ship. If it’s in your project, we probably use it in ours too. We believe deeply in the open-source ecosystem and strive to support—not replace—existing tools and communities.
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
4/5Autonomy Level
5/5Communication Load
5/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would begin by establishing a cost baseline by service, team, environment, and usage driver. I would prioritize opportunities by expected savings, implementation effort, operational risk, and confidence in measurement, then work with service owners to implement and validate savings against the baseline.
I would define a clear tagging and labeling standard for ownership, product, environment, and cost center, then enforce it through infrastructure-as-code policies and deployment checks. I would also create reporting for untagged spend and use allocation rules only where direct tagging is not feasible.
I would automate daily cost ingestion, anomaly detection, budget alerts, and reports segmented by team and service. Using Python, Terraform, and Lambda or equivalent services, I would create actionable alerts with ownership context and integrate remediation or ticket creation where appropriate.
I frame the discussion around measurable options: expected savings, reliability impact, implementation effort, and reversibility. Engineers receive technical details and operational risks, while finance receives forecast impact and realized savings tracking, with both audiences aligned on the decision criteria.
I would document the pre-change baseline, normalize for workload and seasonality where necessary, and compare post-change usage and billing over an agreed observation period. I would attribute the verified delta to the initiative only after accounting for unrelated demand changes, then publish the result to stakeholders.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
