Mundi

Mundi is the treasury operating system for Turkish mid-market companies.

Turkish finance teams operate in one of the world's most demanding macro environments: high inflation, volatile rates, fragmented banking. They spend hours a day moving cash between banks, chasing yield, reconciling payments, forecasting flows. The cost of getting it wrong is measured in significant losses, every day.

Mundi unifies their bank access, sweeps idle cash into institutional yield through licensed financial intermediaries, and reports it in real time.

We relaunched with a B2B focus 15 months ago and AUM has doubled every quarter since. The customers signing up are the kind of names that move the rest of the market when they pick a vendor.

We started with treasury. The bigger goal is to run the whole stack a Turkish finance team uses every day: payments, FX, working capital, and the workflows still stuck in spreadsheets. The next 18 months are about building toward that, and most of the work to get there doesn't exist yet.

The founders are repeat entrepreneurs with previous exits. The cap table is the people who would know: leading fintech VCs, founders of the category-defining Turkish fintechs, and Turkey's best-known bankers. We move fast, we ship constantly, and we're building the company we want to work at.

The role

We're hiring our first Forward Deployed Engineer.

Forward Deployed Engineer is a customer-embedded technical role pioneered at frontier tech companies. It's a different shape from a sales engineer or solutions architect: you sit with new customers from contract signature, build whatever has to be built to make Mundi work in their environment, and ship the customer-specific automation that turns a generic integration into a production-grade one.

The job is to make Mundi work for each customer. You wire their banks, integrate their ERPs, configure their treasury policies, and ship the automation that scales the work. You own this end-to-end. Whatever it takes to get a customer from signed contract to a live, automated treasury, on the shortest possible clock, is your call.

As a second layer, you make the rest of the team more productive. You build the AI tooling, agents, and workflows that compound the existing GTM motion: outbound enrichment and sequencing for the SDR, pre-sales prep automation for the AE, onboarding automation that scales beyond your own bandwidth.

That means judgment, not ticket execution. You'll argue about what to build for which customer, decide what good looks like for an integration, and own the result. You'll work shoulder-to-shoulder with the CTO on the harder technical calls and lean on the rest of engineering for shared infrastructure.

This isn't a sales role with a number to hit. As Mundi grows, the role expands, including direct ownership of pipeline.

If you've embedded with customers to ship technical solutions before and missed that altitude (close to the user, no layers between you and the integration, you own the result), this is that work at the place where the next generation of Turkish finance infrastructure is being built.

What success looks like in 12 months

Two things.

First, ship customers fast. Three numbers track this: account executive deal cycle time down 25% by month 9; outbound meetings per week up 2× with the same sales development representative (SDR) headcount; time-to-aha cut in half, from signed contract to a live customer running automated treasury, what takes weeks turns into days.

Second, build the engine. By year-end, there are AI workflows and onboarding patterns Mundi has because you built them: an onboarding system that lets us scale customer count without scaling headcount, integration patterns the next FDE hire builds on top of, GTM tooling the rest of the team can't imagine working without.

You'll fit if

You've done this before. Two to five years of operating experience at a startup. Title doesn't matter. You've been embedded with customers to ship technical solutions: built integrations, debugged in production, written automation that lasts. You've taken ownership of a customer's path from signed contract to live deployment. GTM experience is a plus, not a requirement.

You build with AI, not just talk about it. You've shipped production code with AI in the loop, run agents that do work, and have a strong point of view on which tools earn their place. You're past the demo phase and you know what these systems are good at and where they break.

Code depth and customer instinct, both at a senior bar. You can ship a feature against a real codebase. You can also walk into a CFO's office and run a treasury demo without losing the room.

You're fluent in Turkish and English. You'll lead demos in Turkish, write outbound in Turkish, and onboard Turkish customers in Turkish. You'll also live in English docs, English tools, and English Slack threads.

You're curious about treasury, fintech, regulated infrastructure, and B2B workflows.

You probably won't fit if

• You want a defined career ladder. We'll figure it out together as you go.
• You need work broken down into tickets. Show up, see the problem, ship the fix.
• You can't hold context in fast-moving environments where priorities adjust as we learn.

How we work

In office in Istanbul, five days a week. Two short syncs each week; the rest is uninterrupted building time. You'll be in customer calls, prospect threads, and a code editor on the same day, often in the same hour.

You'll work directly with the CEO, founders, CPO, and the CTO. Customer calls are part of the job: we don't firewall engineering from users. The in-office requirement is deliberate as we value the compounding effect of being in the same room when an architecture call needs to be made, when a customer surfaces a new problem, when someone needs to whiteboard for ten minutes.