Customer Engineer

About this role

The Mission Minka is an open platform for publishing money. The platform lets product and technology teams integrate payment systems in days, not months. It powers top clearinghouses running real-time payments and the financial institutions innovating on those rails. We are hiring a Customer Engineer: the senior engineer who turns a signed deal into a live integration. We send you to a clearinghouse or a bank to make their money flow through Minka. You write the code, answer the hard architecture questions in the room, and own the integration until it clears its first real transaction in production. A product engineer builds one capability for many customers; you enable many capabilities for one. You enjoy both the social side of complex enterprise organizations and the technology of moving money, and you close the gap between "we signed" and "it works in production." New to our vocabulary? Bridges, wallets, symbols, domains, anchors, proofs — the whole ledger model lives at docs.minka.io . Skim it before you apply; you'll use these terms daily. What You Will Do You own the integration and delivery phase. When a clearinghouse, central bank, or large institution signs, you guide them through building their bridge — the HTTP service that implements our two-phase-commit protocol — plus any bridges into their own systems. You write the sample code, reference implementations, and integration scripts that get them live. You design the ledger model with them: how wallets, symbols, domains, and anchors map onto their accounts, rails, and core banking system. You debug bridges against the platform, handling idempotency, retries, and proof verification. When a prepare or commit phase fails in their environment, you troubleshoot it yourself, often against a go-live deadline. You also run the integration as a project, because at enterprise scale it is one. A single clearinghouse engagement means coordinating its own team, the participant banks it is onboarding, their engineers and core-banking vendors, and the compliance sign-offs before go-live — while keeping Minka's Sales and Product aligned on what the client needs next. You hold this web of stakeholders to a plan: set the sequence, surface the blocker before it becomes a slip, keep every party moving toward one go-live date. This is delivery ownership by a builder — you manage the people and the timeline because you write the code they depend on. You are the technical voice in our delivery-led sales motion — the four-hour Workshop and the one-week Design Sprint, where the client's own data flows through the ledger and we never over-promise. For clearinghouse deals you operationalize the network, onboarding and certifying each participant bank. And you carry the field back to Product: the pain points and requests you hear on-site become the requirements that shape what we build next. That feedback loop is the most valuable thing you do. A resolved ticket is only a win if the customer is live and better off. Requirements Who You Are You have the depth of a senior engineer and the communication of a consultant. You read a client's business goal, map it to our API and ledger model, and write the code that proves it. You have ten or more years building production software, still hands-on, comfortable from architecture down to keyboard. Our stack and SDKs are TypeScript and Node.js. You know REST APIs, distributed systems, idempotency, retries, two-phase commit, and why a system that moves money cannot tolerate partial state. You have taken complex B2B integrations live, ideally in payments or fintech, and connected modern APIs to legacy banking cores — or you will learn that fast. You can run a delivery across many hands: you have held a plan together across teams that don't report to you and driven a multi-party integration to a date. You can stand in front of a bank's CTO or a central bank's team, field "how does this actually work?", and earn trust. You work in professional English and Spanish. And you are comfortable with ambiguity and solo ownership — we can send you to a client alone and trust you to figure out what needs to happen. You have built systems before. Now you want to be the person who makes sure those systems change the way the world moves money. Nice to Have It helps if you already know ledgers, double-entry accounting, reconciliation, or cryptographic signing (Ed25519 proofs, non-repudiation). Instant-payment rails, ACH, ISO 20022, clearing and settlement, or cloud-native deployment on GCP are all pluses. And it would not hurt if you have seen Mr. Robot, hack on weekends, and run your own bitcoin node. Why Minka Money should move as freely as information does on the web. Bitcoin is the settlement layer of the internet; we are the clearing layer on top of it. We are small on purpose, funded for the long game, and we build infrastructure our clients own — their keys, their ledger, no lock-in. If you want your code to clear real money between real institutions, this is the seat.