Slot Frontend Engineer (iGaming)

TL;DR

Slot Frontend Engineer (PixiJS/TypeScript): Building and maintaining a high-performance slot-game client codebase from scratch with an accent on state machine modelling (HFSM), session recovery, and cross-market compliance. Focus on optimizing rendering performance (60 fps), implementing complex skeletal animations, and ensuring strict architectural separation between the presentation and authoritative server layers.

Company

hirify.global is a game development studio specializing in slot-client engagements and development.

What you will do

• Develop and maintain the entire slot-game client codebase from scratch through to live operations.
• Implement typed HFSM to model the slot spin lifecycle, including free spins, bonus rounds, and error recovery.
• Create jurisdiction-aware compliance UI to support multiple markets under audit without per-market code forks.
• Manage client-side performance budgets and asset/texture-memory strategies for mobile and desktop.
• Build and maintain offline mocked backends for development and QA.
• Utilize and document the use of AI tools for scaffolding, refactoring, and technical documentation.

Requirements

• Strong proficiency in TypeScript, PixiJS v8, Spine-Pixi v8, and GSAP.
• Experience implementing strict five-layer architecture (Presentation / HFSM / Domain / Network / Platform).
• Ability to build session recovery mechanisms for disconnections during active game states.
• Capability to ensure 60 fps performance on mobile and desktop browsers without rendering artifacts.
• Experience with asset-loading strategies and managing bundle-size budgets for mobile.
• Proficiency with Vite, Axios, and Git.

Nice to have

• Production experience in regulated iGaming or slot frontend development.
• Experience with Live-ops, including jackpot events, tournaments, and A/B tests.
• Knowledge of localization, specifically RTL and CJK languages.
• Experience with CI/CD pipelines (lint, type-check, test, build, deploy).
• Technical writing skills for layer contracts, HFSM diagrams, and runbooks.