Full-stack Engineer (Junior) — Product Surfaces & Admin Console

*Do Not Reach Out on Linkedin, All Hiring Will Be Done via Wellfound

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

We have a design system, full design handoffs across four surfaces, and a working prototype. Turning that into a production product — one that also re-skins cleanly for partner operators — is a large volume of careful, well-supervised work, and the fastest way for a strong junior engineer to learn how a real financial platform is built.

What you'll own — consumer platform (B2C)

• Product surfaces: market pages, multi-outcome event cards, portfolio views, onboarding flows
• The public site
• Maintaining and extending the component library and design tokens
• Bug fixes across the stack, front and back
• Keeping what you build faithful to the design system, and flagging it when the design and the code disagree

What you'll own — partner product (B2B)

• The internal admin console, including the per-operator configuration screens our team uses to set up and manage partners
• White-label theming: making the component library genuinely re-skinnable so an operator can apply their brand without breaking layout or legibility
• Embeddable and iframe-hosted surfaces that have to behave inside a partner shell we do not control
• The partner-facing documentation site
• Trade surveillance, leagues, regions and trade instrument screens that span both arms

Must have

• 1–3 years professional experience, or a portfolio of substantial projects you can walk us through in detail
• Solid React and TypeScript — you can build a non-trivial component without reaching for a tutorial
• Real CSS ability: responsive layouts, flexbox and grid, and an understanding of why something isn't centring
• Comfortable reading code you did not write and working out what it does
• Git fluency, and the discipline to keep pull requests small and reviewable
• The habit of asking a question after twenty minutes stuck, rather than four hours stuck

Nice to have

• Experience working from a design system or Figma handoff
• Any exposure to theming, multi-brand front-ends or embeddable widgets
• Supabase or any Postgres-backed backend
• Any exposure to fintech, trading or dashboard-heavy products

How this role is supervised

You will not work unsupervised on the ledger, settlement or payment paths. Those are money-critical and you will only touch them paired with a senior engineer. Everywhere else, you will be given real ownership quickly. Expect thorough code review — it is the main way you will learn here, and it is not a judgement on you.