- Experience
- 3+ years
- technical QA · client + backend
- Product
- Slot games
- real-money · jurisdiction rules
- Client
- PixiJS v8 client
- TypeScript · Spine · GSAP
- Server
- Go engine
- NestJS · Redis · RabbitMQ
- Load & perf
- K6 · JMeter
- API · integration · performance
What you'll own,
what you'll bring
Eight things you'll own and eight we need you to bring. If most of the second list already sounds like your week, we should talk.
You will test a TypeScript/PixiJS v8 client alongside a server-authoritative Go engine, ensuring client spin presentation and backend results remain fully consistent. That seam is the job: the client shows the spin, the engine decides it, and most of what goes wrong lives in between. This role offers the opportunity to work on complex slot mechanics, jurisdiction compliance, and high-concurrency architecture across API, integration, and performance testing domains.
You own this seam.
DUTIES AND RESPONSIBILITIES
You will own quality across both halves of a real-money slot product. On the client that means typed HFSM spin-lifecycle transitions — state consistency and session recovery across mid-spin, free spins and bonus rounds — together with PixiJS v8 rendering, Spine-Pixi v8 skeletal animation and GSAP spin-stop choreography on target mobile and desktop browsers. You will also run against offline mocked backends and prove the client survives packet loss and mid-spin disconnections.
- Engine lifecycle QA — spin generation, keep-generate and history-replay endpoints, confirming deterministic replay.
- RGS adapters — SDK-injected RNG sourcing, wallet transaction accuracy, and math/RTP compliance against certified models.
- Backend storage and messaging — PostgreSQL, Redis, RabbitMQ — with K6 or JMeter load tests for spin-endpoint latency and throughput.
Alongside that you validate jurisdiction-specific rules, mandatory messaging and audit-trail behaviour driven by configuration profiles — and turn everything you find into precise technical bug reports that name the root cause, whether it sits in an HFSM state, engine determinism, a database lock or a queue sync issue.
Both halves of the product are yours: the client that shows the spin, and the engine that decides it.
Requirements
We are looking for 3+ years of technical QA covering client-rendered game engines and high-concurrency backend services, a strong understanding of concurrency issues and race conditions, and the communication skills to explain a failure across frontend and backend layers without hand-waving.
- Client — TypeScript, PixiJS v8, Spine-Pixi v8, GSAP, and the architecture layers: Presentation / HFSM / Domain / Network / Platform.
- Server — Go services, RGS/SDK integration contracts, NestJS, and backend support via Redis and RabbitMQ.
- Domain — slot mechanics end to end: paylines, clusters and Megaways, RTP, volatility, free spins, bonus buy, ante bet and max-win.
Basic understanding is enough on the stack itself. We also expect experience or theoretical knowledge of performance testing tools such as K6 and JMeter, for backend load and client frame-budget profiling, and a proven ability to put LLMs and AI coding assistants to work on test-case generation, documentation analysis and code auditing.
Basic understanding is enough on the stack. Depth is what we build together.
Join our team
Send your CV and a few lines about yourself.
After you hit send
- 01We read every application ourselves
- 02You get a call slot or a straight answer
- 03No silent pipelines, no automated rejections