Finance Transformation Manager

Job description

About this role

A Power Platform, automation or AI builder who has turned manual processes into working solutions. An analytics or data engineer who understands how to make financial data reliable, structured and useful. The common denominator isn't your previous job title. It's what you've built.

Responsibilities

• You'll work alongside the Finance team and across our technology ecosystem, identifying opportunities to improve how Finance operates.
• Some weeks that might mean investigating why Dynamics and Anaplan disagree on a number and fixing the underlying integration or data flow.
• Other weeks it might mean building an AI-powered workflow that reduces a two-day reconciliation to two hours.
• You might redesign a reporting process, build an automated control, improve data integrity, create an internal tool, connect systems, or identify where AI can safely remove repetitive manual work.
• You'll also work with Finance colleagues who understand the business and accounting requirements deeply.
• Your role is not to replace that expertise.
• It's to combine it with engineering thinking to build something better.
• You'll become the bridge between Finance, Data, Technology and Engineering — someone who can understand the business problem, interrogate the underlying systems and data, and then help build the solution.

Qualifications and requirements

• 1. You build things
• You have hands-on experience creating something that solved a real problem.
• An AI/GenAI workflow
• An internal tool
• A data pipeline
• A reporting solution
• An ERP solution
• A Power Platform application
• A reconciliation process
• A system or workflow that materially improved how people work
• It doesn't have to be built in Claude.
• It doesn't even have to have been built specifically for Finance.
• But it must be real.
• You'll be expected to demonstrate something you've built as part of our interview process.
• 2. You think in systems
• You naturally look beyond the immediate task and ask how the underlying system works.
• data → integration → process → system → control → output.
• You enjoy finding the root cause rather than repeatedly fixing the symptom.
• 3. You're comfortable with technology
• Data engineering / analytics engineering
• APIs and integrations
• Data modelling and transformation
• You don't need experience across all of these.
• Depth in one or more, combined with the ability and curiosity to learn the rest, is more valuable than a checklist of technologies.
• 4. You're curious about Finance
• You don't need to arrive knowing every accounting concept.
• But you do need to be interested in understanding the domain.
• You'll need to become comfortable with areas such as reconciliation, reporting, planning, financial data, controls, audit and the systems that support them.
• The expectation isn't that you already know everything.
• The expectation is that you can learn quickly and then use your technical capability to make the domain work better.