Back to jobs

FinOps Data Engineer

Pay
Pay not listed
Work setting
Remote — work setting source
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.
Listed location: Remote, Global
Read the full posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering › FinOps — team source
Department: Engineering › FinOps
From the employer’s posting

What you’ll work on

Full posting

We're looking for a FinOps Data Engineer to help drive cost optimization and cloud financial governance across our AWS infrastructure and GCP footprint.

This is a hands-on engineering role, not an analyst seat.

  • Find and ship cloud savings across AWS and GCP, from identification to realized dollars

  • Design and run BigQuery/dbt models that reconcile raw CUR and Storage Lens data into mart tables

  • Build cost-vs-revenue and customer segmentation models for unit economics and margin

  • Build cost attribution, tagging policies, and chargeback/showback for engineering teams

  • Automate cost reporting, anomaly detection, and alerting with Python, Terraform, and Lambda

From the employer’s posting
We're looking for a FinOps Data 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 role owns the data side of that mission: the models, pipelines, and analysis that make cost, usage, and margin numbers trustworthy across the company.
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 dbt model or Python pipeline that ships the fix, building the cost-vs-revenue mart that answers a margin question once instead of every time, and chasing a number until it reconciles. Strong communication matters as much as technical depth, you'll regularly explain a savings case or a data model's implications to an engineering team, a finance stakeholder, and a leadership audience in the same week.
Take ideas from identification through to a realized dollar figure, not just a recommendation.
Design and run the BigQuery/dbt models that turn raw billing and usage data (CUR, Storage Lens) into reconciled, trustworthy mart tables
Model unit economics and margin by product line and customer segment
Tagging policies, cost allocation, and chargeback/showback so engineering teams can see and own their own spend.
Write the scripts and infrastructure-as-code (Python, Terraform, Lambda) that enforce cost policy rather than relying on manual review.

Benefits in the posting

Full benefits wording
  • 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
  • Tech Allowance
  • 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
  • Flexible Work
  • Professional Development
  • Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.

From the employer’s posting.

Apply at Supabase

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 15, 202638 days ago
Recorded sightings
36
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 38

Similar jobs usually come down between day 6 and day 56.

From 14,771 similar postings that came down. Coming down is not always a hire.

Supabase is hiring

2 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Bash
  • Python
  • SQL
  • AWS
  • BigQuery
  • dbt
  • GCP
  • Terraform
Where the posting names them
- Have data science fundamentals: statistical forecasting, anomaly detection, and experimentation, and know when a rigorous model beats a rule of thumb. - 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).
We're looking for a FinOps Data 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 role owns the data side of that mission: the models, pipelines, and analysis that make cost, usage, and margin numbers trustworthy across the company. 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 dbt model or Python pipeline that ships the fix, building the cost-vs-revenue mart that answers a margin question once instead of every time, and chasing a number until it reconciles. Strong communication matters as much as technical depth, you'll regularly explain a savings case or a data model's implications to an engineering team, a finance stakeholder, and a leadership audience in the same week. What You'll Be Responsible For
- 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.
- Have strong AWS expertise and working GCP knowledge, including pricing models, billing structures, and cost optimization mechanics. - Have data engineering depth: dbt, BigQuery (or an equivalent modern warehouse), SQL at scale, and data modeling for analytics (dimensional modeling, incremental models, testing). - Have data science fundamentals: statistical forecasting, anomaly detection, and experimentation, and know when a rigorous model beats a rule of thumb.
About the Role We're looking for a FinOps Data 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 role owns the data side of that mission: the models, pipelines, and analysis that make cost, usage, and margin numbers trustworthy across the company. 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 dbt model or Python pipeline that ships the fix, building the cost-vs-revenue mart that answers a margin question once instead of every time, and chasing a number until it reconciles. Strong communication matters as much as technical depth, you'll regularly explain a savings case or a data model's implications to an engineering team, a finance stakeholder, and a leadership audience in the same week.
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 the FinOps data pipeline: Design and run the BigQuery/dbt models that turn raw billing and usage data (CUR, Storage Lens) into reconciled, trustworthy mart tables, the foundation everything else in FinOps is built on.
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 data engineering depth: dbt, BigQuery (or an equivalent modern warehouse), SQL at scale, and data modeling for analytics (dimensional modeling, incremental models, testing).
- 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.
- 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 the FinOps data pipeline: Design and run the BigQuery/dbt models that turn raw billing and usage data (CUR, Storage Lens) into reconciled, trustworthy mart tables, the foundation everything else in FinOps is built on. - Build cost-vs-revenue and customer segmentation models: Model unit economics and margin by product line and customer segment, and extend coverage as new products and segments come online.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

About the Role

We're looking for a FinOps Data 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 role owns the data side of that mission: the models, pipelines, and analysis that make cost, usage, and margin numbers trustworthy across the company.

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 dbt model or Python pipeline that ships the fix, building the cost-vs-revenue mart that answers a margin question once instead of every time, and chasing a number until it reconciles. Strong communication matters as much as technical depth, you'll regularly explain a savings case or a data model's implications 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 the FinOps data pipeline: Design and run the BigQuery/dbt models that turn raw billing and usage data (CUR, Storage Lens) into reconciled, trustworthy mart tables, the foundation everything else in FinOps is built on.

  • Build cost-vs-revenue and customer segmentation models: Model unit economics and margin by product line and customer segment, and extend coverage as new products and segments come online.

  • Apply data science to cost and usage data: Build forecasting models, detect anomalies statistically rather than by threshold alone, and quantify savings opportunities (e.g. storage lifecycle, request-cost patterns) with rigor a spreadsheet can't match.

  • 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 and self-serve analytics 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 data engineering depth: dbt, BigQuery (or an equivalent modern warehouse), SQL at scale, and data modeling for analytics (dimensional modeling, incremental models, testing).

  • Have data science fundamentals: statistical forecasting, anomaly detection, and experimentation, and know when a rigorous model beats a rule of thumb.

  • 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 spanning data analytics, data engineering, or data science in a FinOps, cloud cost management, or cloud governance context.

  • 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.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Remote, Global

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.
More source context
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
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.