Lead Software Engineer

We're building financial infrastructure from scratch. We're looking for a Lead Engineer who wants to build the spine of a transactional system — the part that must be right every single time. Someone who thinks about ordering, consistency, idempotency, throughput, latency, and the quiet mechanics of how systems fail and recover. This is systems engineering, not app building.

This is a founding-team role. You'll decide how the whole thing is shaped: the architecture, the tools, the patterns, the early hires. You won't just write code; you'll define the foundation the rest of the system stands on.

What you'll do (subject to change)

• Build the core transactional engine
• Shape and implement the internal ledger: how value is recorded, moved, reconciled, and audited.
• Choose a sensible, durable tech stack. We're stack-agnostic: good engineers know how to pick the right tools.
• Ship early versions quickly, then turn them into reliable, observable, production-ready systems.
• Think and make decisions about load, ordering, concurrency, latency, failure modes, and keeping the system steady under pressure.
• Design components that behave well when things go wrong, not just when things go right.
• Work directly with product to turn rough ideas into concrete, buildable designs.
• Help translate technical decisions into something regulators and compliance teams can understand and approve (clarity matters as much as code).
• Set the engineering culture: clear thinking, clean boundaries, solid tradeoffs.
• Hire and mentor the early engineering team.
• Build parts of the system that may later connect to digital forms of value (tokenized assets, programmable money, etc.), though no prior blockchain experience is required.

What you've done (or know how to do)

We're not counting years. We care about whether you've built and scaled real systems.

You might have:

• Designed or maintained backend systems where correctness mattered
• Worked on or built out ledger-like systems: balances, movements, reconciliation, states that must always add up
• Built or maintained systems in payments, financial engineering, neobanking, or digital banking (helpful, but not required)
• Taken something from zero → v1 → something that actually had to scale
• Worked on infrastructure where ordering, reliability, and recovery weren't optional
• Dealt with concurrency, race conditions, and real-world load
• Worked in small teams where responsibility wasn't shared, you owned it
• Operated in environments where compliance, auditability, or regulation shaped your design choices

You have opinions shaped by building things, not by reading about them.

How we work

We're a small and hands-on team. We value clarity, long-term thinking, and written reasoning. We avoid unnecessary complexity and focus on the problems that matter.

We're building something that will sit in a regulated environment, so discipline, transparency, and careful design are critical to the work, not just afterthoughts.

There's no map for what we're building. You should be comfortable drawing it.

What we offer

• A founding role shaping a long-term, high-impact system
• Real ownership and autonomy
• Competitive compensation
• The chance to build foundational financial infrastructure from the ground up