Middle Frontend Developer / Pixi.js

This role is suitable for a Middle Frontend Developer with 3+ years of frontend experience, including at least one year delivering HTML5 slot games with Pixi.js, JavaScript, and TypeScript.

The candidate should be skilled in OOP, asynchronous programming, performance optimization, Spine animations, asset pipelines, Codex, WordCode, and fluent English.

They should be familiar with developing and shipping games end-to-end, designing reusable UI components, improving frameworks and build pipelines, reviewing code, collaborating across disciplines, and debugging WebGL performance on desktop and mobile.

How would you structure a reusable Pixi.js architecture for multiple slot games?

I would separate the shared framework from game-specific logic using reusable modules for scenes, reels, symbols, animations, events, configuration, and asset loading. Dependency injection and clear interfaces would allow each title to reuse core functionality without tightly coupling projects.

How do you optimize rendering performance in Pixi.js across desktop and mobile devices?

I profile CPU and GPU usage, reduce draw calls and texture switches, use texture atlases, limit unnecessary container updates, and apply object pooling for frequently created objects. I also control resolution, animation complexity, and particle counts based on device capabilities.

How would you implement a slot reel spin and stop sequence?

I would model the reel as a state machine with states such as idle, spinning, stopping, and stopped. The animation loop updates symbol positions, while the final result is applied deterministically and synchronized with easing, anticipation, win presentation, and user input rules.

How do you manage asynchronous operations such as asset loading and backend requests?

I use async/await with explicit loading states, cancellation or timeout handling, and centralized error reporting. Asset loading should be coordinated through a shared loader and cache so that concurrent requests are deduplicated and failures can be retried safely.

How would you integrate and control Spine animations in a Pixi.js game?

I would load Spine skeleton data through the asset pipeline, reuse cached resources, and expose a small animation controller for playing tracks, handling completion events, and managing transitions. Animation names, skins, and timing should be defined through configuration rather than scattered throughout game logic.

What should a robust asset management pipeline include for HTML5 games?

It should support manifest-based loading, cache versioning, texture atlases, compressed and device-specific assets, preload prioritization, and reliable fallback handling. The build pipeline should validate references and optimize assets before deployment to reduce startup time and bandwidth usage.

How would you design communication between the frontend slot game and backend services?

I would isolate transport logic in an API or platform adapter layer and expose typed domain methods to the game. The client should validate responses, handle retries and connection failures, prevent duplicate actions, and keep outcome presentation separate from transport implementation.

How do you use TypeScript and OOP to keep a game codebase scalable?

I use strict typing, interfaces for contracts, composition over deep inheritance, and focused classes with clear responsibilities. Shared abstractions should represent stable behavior, while game-specific rules remain configurable or implemented behind well-defined interfaces.

How would you debug a memory leak or rendering issue in a Pixi.js game?

I would reproduce the issue, inspect browser performance and memory profiles, and monitor destroyed display objects, event listeners, timers, textures, and WebGL resources. Common fixes include removing listeners, destroying unused containers and textures, stopping animation loops, and preventing repeated asset loading.

How would you improve build automation and development standards across several game projects?

I would create shared configuration, linting, formatting, testing, and build packages, then enforce them through CI checks. Automated asset validation, type checking, bundle-size monitoring, and deployment pipelines would make releases more consistent and reduce regressions across the portfolio.

Join a fast-moving game studio startup building standout HTML5 slot games with a collaborative, bureaucracy-free team. You’ll develop games end-to-end while shaping shared frontend architecture, reusable components, asset pipelines, and performance standards across projects. The stack includes Pixi.js, JavaScript/TypeScript, Spine, WebGL, Codex, and WordCode, with fully remote work available from Ukraine, Germany, Slovakia, Cyprus, or Poland and flexible CET hours. Salary is not disclosed, but the role offers meaningful technical ownership, minimal meetings, strong benefits, equipment, and regular team meetups.