The Finance Engineer: inside the new hybrid finance role taking shape in 2026

A Finance Engineer is a finance professional who combines accounting, FP&A, or finance leadership expertise with automation, AI tools, systems integration, and workflow design. Rather than replacing traditional finance roles, finance engineering adds a technical skill layer that helps finance teams automate processes and build internal tools.
If you have been automating bits of the close, vibe coding dashboards at the weekend, or wiring Claude or Copilot into your team's workflow, you already recognise what that description means in practice. According to CFO Connect's State of AI in Finance 2026 report, 56% of finance professionals say workflow automation is the single most important AI-related skill for their career in the next two years. Independent finance writers and operators have begun publicly coining the term in 2026, and the job market is starting to follow. This article defines the term in CFO Connect's own voice, maps the skill layer against CFO Connect's own data, and gives finance leaders a concrete frame for building it inside their teams.
What is a Finance Engineer?
A Finance Engineer is a finance professional, whether Controller, FP&A lead, Head of Finance, or CFO, who has added technical fluency and a build-first mindset to their existing finance foundation. Controllers still close the books, but they are increasingly automating the close. FP&A leads still forecast, but they are increasingly building the dashboards rather than populating them by hand. Heads of Finance still run the function, but they are increasingly building the systems that run it. The Finance Engineer skill layer sits on top of what they already know: the business context, the accounting standards, the commercial judgement. The difference is that they can now ship the tool, not just specify it.
What is finance engineering?
One disambiguation worth making early: financial engineering, the quant discipline, covers derivatives pricing, stochastic calculus, and risk modelling. That is not what this article is about. The finance engineer in 2026 is not a quant operating on a trading desk; they are an operator inside a corporate finance team, using AI tooling and automation to build internal systems and streamline workflows. The two disciplines share a word. The people and the work are distinct.
What does a Finance Engineer actually do?
The clearest account of day-to-day Finance Engineer work comes from CFO Connect's State of AI in Finance 2026 report, which maps the four technical must-haves now emerging across leading finance teams. These four skills are, in practice, the Finance Engineer's toolkit.
LLM literacy. Knowing how to use ChatGPT, Copilot, or Claude to analyse data, draft narratives, and validate outputs against source documents. In a Finance Engineer context, this looks like a Controller using an LLM to draft variance commentary on the monthly close, grounded in the actuals, in minutes rather than hours. See CFO Connect's Claude for Finance Teams playbook for worked workflows.
Workflow automation. Identifying friction in existing processes and removing it. An FP&A lead who refreshes dashboards daily instead of weekly because they have automated the data pull. A finance ops lead who has turned reconciliation from a Monday morning drag into a background process that flags exceptions. For a practical guide to how Claude, Cowork, and Zapier layer together for finance automation, see Claude Code, Cowork, and Zapier for Finance.
Data literacy and governance. Understanding data structures, recognising when inputs are incomplete, and working confidently across structured and unstructured sources. This is what lets a Finance Engineer interrogate a data model rather than wait for engineering to answer the question.
Systems integrations. Understanding how data flows through the ERP, how to connect systems, and working with basic SQL or API principles. A Head of Finance who can connect the ERP to a planning tool without raising an engineering ticket is not blocked by the infrastructure. The MCP and Claude for finance article covers how finance teams are using Model Context Protocol to achieve exactly this.
The State of AI in Finance 2026 report's CFO Connect Summit 2025 poll sets out the priority order clearly: 56% of finance professionals rank workflow automation as the most important AI-related skill for their careers in the next two years, with data literacy at 21% and cross-functional collaboration with AI at 14%. The Finance Engineer skill layer is the practical expression of all three, applied inside the finance function rather than delegated to a technology team. For a closer look at how the FP&A function in particular is being redesigned around these skills, see FP&A AI Upskilling: How CFOs Should Redesign Finance Roles.
Finance Engineering in practice: Pauline Babell, CFO, Spendesk
The four skills above are not hypothetical. Pauline Babell, CFO at Spendesk, demonstrated all of them live to nearly 500 finance professionals in a CFO Connect masterclass.
Her starting point was the same as most finance leaders: seven disconnected tools, no single source of truth, and a Monday morning ritual that consumed three hours before she had a number she could trust.
For years, my week started the very same way. Open Excel, open my ERP, export the data, open the spend tool, export again, then perform VLOOKUPs, pivot, reformat everything. Maybe three hours later, I had a number I could actually trust enough to send to the board. That number was already a week old by the time anyone read it. — Pauline Babell, CFO, Spendesk
Her response was not to hire a data team or raise an engineering ticket. She wired Claude directly into Spendesk's live spend data using MCP (Model Context Protocol), a connection that required one HTTP address and no engineering support. Three core reporting workflows, travel compliance, OPEX review, and AP aging, each previously taking hours, now run in under eight minutes each.
It's literally a copy-paste of an HTTP address. And then the MCP is connected. And then I can ask a simple question, plain English, conversational style. — Pauline Babell, CFO, Spendesk
That is systems integration, workflow automation, and LLM literacy applied at CFO level. It is also the Finance Engineer skill layer in action: a finance professional who built the tool rather than specified it, who automated the wait rather than managing around it.
For the full technical walkthrough and the exact prompts Pauline used, see MCP and Claude for Finance: How One CFO Stopped Waiting for Answers on Her Own Numbers.
Who is hiring Finance Engineers in 2026?
The clearest public signal of how the finance engineer role is being scoped in the market comes from Spring Health, the US mental healthcare company (Series E, $3.3 billion valuation), which is publicly hiring a Senior Finance Engineer. The role reports to the VP of Financial Planning and Analysis and the Chief of Staff to the CFO. That reporting line is the most important detail: the Finance Engineer sits inside finance, not in a separate engineering organisation. Required experience is 4+ years deploying automation, AI, or machine learning systems in a finance context, combined with 4+ years in FP&A, Strategic Finance, Accounting, or Finance Transformation. This is not a software engineer being asked to learn finance. It is a finance professional being asked to operate at the system level. The base salary range in Spring Health's public listing sits at $159,100 to $179,000, with equity and benefits.
This is currently a US-led signal. The pattern is consistent with how adjacent role titles have crystallised before: the GTM Engineer title, which Clay and the broader SaaS community established over the past few years, followed a similar arc from informal skill layer to explicit hiring brief. UK and European finance teams should expect the same pattern over the next 6 to 12 months. For a broader view of how hiring expectations across finance are shifting, see Finance Team Roles and Responsibilities and The Finance Talent Pipeline: What CFOs Should Do Now.
What skills does a Finance Engineer need?
The State of AI in Finance 2026 report sets out two layers, and both matter for the finance engineer role.
Technical layer:
LLM literacy: knowing how to prompt effectively, validate outputs, and integrate AI safely into daily workflows across reporting, analysis, and narrative drafting
Workflow automation: identifying and eliminating friction across the close, forecast variance commentary, reconciliations, and reporting packages
Data literacy and governance: reading, interpreting, and communicating confidently across structured and unstructured data sources, and recognising when inputs are incomplete
Systems integrations: understanding ERP data flows, connecting tools, and working with basic SQL or API principles without depending on engineering for every data question
Behavioural layer:
Curiosity and experimentation: running small tests with new tools rather than waiting for a complete playbook, treating AI as a coworker to be actively upskilled
Storytelling and business communication: turning AI-generated analysis into stakeholder decisions and organisational alignment
Strategic prioritisation: choosing which automations are worth building, assessing effort versus value, and ignoring low-impact tools regardless of their novelty
Change management: guiding colleagues through new workflows, championing adoption, and shaping how the team's culture adapts to the change
Willingness to automate your own role: proactively systematising tasks to free capacity for higher-value work, treating adaptability as a career asset rather than a risk
The behavioural layer is not a soft addendum to the technical one. It is what makes the technical layer land inside an organisation. As Rebeca Bichachi, CPA, Product Marketing Director at NetSuite, wrote in CFO Connect's State of AI in Finance 2026 report: "Finance leaders increasingly value problem-solving and storytelling skills. Only 23% of CFOs now rank deep accounting knowledge as the top hiring priority."
Technical AI fluency without the behavioural layer produces a Finance Engineer who can automate but cannot influence. The behavioural skills without the technical layer produce a finance professional who can communicate but cannot ship. Both layers together are the role.
Traditional finance role | Same role with Finance Engineer skill layer |
Controller closes the books through manual process | Controller automates the close, reviews exceptions only |
FP&A lead builds and populates dashboards in spreadsheets | FP&A lead automates the refresh and focuses on the narrative |
Head of Finance raises engineering tickets for data connections | Head of Finance connects systems directly and owns the data flow |
Finance ops lead runs manual reconciliations each period | Finance ops lead runs automated reconciliation with exception flagging |
Is this actually a job title, or is it a skill layer?
Both, but in a specific ratio worth being clear about.
In 2026, the Finance Engineer is overwhelmingly a skill layer being added to existing roles. Most finance professionals building these capabilities are not changing their title; they are changing what they can do. The Controllers, FP&A leads, and Heads of Finance who are automating workflows, building internal tools, and operating at the system level are Finance Engineers whether or not their job description says so.
A small but growing number of companies, Spring Health being one publicly documented example, are formalising the skill layer into a dedicated senior title with its own reporting line and compensation band. This makes sense at a certain scale: when the automation and systems work becomes substantial enough to warrant a specialist rather than a capability distributed across the team.
CFO Connect's read is that most finance leaders should treat the Finance Engineer as a skill layer to build deliberately inside the team they already have, not as a net-new headcount requisition. Build the capability first. The title will follow the work. If the role title consolidates over the next 12 to 24 months, which the early hiring signals suggest it will, the teams that built the capability early will be better positioned to hire for it or to promote from within.
How to start
Three concrete moves worth making this quarter, grounded in the State of AI in Finance 2026 skill framework.
Step 1: Automate one workflow end-to-end this month
Pick the process currently consuming the most manual time: the close, forecast variance commentary, dashboard refresh, or reconciliations. Pilot full automation using tooling the team already has access to (the Spendesk AI Hub is a useful starting point for finance-specific AI resources). This is a build-and-measure exercise, not a procurement project. The learning comes from shipping something, not from evaluating options. For a practical framework on where to begin, see A Short to Long-Term Plan for AI Adoption in Finance.
Step 2: Audit your team's LLM literacy honestly
The State of AI in Finance 2026 data says 56% of finance professionals see workflow automation as the most important skill for their career in the next two years. If your team is not actively building that fluency, you are behind your own peer set. That gap compounds quickly at the pace things are moving right now.
Step 3: Update the hiring brief for every new finance role in 2026
For FP&A leads, controllers, and finance ops roles, add automation literacy and AI fluency to the requirement set explicitly. Spring Health's public Senior Finance Engineer listing is one model of how to scope the senior version of that skill mix. The underlying expectations are shifting across all seniority levels, not just at the top.
CFO Connect's full library of coverage on Claude for Finance Teams, MCP for finance, and AI adoption is the natural next step from here. The Finance Engineer skill layer is already forming inside your organisation. The question is whether you are building it deliberately or discovering it after the fact.
Frequently asked questions: Finance Engineers
What is a Finance Engineer?
A Finance Engineer is a finance professional, whether a Controller, FP&A lead, Head of Finance, or CFO, who has added technical fluency and a build-first mindset to their existing finance foundation. The role is primarily a skill layer applied on top of core finance expertise: finance professionals who can automate workflows, integrate systems, and build internal tools without depending on a separate engineering team to do it for them.
Is a Finance Engineer the same as a Financial Engineer?
No. Financial engineering is a separate quant discipline covering derivatives pricing, stochastic calculus, and exotic options modelling, typically found in investment banking and asset management. A Finance Engineer in the 2026 sense is an operator inside a corporate finance function, using AI tooling and automation to streamline workflows and build internal systems. The disciplines share a word; the people and the work are different.
Do Finance Engineers need to know how to code?
Not in the full software engineering sense. The skill requirement set out in CFO Connect's State of AI in Finance 2026 report is systems integration literacy: understanding how data flows through the ERP, working with basic SQL or API principles, and connecting tools without depending on engineering for every data question. LLM literacy and workflow automation are the higher-priority technical skills. Finance Engineers build and configure; they do not typically write production software.
How much does a Finance Engineer earn?
The clearest public benchmark in 2026 comes from Spring Health's public Senior Finance Engineer listing, which carries a base salary range of $159,100 to $179,000, plus equity and benefits. This is a US-based, Series E company, senior-level data point. The title is too new for broad compensation benchmarks to exist; more data will emerge as the role consolidates over the next 12 to 24 months.
Can a Controller or FP&A lead become a Finance Engineer?
Yes, and many already are. The Finance Engineer is not a new role that displaces existing ones; it is a skill layer added to them. A Controller who automates the month-end close is operating as a Finance Engineer. An FP&A lead who builds dashboards and automates data refreshes is operating as a Finance Engineer. The title may not change; the capability does.
What tools do Finance Engineers use?
According to the State of AI in Finance 2026 report, the core toolkit covers: LLM platforms (ChatGPT, Microsoft Copilot, Claude) for analysis, narrative drafting, and workflow automation; workflow automation tools for removing friction from recurring processes; data platforms for working across structured and unstructured sources; and ERP-connected systems where basic SQL or API knowledge lets finance professionals query data directly. See MCP and Claude for finance for how teams are connecting these tools today.
Is Finance Engineer a real job title in 2026?
It is becoming one. In 2026 it is primarily a skill layer being applied across existing roles, but dedicated titles are emerging: Spring Health's public Senior Finance Engineer listing is one documented example, with the role reporting to the VP of FP&A rather than sitting in a separate engineering organisation. As the skill layer becomes more explicit and more companies scope it at the hiring level, the title should consolidate over the next 12 to 24 months.
How do I become a Finance Engineer if I am already working in finance?
Start with one workflow. Pick a high-friction, manual process and pilot end-to-end automation using tools your team already has. Build LLM fluency by using Claude, Copilot, or ChatGPT on real finance tasks: variance commentary, dashboard preparation, reconciliation. Update your own professional profile and your team's next hiring brief to reflect automation literacy as a requirement, not a bonus.