playson - Compliance Engineer

• You are a developer first. 3+ years writing production code, comfortable reading someone else's codebase and forming your own opinion about what it does. You are not a documentation coordinator who learned some technical words • Strong Node.js and TypeScript. Our game math packages, engine integration, rules and bets migrations, test suites, and compliance automation are all JavaScript-side. You will read game math code and verify that what it does matches what we told the lab it does - and you will write the tooling that makes that check repeatable • You know what it takes to build certified products. You have worked for an iGaming game provider, a lottery, or another business where products require certification. You understand how that shapes development, testing, and releases, and why the code and supporting evidence need to stay aligned. • You build pipelines, not checklists. You have taken a manual, high-stakes process and turned it into something engineered: automated evidence, versioned artefacts, gates that fail closed • You can read data and write queries. SQL against a production analytics store, log investigation, understanding a metrics pipeline well enough to tell a real control failure from a broken dashboard • Composure in front of an auditor. In a lab session, an ISO assessment, or a future SOC 2 walkthrough, you answer the question that was asked with the evidence that was requested. You communicate with auditors and certification labs precisely and factually. You provide complete evidence for the question or control being assessed, avoid speculation, and escalate regulatory interpretations to the Head of Compliance • You know where your authority ends. When a question moves from technical fact to regulatory interpretation or commercial consequence, you route it to the Head of Compliance instead of improvising • You write clearly and permanently. Compliance evidence is read years later by people who were not in the room. Your documentation has to survive that • You are comfortable saying no. You will be the person telling a squad, under release pressure, that their change does not pass the gate. That conversation needs to be calm, specific, and final • Precise by temperament. You check the version number rather than remembering it. You are not bored by an audit trail • Direct dealings with a certification lab (GLI, BMM, eCOGRA, iTech Labs, or similar) or a gaming regulator • Hands-on evidence work for ISO 27001, SOC 2, or an equivalent information-security audit • Understanding of RNG, RTP mathematics, and how statistical certification evidence is produced • Familiarity with multi-jurisdiction licensing (UKGC, MGA, and regulated EU and LatAm markets) • Observability and alerting tooling - Datadog or equivalent, including building automation on top of it rather than just reading dashboards • Experience with change-management controls, audit trails, and segregation-of-duties models • Incident response experience, particularly where the incident had a regulatory or audit dimension • WHAT YOU CAN EXPECT ON THIS ROLE • A role with real authority: you hold gate sign-off, and a release does not go past you without it • Genuine engineering work - you own the compliance pipeline as a product, not a pile of checklists with a technical title • Direct exposure to certification labs, ISO assessors, and the path to SOC 2 - rare and portable experience • Close collaboration with math, QA, platform, and SRE across games and the platform • A compliance function that is being built up deliberately, with room to shape how it works