Senior Full-stack Engineer — Ledger, Markets & Settlement

How Zabili is structured
Zabili is the prediction market platform built and operated by Degenerate. It runs on two arms off one platform. The consumer arm (B2C) is our own product, where users trade directly with us. The partner arm (B2B) licenses that same engine to betting and gaming operators, who run our markets inside their platforms, under their brand, with their wallet. Every role on this team serves both.
Working pattern
We work remotely on GMT+3 core hours, so your day overlaps with the rest of the team. Markets resolve when events happen, and events happen at weekends — sport especially. Expect some weekend cover on a rota, and occasional out-of-hours work around launches and partner go-lives. It is shared across the team, it is planned in advance rather than sprung on you, and it is not a euphemism for working every Saturday.
Why this role exists
Every unit of value on the platform lives in a double-entry ledger, and every price is produced by a market-making engine. Both must be provably correct — and both must work when the money belongs to our own users and when it belongs to a partner operator. This role owns that engine end to end.
What you'll own — consumer platform (B2C)
• The double-entry ledger: accounts, journals, invariants, reconciliation
• The LMSR liquidity engine, including subsidy budgeting via the b parameter
• Trade execution, position tracking and settlement
• The resolution and oracle state machine, including the dispute window
• The platform's invariant test suite — the properties that must hold after every single operation
• The trading interface where all of the above surfaces to users: market pages, order entry, portfolio and positions
What you'll own — partner product (B2B)
• Multi-tenant ledger design: strict segregation between operators, and between operator float and end-user liability
• Per-operator liquidity and subsidy budgeting — each partner gets its own risk envelope, not a share of ours
• A market catalogue that can be scoped per partner: which markets an operator sees, at what limits, in what currency
• Resolution and settlement events pushed reliably into partner systems, including replay after an outage on their side
• Per-operator settlement reporting and reconciliation that a partner finance team can audit without calling us • Invariants that hold per tenant, not just in aggregate
Must have
• 5+ years full-stack engineering, with real ownership of a system that moved money — payments, exchange, banking, lending or wallet infrastructure
• Fluency in double-entry accounting as an engineering discipline, not a finance concept
• Strong SQL and transactional reasoning: isolation levels, race conditions, idempotency, concurrent writes
• Postgres in production
• Production React and TypeScript, including real-time state: websockets, subscriptions, optimistic updates
• Demonstrated experience mentoring junior engineers — this team has two, and their growth is partly your responsibility
• The instinct to write the failing test before the feature
Nice to have
• Multi-tenant architecture where tenants must never see each other
• Exposure to order books, AMMs, market making or derivatives pricing
• Supabase (Postgres, realtime, row-level security)
• Experience migrating a system from one market structure to another
• Prior work in a regulated or licensed environment
#IkoKazi

Work arrangement
Yes