Crypto game testing

• Test our crypto originals Plinko, Roulette, Crash, Prime Dice where settlement is on-chain and the maths is the product.
• Verify provably-fair mechanics end to end: the pre-committed server seed hash, client seed changes, nonce incrementing per bet, seed rotation revealing the previous seed, and outcomes a player could independently reproduce from the published algorithm.
• Test each title's own maths: Plinko row counts, risk levels and multiplier grids; Crash cash-out timing, auto-cash-out and multi-bet; Dice roll-over/under targets against payout multiplier and house edge; Roulette inside, outside and neighbour bets against the payout table.
• Validate token precision and rounding per currency decimal places, rounding direction, dust amounts, and the difference between the stored value and the displayed one.
• Reconcile the ledger: deposits, bets, wins and withdrawals against both the platform wallet and the chain, including pending, confirmed and late confirming transactions.
• Hammer concurrency: double-submitted bets, spam betting, the same account open in two tabs or on two devices, and races between a bet and a balance update.
• Probe the limits: minimum and maximum stake per currency, max-win and max-profit caps, and behaviour when a win would exceed the cap.
• Test the failure paths that cost money connection dropped at bet submit, bet placed but the response lost, cash-out fired at the instant of a crash and confirm the balance reconciles afterwards.
• Verify the bet history and the fairness-verification page tell the same story as the API and the chain.

Live casino testing

• Test streamed dealer tables end to end, from lobby listing through to a settled round and the transaction that follows it.
• Pin down bet-window timing: when the window opens and closes against the server clock, whether a last-instant bet is accepted or rejected cleanly, and what happens to a bet that lands after the cut-off.
• Verify game state stays in sync with the studio: dealer action versus client state, the displayed result versus the provider's round result, and a round ID you can trace from the table to the wallet.
• Cover the table games properly blackjack split, double, insurance and bet-behind; roulette inside, outside, neighbour and racetrack bets; side bets such as perfect pairs and 21+3 each checked against its own payout rules.
• Test chips and controls: denominations per currency, rebet, double, undo, table minimums and maximums, and multi-seat or multi-table play.
• Break the real-time layer deliberately: socket dropped mid-round, reconnect, mobile backgrounding, airplane mode, throttled bandwidth, and a frozen stream while the round continues underneath then confirm the balance and outcome are still correct.
• Check the stream itself: latency against game state, quality tiers and auto-degradation, audio, fullscreen, orientation change and picture-in-picture, on real devices and in in-app wallet browsers.
• Validate third-party provider integrations: lobby listings and live stats, launch token and session handling, currency and limit mapping, error codes, and returning to the lobby cleanly.
• Confirm balance sync between our wallet and the provider session, including funds held in a pending round and what happens if the session expires while a bet is live.
• Verify round history and video replay match the settled result, and that responsible-gaming limits and jurisdictional blocks apply correctly mid-session, not just at launch.

Across all three

• Own test strategy for the titles you're responsible for and be accountable for the release call.
• Run functional, regression and exploratory testing across desktop, mobile and tablet, on real devices as well as standard browsers.
• Check the things regulators and players both care about: responsible gaming controls, bet limits, jurisdictional restrictions and correct behaviour across currencies and locales.
• Write and maintain automated tests in our Playwright/TypeScript suite page objects, settlement specs and regression coverage for each new title and raise the bar on how we approach automation as a team.
• Drive our AI-assisted and agent-led testing: use AI agents to accelerate test authoring, extend exploratory coverage, maintain suites against UI churn and triage failures then turn what works into a repeatable practice the rest of the team can use.
• Judge where AI helps and where it doesn't. Agent-generated coverage still has to be reviewed, and a confident wrong answer about a payout is worse than no answer.
• Support UAT and monitor titles after release verify fixes in production, and help triage live incidents when something behaves unexpectedly with real money on the table.
• Raise clear, reproducible bugs in Jira and drive them to resolution with product owners and developers.
• Investigate mobile stability issues crashes, memory pressure, rendering failures and get to a root cause rather than a workaround.
• Spot patterns across the portfolio. A defect that appears in four games usually isn't four bugs.
• Mentor and set standards. As the QA function grows, how we test is partly your design.
• Communicate release readiness honestly: what's tested, what's risky, what isn't ready.

What we're looking for

Essential

• 5+ years in QA on web or mobile products, with real ownership of test strategy rather than just execution.
• Hands-on experience testing at least one of our three core areas slots, crypto/originals games, or live casino and the appetite to own all three.
• Comfortable testing real-time,