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 Member of Technical Staff.

Member of Technical Staff is a senior IC title common at frontier tech companies. It's deliberately open-ended: you sit close to the people deciding what to build, you ship the thing yourself, and you take on the harder technical problems sitting behind the product.

At Mundi today, founders, the CPO, and the CTO shape features, architecture, and the future of the company together. And that's where you'll be, in the room where the decisions get made, with the conviction and context to go build them.

But the role is bigger than features. Treasury infrastructure has hard problems underneath it: bank integrations, settlement and reconciliation, the systems that move real money safely. AI is changing how this kind of product gets built and how a small team can compete with incumbents. You'll also pick up the work that doesn't fit anyone else's lane: architecture calls, infra we haven't built yet, the experimental thing no one's tried.

That means judgment, not ticket execution. You'll argue about what to build, decide what good looks like, 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.

If you've been the technical half of a small founding team and miss that altitude (close to the problem, no layers, your taste actually matters), this is that job again, with a company that already has strong momentum to go big.

What success looks like in 12 months

Two things.

First, ship. Roughly one major customer-facing feature a month, twelve over the year. Major meaning a Mundi customer can name it and tell you what changed for them. Not a refactor, not a config flag, a thing in the product that wasn't there before.

Second, change what the team can do. By year-end, there are capabilities Mundi has because you built them: bank rails or a settlement system the rest of the product gets to assume, an architectural call the next hire builds their work on top of, an AI-driven way of working that doubled the team's output. The kind of thing where, a year from now, someone says we couldn't have done X without it.

You'll fit if

You've done this before. You've been a technical co-founder, a founding engineer, or held an adjacent role with comparable rigor and breadth. You've shipped product to real users in environments without a PM holding your hand and without a more senior engineer defining the bar.

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 product taste, both at a senior bar. You can architect a backend, ship the frontend, and reason about UX in one pass.

You're fluent in Turkish and English. You'll work with Turkish customers, write Turkish UX copy, and run Turkish-language conversations. 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 product shaping sessions, code reviews, and a code editor on the same day, often in the same hour.

You'll work directly with the 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.

Compensation

Senior cash and meaningful ESOP. As our first MTS, you're joining early enough that the grant matters. If you're currently sitting on vested options elsewhere, we'll have a real conversation about making the move worth it.