Forward Deployed Analyst

Forward Deployed Analyst

What is Nanzen

Nanzen is disrupting B2B commerce by bringing agentic workflows to finance operations, automating critical, trust-sensitive flows that still run on emails, spreadsheets, old databases, manual approval chains and basic wire transfers.

We are ambitious, we are building Nanzen to be an era-defining company, where there's a clear before and after in B2B commerce.

The Nanzen team

Nanzen's philosophy is the smallest team of the best people, covering the maximum footprint.

We prefer in person but we do hybrid. Life can be better if you can make the best of both worlds. On the days we're not sitting next to each other, we miss the speed of a whiteboard session and the good vibes.

You need to have the ambition to work on something small that can change the world. This requires your attention and love. It's about caring, not grinding your life away. We have families and we intend for our kids to see their parents, but this is not a 9 to 5 job at Dunder-Mifflin.

Trust is everything. At Nanzen we base our relationships on transparency, autonomy and accountability (= allergic to BS).

The Forward Deployed Analyst role

Sit between the Nanzen engineering team and the customer's finance team and make the agents work on their real data.

What you own

Understand the pain. Understand how the customer's finance function actually operates: their counterparties, their data, their workflows, who approves what, where the exceptions go and what happens to them. The real thing.

Getting Nanzen live on their real data. Their invoices, ledgers, contracts and email, running through the product for the first time. Engineers handle the plumbing; you own whether the result is right.

Working out what actually went wrong. When an output looks off, judgement matter: the agent is wrong, the data is wrong, or the customer's process was never what they described. Getting this right is crucial.

Turning findings into product. Sit with the product engineering team while the fix is designed or the feature is deployed. Voicing what the customer actually meant, what's a real requirement versus a one-off, and what the agent should have done instead. You bring the reproducible case with the correct answer attached, so the fix can be tested forever rather than checked once. You stay with it until it ships, and you're the one who verifies it on the customer's data afterwards.

Guiding the agents with first-principles and own experience. Help the engineering team design, tune and build confidence into the agent's actions by mapping, understanding and annotating trajectories and helping create benchmarks from findings. You are riding the wave of how finance is adopting AI.

It's so good you are here. You become the person the controller calls. Trust with a finance team isn't won by being responsive and just nice. It's won also by understanding how they work and how Nanzen and the agents work.

The bar. You set the standard for whoever joins next, and you help choose them. We hire slowly and stay small on purpose.

You'll probably recognise yourself

• You've worked inside a finance function, or close enough to have felt the pain first-hand: AP, AR, controlling, treasury, audit, or consulting into those teams.
• You're not an engineer and don't need to be, but you're technically curious enough that engineers take you seriously. You want to know how the thing actually works, you can read what an agent did without needing it translated for you, and you've never been satisfied by "it's complicated."
• You've been the person who found the number nobody could explain, and you remember exactly what it took.
• You'd rather be on site in the trenches than in a deck.
• You can hold your own with a controller and with an engineer in the same hour, and translate between them without losing either.
• You've watched a demo work perfectly and known immediately why it wouldn't survive contact with real data.
• You've handed a problem to engineers in a form they could act on. Engineers enjoy working with you because you know your stuff and you make sense.
• You find it frustrating that this work is still done by hand. Someone, somewhere, is re-keying an invoice into a spreadsheet right now, and you want be the one that ships the AI that fixes that.

Probably not for you if

• You need the destination described before you'll start walking. Nobody here can hand you the spec. Finding it is the job.
• You want to stay at the level of process and strategy. The value here is in the transaction-level detail. This invoice, this exception, this approval, this counterparty. Specifics.
• You measure your work in workshops run and documents delivered rather than in something working on real data.
• You're waiting to be convinced about AI beind the tsumani that will change finance.

How we work

Very AI-pilled but anchored in reality. Small team, high trust, no ceremony. Design decisions get written down and argued on the document. You'll spend your time in their systems, our product, and a lot of conversations.