Building the systems underneath.
A double-entry core holding every balance across fiat and digital assets, the compliance systems that run inside it rather than beside it, the payment rails under all of it, and the apps people actually open. None of it is a prototype: it is in production inside licensed financial institutions, moving their customers’ money.
How it works here.
- Eight to twelve
- That is the size of a team, and it is the size on purpose. Nothing gets built twice by two groups who do not know about each other, and what you make is identifiable afterwards as the thing you made.
- Everyone is reachable
- Access does not stop at a level. There is nobody you have to go through to reach the person who can decide something, including at the top, and an idea or a concern is answered rather than logged.
- Decisions are made with the people who implement them
- Architecture is discussed with whoever will write it, which is why it appears in the posting as something you do rather than something handed down to you.
- What you know is expected to leave you
- Mentoring is written into both roles as a responsibility rather than offered as a perk. Somebody senior who keeps what they know is a single point of failure, and this is not a business that can carry one.
- AI is expected, not tolerated
- In regulated businesses these tools are usually banned outright or used quietly. Here they are in the posting by name — Cursor, Copilot, Claude Code, Aider — and using them is the expectation rather than something you get away with. What the hours buy is the part that still needs a person: the design, the edge cases, the review. What does not move is the standard the output is held to, which is why reviewing it is written into the job rather than assumed.
- Operated, not delivered
- The platform is not handed over and left. It runs continuously inside licensed institutions, moving real money from your first week — so the work is kept rather than shipped, and whoever chose how something works is whoever keeps it working.
