Finance Engineer

We're looking for a Finance Engineer to join our Finance team, building the data pipelines, dashboards, and automation that run the finance function and the revenue operations around it, from deal desk to sales compensation. Our goal is to operate finance as a small, senior team that runs on systems rather than headcount — and how well we do that depends on how quickly anyone here can get a trusted number on unit economics, cash burn, or technology spend and act on it. Building that capability is the heart of this role. You'll be working inside the numbers you're automating, not alongside them.The ideal candidate is an engineer first: strong data engineering fundamentals across SQL, Python, warehouse modeling, and orchestration, combined with enough finance and operational fluency to model revenue, cost, and margin without hand-holding. Experience building internal tools and agent workflows that non-engineers rely on daily is what sets this candidate apart.

This is a cross-functional role. You'll work closely with the VP Finance, our Controller, sales leadership, and engineering and infrastructure leadership — not as a handoff point, but as the person who learns enough of each domain to follow a number back to its source. At times you'll build the model, run the analysis, and present the finding yourself, both to deliver impact directly and to learn what's worth automating next. The bar is someone who understands the decision a number is meant to support, measures it from the outset, and would rather find out a model was wrong in a week than at quarter close. That discipline is what turns cross-functional ownership into an advantage.

The role is embedded within the Finance team and reports to the VP Finance.

What You’ll Do:

• Own unit economics — build and maintain cost-to-serve, gross margin, and contribution models by product, customer, and workload, rebuilt from source data rather than spreadsheets.
• Own budgeting for the technology organization: cloud and GPU/TPU spend attribution, vendor and capacity forecasting, and the models engineering leadership uses to plan.
• Build and run finance dashboarding — a single source of truth for burn, runway, margin, and company KPIs that the leadership team and board can trust.
• Automate budget-vs-actuals: live department-level views and overspend alerts that make budget and margin targets enforceable without manual chasing.
• Build the deal desk framework: pricing and discount guardrails derived from the margin model, automated quote and order-form generation, and routing so only non-standard deals need escalation — raising deal throughput without finance in the loop on every deal.
• Automate sales compensation: implement a comp tool and the pipelines behind it so statements, accelerators, and disputes run from CRM and billing data instead of spreadsheets.
• Design and ship finance agents and internal tools — workflows that pull, reconcile, and summarize financial data so non-engineers get answers without filing a ticket.
• Build and maintain the finance data layer: pipelines from billing, payroll, cloud, and accounting systems into a well-modeled warehouse.
• Partner with the VP Finance, Controller, and engineering leadership to trace discrepancies to their real source and ship fixes that hold.

What You’ll Need:

• Strong data engineering fundamentals, including SQL, Python, warehouse modeling, and orchestration (dbt, Airflow, or equivalent).
• Measurement discipline. You define what a number is for before you build it, you stay skeptical of your own results until they reconcile, and you treat an unexplained variance as a problem rather than noise.
• Appetite for the whole stack. Your core strength might be pipelines, but when a margin number looks wrong and traces back to a billing event or a cloud tag, you want to go find it yourself. The people who do well here went deep in one area first, then kept expanding outward.
• Experience working with financial or operational data — revenue, cost, billing, payroll, or cloud spend — and enough fluency in revenue, cost, and margin structures to model them without hand-holding.
• A track record of building internal tools, dashboards, or automations that non-engineers rely on daily.
• Familiarity with LLM-based agent workflows and comfort applying them to real operational processes, with a clear-eyed view of where they break.
• Enthusiasm for automating existing processes — you thrive on making manual work disappear and making systems faster and more reliable.
• Strong Python skills; experience with accounting, billing, or ERP system APIs (NetSuite, Stripe, or similar) is a plus.
• Excellent communication and a collaborative mindset — you can explain what a number means, and what it doesn't, to a VP Finance, a Controller, and an engineering lead.