Senior Platform Engineer

What the job is

Every casino running on Scalara runs the same software. Our own brands and every private copy we sell are built from one codebase, so a change you make reaches everyone, and a mistake you make does too. That constraint is the job.

You would own a domain rather than a queue of tickets. The domains that need an owner are the wallet and ledger, where real, bonus and locked balances reconcile across fiat and crypto rails; the compliance engine, where a five-tier trust model decides what a player may do before money moves; and the provisioning pipeline, which takes an operator from application to a deployed environment without a person in the middle.

The work is mostly correctness under concurrency. Bets settle exactly once even when a game provider's connection stutters and retries. A withdrawal cannot be paid twice. A ledger that disagrees with itself is an incident, not a bug. If that sounds like the interesting part of the problem rather than the tedious part, this is the right role.

The first ninety days

Weeks one to three. Read the platform with an engineer who already knows it, and ship something small to production in your first week. You will run the local stack, follow one real deposit from the payment provider through the ledger to the player's balance, and read the audit trail it produced.

Weeks four to eight. Take your first real piece of a domain. Something with a clear boundary and a real operator waiting for it. You will write the design note, get it reviewed, build it, and be the person who watches it in production afterwards.

Weeks nine to thirteen. Own the domain. By the end of the quarter you should be the person the rest of the team asks before changing anything inside it, and you should have opinions about what is wrong with it that you are already fixing.

What we need

• Several years building production backend systems that hold money, state or both, and a clear account of something you got wrong and how you found out.
• Comfort with concurrency, idempotency and retries as everyday concerns rather than as an advanced topic.
• Working knowledge of relational data modelling, and the instinct to reach for a constraint before reaching for a check in application code.
• The habit of writing a short design note before writing code, and of reading somebody else's carefully.
• English good enough to argue precisely in writing, because most of our decisions are made in text.

What we do not need

• Experience in iGaming. Several of the best engineers here arrived from other regulated industries. The domain is learnable, the engineering judgement is not.
• A specific framework on your CV. We care what you have shipped and what you understand, not which library you shipped it with.
• A degree.
• A portfolio of side projects. What you have done at work counts fully.
• Availability at midnight. We run a real on-call rotation with real handovers, not an expectation that everyone is always reachable.

Location and working model

Our engineering base is in Serbia, and this role is either there or remote within European time zones. We work asynchronously by default and meet deliberately: a short daily written update, one working session a week per domain, and a quarterly week together in person.

The commercial side of the business sits in the UAE, the UK and Europe, so you will occasionally be on a call with an operator. That is intentional. Engineers here talk to the people using what they build.

How to apply

Email contact@scalaralabs.com with the subject line Senior Platform Engineer.

Send a CV or a profile, and a few paragraphs about one system you built that had to be correct rather than merely working: what it did, what could have gone wrong, and how you knew it had not. That paragraph matters more to us than the CV.

We read every application. If we are not going to take it further, we will tell you.